docs: More smallish changes while revisiting translations.

Author: smoe

docs/man/man9/hostmot2.9

@@ -882,7 +882,7 @@ This would be set to 1.5 ms for 1-2 ms servos for a 0 center position.
 (float rw) scale
 Sets the per channel pulse width scaling.
 For example, setting the scale to 90 and the offset to 1.5 ms would result in a position range of +-45 degrees
-and scale in degrees for 1-2 ms servos with a full motion range of 90 degrees
+and scale in degrees for 1-2 ms servos with a full motion range of 90 degrees.
 
 .SS stepgen
 

docs/man/man9/sserial.9

@@ -272,8 +272,7 @@ This is intended as a speed control signal for a VFD.
 
 \fBParameters:\fR
 
-(bit rw) .7i77.0.0.output\-NN\-invert: Invert the sense of the corresponding
-output pin.
+(bit rw) .7i77.0.0.output\-NN\-invert: Invert the sense of the corresponding output pin.
 
 (bit rw) .7i77.0.0.spindir\-invert: Invert the sense of the spindle direction pin.
 

docs/src/gui/gmoccapy.adoc

@@ -498,7 +498,7 @@ You can specify the log level in the INI file like this:
 [DISPLAY]
 DISPLAY = gmoccapy <log_level_param>
 ----
-using this parameters:
+using these parameters:
 ----
 Log level   <log_level_param>
 DEBUG       -d

docs/src/gui/qtdragon.adoc

@@ -1034,11 +1034,11 @@ One can use this to split the size between the two areas. This can be set differ
 This tab displays the graphical representation of the current program.
 The side buttons will control the display.
 
-* 'User View': Select/restore a user set view of the current program
-* 'P','X','Y','Z': Set standard views
-* 'D': Toggle display of dimensions
-* '+', '-': Zoom controls
-* 'C': Clear graphics of tool movement lines
+* 'User View': Select/restore a user set view of the current program.
+* 'P','X','Y','Z': Set standard views.
+* 'D': Toggle display of dimensions.
+* '+', '-': Zoom controls.
+* 'C': Clear graphics of tool movement lines.
 
 In `qtdragon_hd` there are also macro buttons available on the right side.
 Up to tens buttons can be defined in the INI.

docs/src/gui/qtvcp-widgets.adoc

