docs: whatever was noticed while translating

Author: smoe

docs/src/config/python-interface.adoc

@@ -321,7 +321,8 @@ see <<python:reading-ini-values,ReadingINI file values>> for an example.
 *settings*:: '(returns tuple of floats)' -
   current interpreter settings: +
   settings[0] = sequence number, +
-  settings[1] = feed rate, settings[2] = speed, +
+  settings[1] = feed rate, +
+  settings[2] = speed, +
   settings[3] = `G64 P` blend tolerance, +
   settings[4] = `G64 Q` naive CAM tolerance.
 

docs/src/gcode/coordinates.adoc

@@ -148,7 +148,7 @@ command would not have been modal and any commands issued after it would
 have returned to using the G55 offsets because that coordinate system
 would still be in effect.
 
-[source,{ngc}]
+[source,{ngc}](((G54)))(((G55)))(((G56)))(((G57)))(((G58)))(((G59)))(((G59.1)))(((G59.2)))(((G59.3)))
 ----
 G54	uses parameters of coordinate system 1
 G55	uses parameters of coordinate system 2

docs/src/gui/gui-dev-reference.adoc

@@ -12,18 +12,17 @@
 :css: {basebackend@docbook:'':css}
 
 This document attempts to be a 'best practices' reference for general use screen development. +
-While it's possible to program just about anything to work with linuxcnc, using common frame work,
- language and configuration requirements allows easier transition between screens and more developers 
-to maintain them. +
+While it is possible to program just about anything to work with LinuxCNC, using a common frame work,
+language and configuration requirements allows easier transition between screens and more developers to maintain them. +
 That said, nothing in this document is written in stone.
 
 == Language
-Python is currently the preferred language of linuxcnc's screen code. +
+Python is currently the preferred language of LinuxCNC's screen code. +
 Python has a low entry bar for new users to modify the screens to suit them. +
-Python has a rich array of documentation, tutorials and libraries to pull from. + 
-It is already used and integrated into linuxcnc's system requirements. +
+Python has a rich array of documentation, tutorials and libraries to pull from. +
+It is already used and integrated into LinuxCNC's system requirements. +
 While C or C\++ could be used, it severely limits who can maintain and develop them. +
-It would be better to extend python with C/C++ modules for whatever function that requires it.
+It would be better to extend Python with C/C++ modules for whatever function that requires it.
 
 == Localization of float numbers in GUIs
 Different locales use different decimal separators and thousands separators. Locale-specific
@@ -37,16 +36,16 @@ are suggested if parsing float to string and vice-versa:
 
 == Basic Configuration
 Currently, most screens use a combination of INI file and preference file entries to configure their functions. +
-INi text files are usually used for the common machine controller settings, while text based preference files 
+INI text files are usually used for the common machine controller settings, while text based preference files
 are used for more GUI related properties (such as sounds, size, colors). +
-There can be other files used for translations, stylizing and function customization. These are highly dependent 
+There can be other files used for translations, stylizing and function customization. These are highly dependent
 on the underlying widget toolkit.
 
 === INI [DISPLAY]
 The *[DISPLAY]* section of the INI is for specifying screen related settings. +
 
 ==== Display
-The most important of is specifying the name of the screen that the linuxcnc script will use to load. +
+The most important of is specifying the name of the screen that the LinuxCNC script will use to load. +
 The screen program usually recognizes switches such as to set full screen. +
 Title is for the window title and icon is used for iconizing the window.
 
@@ -93,7 +92,7 @@ ANGULAR_INCREMENTS = continuous, .5, 1, 45, 90, 360
 ----
 
 ==== Machine Type Hint
-The screen often needs to be adjusted based on machine type. Lathes have different controls and display DROs 
+The screen often needs to be adjusted based on machine type. Lathes have different controls and display DROs
 differently. Foam machine display the plot differently. +
 The old way to do this was adding switches LATHE = 1, FOAM = 1 etc
 
@@ -124,15 +123,15 @@ DEFAULT_LINEAR_VELOCITY =
 MIN_LINEAR_VELOCITY =
 MAX_LINEAR_VELOCITY =
 
-DEFAULT_ANGULAR_VELOCITY = 
-MIN_ANGULAR_VELOCITY = 
-MAX_ANGULAR_VELOCITY = 
+DEFAULT_ANGULAR_VELOCITY =
+MIN_ANGULAR_VELOCITY =
+MAX_ANGULAR_VELOCITY =
 ----
 
 ==== Spindle Manual Controls
 Manual controls for spindle control could be, (or a combinations of) buttons, sliders or dials +
 You can set limits that are less then the what the machine controller can utilize by setting these entries. +
-If your screen is capable of running multiple spindles, then should accept entries higher then the shown '_0_'
+If your screen is capable of running multiple spindles, then should accept entries higher then the shown '_0_'.
 
 [source,{ini}]
 ----
