docs: More translation-revisiting changes.

Author: smoe

docs/man/man9/hostmot2.9

@@ -871,7 +871,7 @@ Sets the master RC PWM frequency. Maximum is 1 kHz, minimum is .01 Hz. Defaults
 
 .TP
 (float rw) width
-Sets the per channel pulse width in (ms/scale)
+Sets the per channel pulse width in (ms/scale).
 
 .TP
 (float rw) offset
@@ -1123,7 +1123,7 @@ Only full GPIO pins have this parameter.
 (bit r/w) is_opendrain
 This parameter only has an effect if the "is_output" parameter is True.
 If this parameter is False, the GPIO behaves as a normal output pin:
-the IO pin on the connector is driven to the value specified by the "out" HAL pin (possibly inverted), and the value of the "in" and "in_not" HAL pins is undefined.
+The IO pin on the connector is driven to the value specified by the "out" HAL pin (possibly inverted), and the value of the "in" and "in_not" HAL pins is undefined.
 If this parameter is True, the GPIO behaves as an open-drain pin.
 Writing 0 to the "out" HAL pin drives the IO pin low, writing 1 to the "out" HAL pin puts the IO pin in a high-impedance state.
 In this high-impedance state the IO pin floats (weakly pulled high), and other devices can drive the value;

docs/man/man9/lcd.9

@@ -46,35 +46,28 @@ and, as the output format mimics the ADM3 terminal format, it could be used
 to stream data to a serial device. Perhaps even a genuine ADM3. 
 The strings contain a mixture of text values (which are displayed directly), 
 "escaped" formatting codes and numerical format descriptors. 
-For a detailed description of formatting codes see: 
-http://en.wikipedia.org/wiki/Printf
+For a detailed description of formatting codes see: http://en.wikipedia.org/wiki/Printf .
 
-The component can be configured to display an unlimited number of 
-differently-formatted pages, which may be selected with a HAL pin. 
+The component can be configured to display an unlimited number of differently-formatted pages, which may be selected with a HAL pin. 
 .TP
  \fBEscaped codes\fR
- \en Inserts a clear-to-end, carriage return and line feed character. This will 
-still linefeed and clear even if an automatic wrap has occurred (lcd has no 
-knowledge of the width of the lcd display.) To print in the rightmost column it
-is necessary to allow the format to wrap and omit the \en code.
+ \en Inserts a clear-to-end, carriage return and line feed character.
+This will still linefeed and clear even if an automatic wrap has occurred (lcd has no knowledge of the width of the lcd display).
+To print in the rightmost column it is necessary to allow the format to wrap and omit the \en code.
 
- \et Inserts a tab (actually 4 spaces in the current version rather than a true
-tab.)
+ \et Inserts a tab (actually 4 spaces in the current version rather than a true tab.)
 
  \eNN inserts the character defined by the hexadecimal code NN. 
- As the ',' character is used in the format string to separate LCD instances
- it must be represented by \e2C in the format string. (the decimal
- separator is handled differently)
+ As the ',' character is used in the format string to separate LCD instances it must be represented by \e2C in the format string (the decimal separator is handled differently).
 
  \e\e Inserts a literal \e.
 
 .TP
  \fBNumerical formats\fR
 
 \fBlcd\fR differs slightly from the standard printf conventions.
-One significant difference is that width limits are strictly enforced to prevent the LCD display 
-wrapping and spoiling the layout. The field width includes the sign character
-so that negative numbers will often have a smaller valid range than positive. 
+One significant difference is that width limits are strictly enforced to prevent the LCD display wrapping and spoiling the layout.
+The field width includes the sign character so that negative numbers will often have a smaller valid range than positive. 
 Numbers that do not fit in the specified width are displayed as a line of asterisks (\fB********\fR).
 
 Each format begins with a "%" symbol. (For a literal % use "%%").
@@ -85,41 +78,33 @@ This is the default and is not strictly necessary.
 
 "0" Pad the number to the specified width with the numeral 0. 
 
-"+" Force display of a + symbol before positive numbers. This (like the \- sign)
-will appear immediately to the left of the digits for a space-padded number 
-and in the extreme left position for a 0-padded number. 
+"+" Force display of a + symbol before positive numbers.
+This (like the \- sign) will appear immediately to the left of the digits for a space-padded number and in the extreme left position for a 0-padded number. 
 
-"1234567890" A numerical entry (other than the leading 0 above) defines the
-total number of characters to display including the decimal separator and the sign.
+"1234567890" A numerical entry (other than the leading 0 above) defines the total number of characters to display including the decimal separator and the sign.
 Whilst this number can be as many digits as required, the maximum field width is 20 characters.
-The inherent precision of the "double" data type means
-that more than 14 digits will tend to show errors in the least significant digits.
+The inherent precision of the "double" data type means that more than 14 digits will tend to show errors in the least significant digits.
 The integer data types will never fill more than 10 decimal digits. 
 
 Following the width specifier should be the decimal specifier.
 This can only be a full-stop character (.) as the comma (,) is used as the instance separator. 
