Merge branch 'develop' of bitbucket.org:k1jt/wsjtx into develop

doc/user_guide/en/make-qso.adoc

@@ -83,12 +83,13 @@ fully automated QSOs.
 === Contest Messages
 
 The FT4, FT8, and MSK144 protocols support special messages optimized
-for *NA VHF* and *EU VHF* contests. FT8 also supports messages for
+for *NA VHF* and *EU VHF* contests.  FT4 and FT8 also support messages
-*ARRL Field Day* and the *ARRL RTTY Roundup*.  The decoders recognize
+for *ARRL Field Day*, *ARRL RTTY Roundup*, and the *WW Digi* contest.
-and decode these messages at any time.  Configure the program to
+The decoders recognize and decode these messages at any time.
-automatically generate the required message types by selecting a
+Configure the program to automatically generate the required message
-supported operating activity on the *Settings | Advanced* tab.  Model
+types for contest exchanges and carry out suitable auto-sequencing by
-QSOs then proceed as follows, for each event type:
+selecting a supported operating activity on the *Settings | Advanced*
+tab.  Model QSOs then proceed as follows, for each event type:
 
 *NA VHF Contest*
 
@@ -131,6 +132,31 @@ to upgrade _WSJT-X_ if you will use *EU VHF Contest* messages.
  W9XYZ K1ABC R 589 MA
                        K1ABC W9XYZ RR73
 
+*WW Digi Contest*
+
+ CQ K1ABC FN42
+                       K1ABC S52XYZ JN76
+ S52XYZ K1ABC R FN42
+                       K1ABC S52XYZ RR73
+
+
+Contest QSOs are generally treated as invalid when they appear in one
+station's log and not the supposed QSO partner's.  To avoid Not-in-Log
+(NIL) penalties for yourself and others, we recommend the following
+guidelines for contest logging with FT4, FT8, and MSK144:
+
+ - Activate and learn to use the alternate F1-F6 bindings selectable
+   on the *Settings | General* tab.
+ 
+ - Always log a QSO when you have received RRR, RR73, or 73 from a
+   station you are working.
+
+ - Log a QSO when you send RR73 or 73 if you are reasonably confident
+  it will be copied. But be sure to watch for any indication that it
+  was not copied, and then take appropriate action. For example, if
+  you receive the Tx3 message (R plus contest exchange) again, hit F4
+  to re-send your RR73.
+
 [[COMP-CALL]] 
 === Nonstandard Callsigns
 

doc/user_guide/en/tutorial-example4.adoc

@@ -45,7 +45,7 @@ when double-clicking.
 
 .Best S+P Button
 
-The FT4 user interface includes a new button labeled *Best S+P*.
+The FT4 user interface includes a button labeled *Best S+P*.
 
 image::Best_S+P.png[align="center"]
 

doc/user_guide/en/vhf-features.adoc

@@ -26,8 +26,6 @@ propagation
 - *Doppler tracking*, which becomes increasingly important for EME
 on bands above 1.2 GHz.
 
-- Optional *Auto-Sequencing* in JT4, JT9, and JT65 as well as FT8 and QRA64.
-
 [[VHF_SETUP]]
 === VHF Setup
 
@@ -160,18 +158,16 @@ image::JT4F.png[align="center",alt="JT4F"]
 In many ways JT65 operation on VHF and higher bands is similar to HF
 usage, but a few important differences should be noted.  Typical
 VHF/UHF operation involves only a single signal (or perhaps two or
-three) in the receiver passband.  You may find it best to check
+three) in the receiver passband.  We recommend that you check *Single
-*Single decode* on the *Settings -> General* tab.  There will be
+decode* on the *Settings -> General* tab, and do not check *Two pass
-little need for *Two pass decoding* on the *Advanced* tab.  With VHF
+decoding* on the *Advanced* tab.  With VHF features enabled the JT65
-features enabled the JT65 decoder will respond to special message
+decoder will respond to special message formats often used for EME:
-formats often used for EME: the OOO signal report and two-tone
+the OOO signal report and two-tone shorthand messages for RO, RRR, and
-shorthand messages for RO, RRR, and 73.  These messages are always
+73.  These messages are always enabled for reception; they will be
-enabled for reception; they will be automatically generated for
+automatically generated for transmission if you check the shorthand
-transmission if you check the shorthand message box *Sh*.
+message box *Sh*.  *Deep* on the *Decode* menu will be automatically
-
+selected.  You may optionally include *Enable averaging*, *Enable Deep
-*Deep* on the *Decode* menu will be automatically selected.  You may
+search*, and *Enable AP*.
-optionally include *Enable averaging*, *Enable Deep search*, and
-*Enable AP*.
 
 The following screen shot shows three transmissions from a 144 MHz EME
 QSO using submode JT65B and shorthand messages.  Take note of the
@@ -275,8 +271,6 @@ this number is well below 100%, you may increase the decoding depth
 from *Fast* to *Normal* or *Deep*, and increase *F Tol* from 100 to
 200 Hz.
 
-+
-
 NOTE: Most modern multi-core computers can easily handle the optimum
 parameters *Deep* and *F Tol 200*.  Older and slower machines may not
 be able to keep up at these settings; at the *Fast* and *Normal*