docs: More bits spotted while translating.

Author: smoe

docs/src/config/core-components.adoc

@@ -95,8 +95,7 @@ unlock_joints_mask=0x38 selects joints 3,4,5
 [[sec:motion-pins]]
 === Pins(((motion:HAL pins)))
 
-These pins, parameters, and functions are created by the realtime 'motmod'
-module.
+These pins, parameters, and functions are created by the realtime 'motmod' module.
 
 * 'motion.adaptive-feed' - (float, in) When adaptive feed is enabled with 'M52 P1' , the
   commanded velocity is multiplied by this value. This effect is
@@ -109,13 +108,10 @@ module.
   controlled by M67 or M68.
 * 'motion.coord-error' - (bit, out) TRUE when motion has encountered an error, such as
   exceeding a soft limit
-* 'motion.coord-mode' - (bit, out) TRUE when motion is in 'coordinated mode', as opposed to
-  'teleop mode'
+* 'motion.coord-mode' - (bit, out) TRUE when motion is in 'coordinated mode', as opposed to 'teleop mode'
 * 'motion.current-vel' - (float, out) The current tool velocity in user units per second.
-* 'motion.digital-in-00' - (bit, in) These pins (00, 01, 02, 03 or more if configured) are
-  controlled by M62-65.
-* 'motion.digital-out-00' - (bit, out) These pins (00, 01, 02, 03 or more if configured) are
-  controlled by the 'M62-65'.
+* 'motion.digital-in-00' - (bit, in) These pins (00, 01, 02, 03 or more if configured) are controlled by M62-65.
+* 'motion.digital-out-00' - (bit, out) These pins (00, 01, 02, 03 or more if configured) are controlled by the 'M62-65'.
 * 'motion.distance-to-go' - (float,out) The distance remaining in the current move.
 * 'motion.enable' - (bit, in) If this bit is driven FALSE, motion stops, the machine is
   placed in the 'machine off' state, and a message is displayed for the
@@ -147,32 +143,18 @@ module.
 * 'motion.teleop-mode' - (bit, out) TRUE when motion is in 'teleop mode', as opposed to 'coordinated mode'
 * 'motion.tooloffset.x ... motion.tooloffset.w' - (float, out, one per axis) shows the tool offset in effect;
   it could come from the tool table ('G43' active), or it could come from the G-code ('G43.1' active)
-
-* 'motion.on-soft-limit' -
-  (bit, out) TRUE when the machine is on a soft limit.
-* 'motion.probe-input' -
-  (bit, in) 'G38.n'  uses the value on this pin to determine when the
-  probe has made contact.
+* 'motion.on-soft-limit' - (bit, out) TRUE when the machine is on a soft limit.
+* 'motion.probe-input' - (bit, in) 'G38.n'  uses the value on this pin to determine when the probe has made contact.
   TRUE for probe contact closed (touching),
   FALSE for probe contact open.
-* 'motion.program-line' -
-  (s32, out) The current program line while executing. Zero if not
-  running or between lines while single stepping.
-* 'motion.requested-vel' -
-  (float, out) The current requested velocity in user units per
-  second.  This value is the F-word setting from the G-code file,
-  possibly reduced to accommodate machine velocity and acceleration
-  limits. The value on this pin does not reflect the feed override or
-  any other adjustments.
-
-* 'motion.teleop-mode' -
-  (bit, out) TRUE when motion is in 'teleop mode', as opposed to
-  'coordinated mode'
-
-* 'motion.tooloffset.x ... motion.tooloffset.w' -
-  (float, out, one per axis) shows the tool offset in effect;
-  it could come from the tool table ('G43' active), or it could
-  come from the G-code ('G43.1' active)
+* 'motion.program-line' - (s32, out) The current program line while executing.
+  Zero if not running or between lines while single stepping.
+* 'motion.requested-vel' - (float, out) The current requested velocity in user units per second.
+  This value is the F-word setting from the G-code file, possibly reduced to accommodate machine velocity and acceleration limits.
+  The value on this pin does not reflect the feed override or any other adjustments.
+* 'motion.teleop-mode' - (bit, out) TRUE when motion is in 'teleop mode', as opposed to 'coordinated mode'
+* 'motion.tooloffset.x ... motion.tooloffset.w' - (float, out, one per axis) shows the tool offset in effect;
+  it could come from the tool table ('G43' active), or it could come from the G-code ('G43.1' active)
 
 === Parameters
 
@@ -191,10 +173,9 @@ change or removal at any time.
 * 'motion.debug-float-3' - (float, RO) This is used for debugging purposes.
 * 'motion.debug-s32-0' - (s32, RO) This is used for debugging purposes.
 * 'motion.debug-s32-1' - (s32, RO) This is used for debugging purposes.
-* 'motion.servo.last-period' - (u32, RO) The number of CPU cycles between invocations of the servo
-  thread. Typically, this number divided by the CPU speed gives the time
-  in seconds, and can be used to determine whether the realtime motion
-  controller is meeting its timing constraints
+* 'motion.servo.last-period' - (u32, RO) The number of CPU cycles between invocations of the servo thread.
+  Typically, this number divided by the CPU speed gives the time in seconds,
+  and can be used to determine whether the realtime motion controller is meeting its timing constraints
 * 'motion.servo.last-period-ns' - (float, RO)
 
 === Functions