@@ -2554,7 +2554,7 @@ As coded they these function _issue (emit) PyQt5 signals (joy_btn_pressed and jo
 Signal 'joy_btn_pressed' outputs a string code for the button. +
 Signal 'joy_<letter>_pressed' outputs a bool value.
 
-You could override the functions to do something else if making a custom widget,
+You could override the functions to do something else if making a custom widget:
 
 .Callable Functions
 *`reset_highlight()`*::
@@ -2901,7 +2901,7 @@ If the subroutine calls other subroutines or custom M codes, those paths must be
 SUBROUTINE_PATH = ~/linuxcnc/nc_files/examples/ngcgui_lib:~/linuxcnc/nc_files/examples/ngcgui_lib/utilitysubs
 ----
 
-Qtvcp needs to know where to open subroutines from. +
+QtVCP needs to know where to open subroutines from. +
 You can also specify subroutines to be pre-opened in tabs.
 
 [source,{ini}]
@@ -2928,8 +2928,8 @@ NGCGUI_SUBFILE = qpocket.ngc
 * 'FINALIZE GCODE' -create the full G-code and send it to LinuxCNC/a file
 
 ==== Adding Custom Subroutines
-You can create your own subroutines for use with ngcgui. +
-they must follow these rules:
+You can create your own subroutines for use with ngcgui.
+They must follow these rules:
 
 * For creating a subroutine for use with NGCGUI, the filename and the subroutine name must be the same.
 * The subroutine must be in a folder within LinuxCNC's INI designated search path.

docs/src/plasma/plasma-cnc-primer.adoc

@@ -397,7 +397,7 @@ WARNING: It is strongly recommended that the torch cannot be enabled while this
 
 * Used for surface probing. A sensor or switch that is activated if the torch slides up when it hits the material.
 * Connect Proximity sensor output to chosen input pin. If mechanical switches are used. Connect one side of the switch to field power and the other side of the switch to input.
-* Usually Connected to `motion.probe-input`
+* Usually Connected to `motion.probe-input`.
 
 === Ohmic Sensor enable (output)
 

docs/src/user/user-concepts.adoc

@@ -97,8 +97,7 @@ Naive CAM Detector:: Successive G1 moves that involve only the XYZ axes
   The controlled point will touch at least one point on each movement.
   The machine will never move at such a speed that it cannot come to an exact stop at the end of the current movement
   (or next movement, if you pause when blending has already started).
-  On G2/3 moves in the G17 (XY) plane,
-  when the maximum deviation of an arc from a straight line is less than the G64 Q- tolerance,
+  On G2/3 moves in the G17 (XY) plane, when the maximum deviation of an arc from a straight line is less than the G64 Q- tolerance,
   the arc is broken into two lines (from start of arc to midpoint, and from midpoint to end).
   Those lines are then subject to the naive cam algorithm for lines.
   Thus, line-arc, arc-arc, and arc-line cases as well as line-line benefit from the 'naive cam detector'.
@@ -156,13 +155,13 @@ For a feed rate of 0.5 inch per second, the critical distance is latexmath:[$ \f
 === Defaults
 
 When LinuxCNC first starts up many G- and M-codes are loaded by default.
-The current active G- and M-codes can be viewed on the MDI tab in the 'Active G-Codes:' window in the AXIS interface.
+The current active G- and M-codes can be viewed on the MDI tab in the 'Active G-codes:' window in the AXIS interface.
 These G- and M-codes define the behavior of LinuxCNC and
 it is important that you understand what each one does before running LinuxCNC.
-The defaults can be changed when running a G-Code file and left in a different state than when you started your LinuxCNC session.
-The best practice is to set the defaults needed for the job in the preamble of your G-Code file
+The defaults can be changed when running a G-code file and left in a different state than when you started your LinuxCNC session.
+The best practice is to set the defaults needed for the job in the preamble of your G-code file
 and not assume that the defaults have not changed.
-Printing out the G-Code <<gcode:quick-reference-table,Quick Reference>> page can help you remember what each one is.
+Printing out the G-code <<gcode:quick-reference-table,Quick Reference>> page can help you remember what each one is.
 
 === Feed Rate
 
@@ -171,8 +170,7 @@ Read and understand the <<sub:feed-rate,Feed Rate>> section if you have a rotary
 
 === Tool Radius Offset
 
-Tool Radius Offset (G41/42) requires that the tool be able to touch somewhere along each programmed move
-without gouging the two adjacent moves.
+Tool Radius Offset (G41/42) requires that the tool be able to touch somewhere along each programmed move without gouging the two adjacent moves.
 If that is not possible with the current tool diameter you will get an error.
 A smaller diameter tool may run without an error on the same path.
 This means you can program a cutter to pass down a path that is narrower than the cutter without any errors.
@@ -181,13 +179,11 @@ See the <<sec:cutter-radius-compensation,Cutter Compensation>> section for more
 == Homing
 
 After starting LinuxCNC each axis must be homed prior to running a program or running a MDI command.
-
 If your machine does not have home switches a match mark on each axis can aid in homing the machine coordinates to the same place each time.
-
 Once homed your soft limits that are set in the INI file will be used.
 
 If you want to deviate from the default behavior, or want to use the Mini interface,
-you will need to set the option NO_FORCE_HOMING = 1 in the [TRAJ] section of your INI file.
+you will need to set the option `NO_FORCE_HOMING = 1` in the `[TRAJ]` section of your INI file.
 More information on homing can be found in the Integrator Manual.
 
 == Tool Changes
@@ -214,8 +210,8 @@ Normally you are in the G54 coordinate system.
 === G54-59.3 User Coordinates
 
 Normally you use the G54 Coordinate System.
-When an offset is applied to a current user coordinate system a small blue ball with lines
-will be at the <<sec:machine-coordinate-system, machine origin>> when your DRO is displaying 'Position: Relative Actual' in AXIS.
+When an offset is applied to a current user coordinate system,
+a small blue ball with lines will be at the <<sec:machine-coordinate-system,machine origin>> when your DRO is displaying 'Position: Relative Actual' in AXIS.
 If your offsets are temporary use the Zero Coordinate System from the Machine menu or program 'G10 L2 P1 X0 Y0 Z0' at the end of your G-code file.
 Change the 'P' number to suit the coordinate system you wish to clear the offset in.
 
@@ -224,8 +220,7 @@ Change the 'P' number to suit the coordinate system you wish to clear the offset
 
 === When You Are Lost
 
-If you're having trouble getting 0,0,0 on the DRO when you think you should,
-you may have some offsets programmed in and need to remove them.
+If you're having trouble getting 0,0,0 on the DRO when you think you should, you may have some offsets programmed in and need to remove them.
 
 * Move to the Machine origin with G53 G0 X0 Y0 Z0
 * Clear any G92 offset with G92.1
@@ -234,8 +229,7 @@ you may have some offsets programmed in and need to remove them.
 * Turn off tool offsets with G49
 * Turn on the Relative Coordinate Display from the menu
 
-Now you should be at the machine origin X0 Y0 Z0
-and the relative coordinate system should be the same as the machine coordinate system.
+Now you should be at the machine origin X0 Y0 Z0 and the relative coordinate system should be the same as the machine coordinate system.
 
 [[sec:machine-configurations]]
 == Machine Configurations