@@ -156,8 +155,8 @@ MDI_COMMAND_MACRO1 = G53 G0 Z0;G53 G0 X0 Y0,Goto\nMachn\nZero
 ----
 
 === INI [FILTER]
-This section allows setting of what files are shown in the file chooser and 
-what filter programs will preprocess its output before sending it to linuxcnc. +
+This section allows setting of what files are shown in the file chooser and
+what filter programs will preprocess its output before sending it to LinuxCNC. +
 The extensions follow this pattern: +
 PROGRAM_EXTENSION = .extension,.extension2[space]Description of extensions +
 The filter program definitions are such: +
@@ -179,7 +178,7 @@ py = python3
 ----
 
 === INI [HAL]
-Most screens will need some HAL pins. They need to be connected after the screen creates them.+
+Most screens will need some HAL pins. They need to be connected after the screen creates them.
 
 ==== Postgui Halfile
 These files should be run one after another in order, after all the GUI HAL pins have been made.
@@ -204,8 +203,8 @@ POSTGUI_HALCMD = loadusr halmeter
 == Extended Configuration
 
 === Embedding GUI Elements
-Allowing users to build small panels independently, that can be embedded into the main screen 
-is a common and very useful customization. Some screens allow embedding of 3rd party foreign programs, 
+Allowing users to build small panels independently, that can be embedded into the main screen
+is a common and very useful customization. Some screens allow embedding of 3rd party foreign programs,
 others only the native widget toolkit based panels. +
 Usually these are embedded in tabs or side panel widgets. +
 This is how to describe the optional title, loading command and location widget name: +
@@ -233,7 +232,7 @@ MESSAGE_ICON = INFO
 ----
 
 This style gives multiple messages defined by a number. +
-This example shows 3 possible messages based around a VFD error nuumber.
+This example shows 3 possible messages based around a VFD error number.
 
 [source,{ini}]
 ----

docs/src/gui/qtvcp-libraries.adoc

@@ -652,7 +652,7 @@ as the widgets get a reference to the `MainWindow` from the `_hal_init()` functi
 from qtvcp.qt_makegui import VCPWindow
 ----
 
-* *Instantiate `VCPWindow` module*+
+* *Instantiate `VCPWindow` module* +
   Add this Python code to your instantiate section:
 +
 [source,python]

docs/src/gui/qtvcp-vismach.adoc

@@ -309,7 +309,7 @@ Either by adding the component object as the first variable and substituting the
 by substituting the full component/pinname string for a coordinate. +
 
 This example creates a _rectangular prism with opposite corners_ at the specified positions and edges parallel to the XYZ axes. +
-the Z start coordinate will be controlled by the HAL pin 'Zstart'
+The Z start coordinate will be controlled by the HAL pin 'Zstart'.
 
 [source,python]
 ----

docs/src/gui/qtvcp.adoc

@@ -974,8 +974,8 @@ If QtVCP finds these it will call them, if not it will silently ignore them.
   _Class patching_, also known as _monkey patching_, allows to *override function calls in an imported module*. +
   Class patching must be done _before the module is instantiated_, and it _modifies all instances_ made after that. +
   An example might be patching button calls from the G-code editor to call functions in the handler file instead. +
-  Class patching function redefined here, will be called with the HandlerClass instance as 'self' rather then +
-  the patched class instance. This can make access to the patched class function/variables more difficult. +
+  Class patching function redefined here, will be called with the HandlerClass instance as 'self' rather than the patched class instance.
+  This can make access to the patched class function/variables more difficult. +
   When class patching outside of the HandlerClass class, the function call will use the patched class instance as 'self'. 
 
 *`initialized__(self):`*::

docs/src/man/man9/hostmot2.9.adoc

@@ -477,13 +477,12 @@ There is a limit of 64 bits in total.
 
 The valid format characters and the pins they create are:
 
-p: (Pad)::
- Does not create any pins, used to ignore sections of the bit stream that are not required.
+p: (Pad):: Does not create any pins, used to ignore sections of the bit stream that are not required.
 
-b: (Boolean).:: (bit, out) hm2_XXXX.N.ssi.MM.<name>.
- If any bits in the designated field width are non-zero then the HAL pin will be "True".
- (bit, out) hm2_XXXX.N.ssi.MM.<name>-not. An inverted version of the above, the
- HAL pin will be "True" if all bits in the field are zero.
+b: (Boolean).:: (bit, out) hm2_XXXX.N.ssi.MM.<name>. +
+ If any bits in the designated field width are non-zero then the HAL pin will be "True". +
+ (bit, out) hm2_XXXX.N.ssi.MM.<name>-not. +
+ An inverted version of the above, the HAL pin will be "True" if all bits in the field are zero.
 
 u: (Unsigned):: (float, out) hm2_XXXX.N.ssi.MM.<name>.
  The value of the bits