-Currently lcd does not access the locale information to determine the correct separator
-but the \fBdecimal\-separator\fR HAL parameter can be used to choose any desired separator.
+Currently lcd does not access the locale information to determine the correct separator but the \fBdecimal\-separator\fR HAL parameter can be used to choose any desired separator.
 
-Following the decimal separator should be a number that determines
-how many places of decimals to display. This entry is ignored in the case of integer formats. 
+Following the decimal separator should be a number that determines how many places of decimals to display. This entry is ignored in the case of integer formats. 
 
-All the above modifiers are optional, but to specify a decimal precision the
-decimal point must precede the precision, e.g., as in "%.3f". 
+All the above modifiers are optional, but to specify a decimal precision the decimal point must precede the precision, e.g., as in "%.3f". 
 The default decimal precision is 4.
 
 The numerical formats supported are:
 
 \fB%f %F\fR (for example, %+09.3f) These create a floating-point type HAL pin.
-The example would be displayed in a 9-character field, with 3 places of decimals,
-as a decimal separator, padded to the left with 0s and with a sign displayed for 
-both positive and negative. Conversely a plain %f would be 6 digits of decimal,
+The example would be displayed in a 9-character field, with 3 places of decimals, as a decimal separator,
+padded to the left with 0s and with a sign displayed for both positive and negative. Conversely a plain %f would be 6 digits of decimal,
 variable format width, with a sign only shown for negative numbers.
 Both %f and  %F create exactly the same format. 
 
 \fB%i %d\fR (For example %+ 4d) Creates a signed (s32) HAL pin.
-The example would display the value at a fixed 4 characters, space padded,
-width including the "+" giving a range of +999 to \-999. %i and %d create identical output. 
+The example would display the value at a fixed 4 characters, space padded, width including the "+" giving a range of +999 to \-999. %i and %d create identical output. 
 
 \fB%u\fR (for example %08u) Creates an unsigned (u32) HAL pin.
 The example would be a fixed 8 characters wide, padded with zeros. 
@@ -131,16 +116,14 @@ A width may be specified, though the u32 HAL type is only 8 hex digits wide.
 \fB%o\fR Creates an unsigned (u32) pin and displays the value in octal representation. 
 
 \fB%c\fR Creates a u32 HAL pin and displays the character corresponding to the value of the pin.
-Values less than 32 (space) are suppressed. A width specifier may be used,
-for example %20c might be used to create a complete line of one character. 
+Values less than 32 (space) are suppressed. A width specifier may be used, for example %20c might be used to create a complete line of one character. 
 
 \fB%b\fR This specifier has no equivalent in printf.
 It creates a bit (boolean) type HAL pin.  The b should be followed by two characters
 and the display will show the first of these when the pin is true, and the second when false.
 Note that the characters follow, not precede the "b", unlike the case with other formats.
 The characters may be "escaped" Hex values.
-For example "%b\eFF " will display a solid black block if true,
-and a space if false and "%b\e7F\e7E" would display right-arrow for false and left-arrow for true.
+For example "%b\eFF " will display a solid black block if true, and a space if false and "%b\e7F\e7E" would display right-arrow for false and left-arrow for true.
 An unexpected value of 'E' indicates a formatting error. 
 
 \fBPages\fR
@@ -150,8 +133,7 @@ A "Page" in this context refers to a separate format which may be displayed on t
 \fBInstances\fR
 The instance separator is the comma. This creates a completely separate lcd instance,
 for example to drive a second lcd display on the second 7I73. 
-The use of comma to separate instances is built in to the modparam reading code
-so not even escaped commas "\e," can be used.
+The use of comma to separate instances is built in to the modparam reading code so not even escaped commas "\e," can be used.
 A comma may be displayed by using the \e2C sequence. 
 
 .SH AUTHOR

docs/man/man9/pwmgen.9

@@ -15,8 +15,7 @@ The number of channels actually loaded depends on the number of \fItype\fR value
 The value of each \fItype\fR determines the outputs for that channel.
 .P
 .TP
-type 0: single output A single output pin, \fBpwm\fR, whose duty cycle is determined by the input value for positive inputs,
-and which is off (or at \fBmin\-dc\fR) for negative inputs.
+type 0: single output A single output pin, \fBpwm\fR, whose duty cycle is determined by the input value for positive inputs, and which is off (or at \fBmin\-dc\fR) for negative inputs.
 Suitable for single ended circuits.
 .TP
 type 1: pwm/direction
@@ -47,9 +46,7 @@ Operates on all channels at once.
 Enables PWM generator \fIN\fR - when false, all \fBpwmgen.\fIN\fR output pins are low.
 .TP
 \fBpwmgen.\fIN\fB.value\fR float in