@@ -316,7 +297,7 @@ See the motion man page 'motion(9)' for details on the pins and parameters.
 
 == iocontrol
 
-iocontrol - accepts non-realtime I/O commands via NML, interacts with HAL .
+iocontrol - accepts non-realtime I/O commands via NML, interacts with HAL.
 
 iocontrol's HAL pins are turned on and off in non-realtime context.  If you have strict timing requirements or simply need more I/O, consider using the realtime synchronized I/O provided by <<sec:motion,motion>> instead.
 

docs/src/man/man1/halreport.1.adoc

@@ -12,7 +12,7 @@ halreport - creates a report on the status of the HAL
 
 *halreport*
 
-. Supports components made by halcompile and numerous legacy components
+. Supports components made by halcompile and numerous legacy components.
 . Known unhandled components:
 at_pid:: naming conflicts with pid, seldom used
 boss_plc:: no manpage or docs (any users?)

docs/src/man/man1/halrmt.1.adoc

@@ -12,7 +12,7 @@ halrmt - remote-control interface for LinuxCNC
 
 --port _port_:: Waits for socket connections (telnet) on specified
 socket, without port specification it uses default port 5006.
-(note: linuxcncrsh uses 5007 as default)
+(Note: linuxcncrsh uses 5007 as default.)
 --name _server_name_:: Sets the server name to specified name for Hello.
 --connectpw _password_:: Sets the connection password to 'password'. Default: EMC.
 --enablepw _password_:: Sets the enable password to _password_. Default EMCTOO.

docs/src/man/man1/sim_pin.1.adoc

@@ -21,14 +21,14 @@ supported.
 If the named input is a numerical type, the GUI displays:
 
 *Entry* Entry widget for value or a valid Tcl expression. +
-*Set* Pushbutton to set new value from Entry (or use <RETURN>) +
+*Set* Pushbutton to set new value from Entry (or use <RETURN>). +
 *Reset* Pushbutton to reset to the value present on initiation If the
 input is a *bit* type, the GUI shows a single pushbutton that is
 controlled by radio-button selectors:
 
-mode=**pulse** Pulse input to 1 for each pushbutton press +
-mode=**toggle** Toggle input for each pushbutton press +
-mode=**hold** Set input to 1 while pushbutton pressed
+mode=**pulse** Pulse input to 1 for each pushbutton press. +
+mode=**toggle** Toggle input for each pushbutton press. +
+mode=**hold** Set input to 1 while pushbutton pressed.
 
 If the bit item mode begins with an uppercase letter, the radio buttons
 for selecting other modes are not shown

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

@@ -311,7 +311,7 @@ and the 7I70 during real time process data exchanges. For high speed
 applications, choosing the correct mode can reduced the data transfer
 sizes, resulting in higher maximum update rates.
 
-MODE 0:: Input mode (48 bits input data only
+MODE 0:: Input mode (48 bits input data only)
 MODE 1:: Input plus analog mode (48 bits input data plus 6 channels of analog data)
 MODE 2:: Input plus field voltage
 

docs/src/motion/switchkins.adoc

@@ -311,15 +311,15 @@ requirements.
 
 === External offset considerations 
 
-External offsets (set to an axis (_L_) via axis.L.eoffset-request) are preserved during 
-kinematics switches. When an offset is active on an axis before the switch
-(visible in axis.L.eoffset), the trajectory planner maintains that same 
-offset after the switch, similar to how it maintains the commanded 
-position from a G-code. This ensures consistent machine behavior regardless
-of the active kinematics.
+External offsets (set to an axis (_L_) via axis._L_.eoffset-request)
+are preserved during kinematics switches. When an offset is active on
+an axis before the switch (visible in axis._L_.eoffset), the trajectory
+planner maintains that same offset after the switch, similar to how it
+maintains the commanded position from a G-code. This ensures consistent
+machine behavior regardless of the active kinematics.
 
 If maintaining the offset will be an issue due to axis limit changes or other concerns,
-be sure to clear and possibly disable the eoffset before making a kinematics switch
+be sure to clear and possibly disable the eoffset before making a kinematics switch.
 
 == Simulation configs
 

docs/src/plasma/qtplasmac.adoc

@@ -4109,8 +4109,8 @@ Therefore, the length of the wiggle and the feed rate need to be considered in c
 
 For example:
 
-* A feed rate of 1080 mm/min (18 mm/s)
-* A wiggle movement of 4 mm for 3 oscillations
+* A feed rate of 1080 mm/min (18 mm/s).
+* A wiggle movement of 4 mm for 3 oscillations.
 
 This means that the length of the wiggle is 4 x 3 = 12 mm. At the 18 mm/s feed rate, the pierce delay needs to be approx 0.7 seconds to support the wiggle distance at pierce height.