@@ -492,35 +491,26 @@ u: (Unsigned):: (float, out) hm2_XXXX.N.ssi.MM.<name>.
  example if the field is 8 bits wide and the scalmax parameter was 20
  then a value of 255 would return 20, and 0 would return 0.
 
-s: (Signed):: (float, out) hm2_XXXX.N.ssi.MM.<name>.
- The value of the bits
- interpreted as a 2s complement signed number then scaled similarly to
+s: (Signed):: (float, out) hm2_XXXX.N.ssi.MM.<name>. +
+ The value of the bits interpreted as a 2s complement signed number then scaled similarly to
  the unsigned variant, except symmetrical around zero.
 
-f: (bitField):: (bit, out) hm2_XXXX.N.ssi.MM.<name>-NN.
- The value of each individual
- bit in the data field. NN starts at 00 up to the number of bits in the
- field. (bit, out) hm2_XXXX.N.ssi.MM.<name>-NN-not. An inverted version
- of the individual bit values.
-
-e: (Encoder):: (s32, out) hm2_XXXX.N.ssi.MM.<name>.count.
-The lower 32 bits of the
- total encoder counts. This value is reset both by the ...reset and the
- ...index-enable pins. (s32, out) hm2_XXXX.N.ssi.MM.<name>.rawcounts.
- The lower 32 bits of the total encoder counts. The pin is not affected
- by reset and index. (float, out) hm2_XXXX.N.ssi.MM.<name>.position.
- The encoder position in machine units. This is calculated from the
- full 64-bit buffers so will show a True value even after the counts
- pins have wrapped. It is zeroed by reset and index enable. (bit, IO)
- hm2_XXXX.N.ssi.MM.<name>.index-enable. When this pin is set "True" the
- module will wait until the raw encoder counts next passes through an
- integer multiple of the number of counts specified by counts-per-rev
- parameter and then it will zero the counts and position pins, and set
- the index-enable pin back to "False" as a signal to the system that
- "index" has been passed. this pin is used for spindle-synchronised
- motion and index-homing. (bit, in) (bit, out)
- hm2_XXXX.N.ssi.MM.<name>.reset. When this pin is set high the counts
- and position pins are zeroed.
+f: (bitField):: (bit, out) hm2_XXXX.N.ssi.MM.<name>-NN. +
+ The value of each individual bit in the data field.
+ NN starts at 00 up to the number of bits in the field. +
+ (bit, out) hm2_XXXX.N.ssi.MM.<name>-NN-not. +
+ An inverted version of the individual bit values.
+
+e: (Encoder):: (s32, out) hm2_XXXX.N.ssi.MM.<name>.count. +
+ The lower 32 bits of the total encoder counts. This value is reset both by the ...reset and the ...index-enable pins. +
+ (s32, out) hm2_XXXX.N.ssi.MM.<name>.rawcounts. +
+ The lower 32 bits of the total encoder counts. The pin is not affected by reset and index. +
+ (float, out) hm2_XXXX.N.ssi.MM.<name>.position. +
+ The encoder position in machine units. This is calculated from the full 64-bit buffers so will show a True value even after the counts pins have wrapped.  It is zeroed by reset and index enable. +
+ (bit, IO) hm2_XXXX.N.ssi.MM.<name>.index-enable. +
+ When this pin is set "True" the module will wait until the raw encoder counts next passes through an integer multiple of the number of counts specified by counts-per-rev parameter and then it will zero the counts and position pins, and set the index-enable pin back to "False" as a signal to the system that "index" has been passed. this pin is used for spindle-synchronised motion and index-homing. +
+ (bit, in) (bit, out) hm2_XXXX.N.ssi.MM.<name>.reset. +
+ When this pin is set high the counts and position pins are zeroed.
 h: (Split encoder, high-order bits)::
  Some encoders (Including Fanuc) place the encoder part-turn counts and
  full-turn counts in separate, non-contiguous fields. This tag defines
@@ -545,11 +535,10 @@ m: (Multi-turn)::
 Two parameters are universally created for all SSI instances
 
 hm2_XXXX.N.ssi.MM.frequency-khz (float r/w)::
- This parameter sets the SSI clock frequency. The units are kHz, so 500
- will give a clock frequency of 500,000 Hz.
+ This parameter sets the SSI clock frequency. The units are kHz, so 500 will give a clock frequency of 500,000 Hz.
 hm2_XXXX.N.ssi.timer-number-num (s32 r/w)::
- This parameter allocates the SSI module to a specific hm2dpll timer
- instance. This pin is only of use in firmwares which contain a hm2dpll
+ This parameter allocates the SSI module to a specific hm2dpll timer instance.
+ This pin is only of use in firmwares which contain a hm2dpll
  function and will default to 1 in cases where there is such a
  function, and 0 if there is not. The pin can be used to disable reads
  of the encoder, by setting to a nonexistent timer number, or to 0.