-Commanded value.  When \fBvalue\fR = 0.0, duty cycle is 0%,
-and when \fBvalue\fR = \(+-\fBscale\fR, duty cycle is \(+- 100%
-(subject to \fBmin\-dc\fR and \fBmax\-dc\fR limitations).
+Commanded value.  When \fBvalue\fR = 0.0, duty cycle is 0%, and when \fBvalue\fR = \(+-\fBscale\fR, duty cycle is \(+- 100% (subject to \fBmin\-dc\fR and \fBmax\-dc\fR limitations).
 .TP
 \fBpwmgen.\fIN\fB.pwm\fR bit out (output types 0 and 1 only)
 PWM/PDM waveform.
@@ -69,8 +66,7 @@ Range is from \-1.0 to +1.0.
 .TP
 \fBpwmgen.\fIN\fB.max\-dc\fR float in/out
 The maximum duty cycle.  A value of 1.0 corresponds to 100%.
-This can be useful when using transistor drivers with bootstrapped power supplies,
-since the supply requires some low time to recharge.
+This can be useful when using transistor drivers with bootstrapped power supplies, since the supply requires some low time to recharge.
 .TP
 \fBpwmgen.\fIN\fB.min\-dc\fR float in/out
 The minimum duty cycle.  A value of 1.0 corresponds to 100%.
@@ -95,6 +91,5 @@ Because software-generated PWM uses a fairly slow timebase (several to many micr
 For example, if \fBmake\-pulses\fR is called at a 20 kHz rate, and \fBpwm\-freq\fR is 2 kHz, there are only 10 possible duty cycles.
 If \fBdither\-pwm\fR is false, the commanded duty cycle will be rounded to the nearest of those values.
 Assuming \fBvalue\fR remains constant, the same output will repeat every PWM cycle.
-If \fBdither\-pwm\fR is true, the output duty cycle will be dithered between the two closest values,
-so that the long-term average is closer to the desired level.
+If \fBdither\-pwm\fR is true, the output duty cycle will be dithered between the two closest values, so that the long-term average is closer to the desired level.
 \fBdither\-pwm\fR has no effect if \fBpwm\-freq\fR is zero (PDM mode), since PDM is an inherently dithered process.

docs/src/gui/qtdragon.adoc

@@ -46,9 +46,8 @@ It will work in window mode on any monitor with higher resolution but not on mon
 
 == Getting Started - The INI File
 
-If your configuration is not currently set up to use QtDragon,
-you can change it by editing the INI file sections.
-For an exhaustive list of options, see the <<sub:ini:sec:display,display section>> of INI file documentation.
+If your configuration is not currently set up to use QtDragon, you can change it by editing the INI file sections.
+For an exhaustive list of options, see the <<sub:ini:sec:display,display section>> of the INI file documentation.
 
 [NOTE]
 You can only have one of each section ( ie [HAL] ) in the INI file. If you see in these docs multiple section options
@@ -444,7 +443,7 @@ qtdragon.led-probe
 
 These pins are inputs related to spindle VFD indicating. +
 The volt and amp pins are used to calculate spindle power.
-(You must also set the MAX_SPINDLE_POWER in the INI.)
+You must also set the MAX_SPINDLE_POWER in the INI.
 
 [source,{hal}]
 ----
@@ -584,8 +583,7 @@ It uses a HAL non-realtime component which utilizes the external offsets feature
 The component has a HAL pin that specifies an interpolation type, which must be one of cubic, linear or nearest (0, 1, 2 respectively).
 If none is specified or if an invalid number is specified, the default is assumed to be cubic.
 
-When Z LEVEL COMP is enabled, the compensation component reads a probe data file,
-which must be called 'probe_points.txt'.
+When Z LEVEL COMP is enabled, the compensation component reads a probe data file, which must be called 'probe_points.txt'.
 The file can be modified or updated at any time while compensation is disabled.
 When next enabled, the file will be reread and the compensation map is recalculated.
 This file is expected to be in the configuration directory.
@@ -683,8 +681,11 @@ then the tool is lowered until it touches the plate, triggering the probe signal
 Z0 is set to probe height - plate thickness.
 
 The second method uses a tool setter in a fixed position and a known height above the table where the probe signal will be triggered.
-In order to set Z0 to the top of the workpiece, it has to know how far above the table the probe trigger point is (tool setter height).
-and how far above the table the top of the workpiece is.
+In order to set Z0 to the top of the workpiece, it has to know
+
+ . how far above the table the probe trigger point is (tool setter height) and
+ . how far above the table the top of the workpiece is.
+ 
 This operation has to be done every time the tool is changed as the tool length is not saved.
 
 For touching off with a touch probe, whether you use the touchplate operation with thickness set to 0 or use a probing routine,

docs/src/gui/qtvcp-widgets.adoc

@@ -2549,7 +2549,7 @@ def _releasedOutput(self, btncode):
     self['joy_{}_pressed'.format(btncode.lower())].emit(False)
 ----
 
-As coded they these function _issue (emit) PyQt5 signals (joy_btn_pressed and joy_<letter>_pressed) for the any button pressed or released_.
+As coded these function _issue (emit) PyQt5 signals (joy_btn_pressed and joy_<letter>_pressed) for the any button pressed or released_.
 
 Signal 'joy_btn_pressed' outputs a string code for the button. +
 Signal 'joy_<letter>_pressed' outputs a bool value.