Merge pull request #2775 from smoe/translation_breaking_po4a

docs: triggered while translating

Author: hansu

docs/src/config/ini-config.adoc

@@ -1295,19 +1295,18 @@ image::images/encoder-scale.png[align="center"]
 
 The _<num>_ specifies the spindle number 0 ... (num_spindles-1) +
 The value of _num_spindles_ is set by `[TRAJ]SPINDLES=` . +
-By default maximum velocity of the spindle in forward and reverse is approximately
-  2147483000 RPM. +
+By default maximum velocity of the spindle in forward and reverse is approximately 2147483000 RPM. +
 By default minimum velocity of the spindle in forward and reverse is 0 RPM. +
 By default the increment is 100 RPM. +
 You change these default by setting the following INI variables:
 
 [NOTE]
-These settings are for the motion controller component. Control screens can limit
- these settings further. 
+These settings are for the motion controller component.
+Control screens can limit these settings further. 
 
 * `MAX_FORWARD_VELOCITY = 20000`
   The maximum spindle speed (in rpm) for the specified spindle. Optional.
-  This will also set MIN_FORWARD_VELOCITY to the negative value unless overridden.
+  This will also set MAX_REVERSE_VELOCITY to the negative value unless overridden.
 * `MIN_FORWARD_VELOCITY = 3000`
   The minimum spindle speed (in rpm) for the specified spindle. Optional.
   Many spindles have a minimum speed below which they should not be run.

docs/src/config/iov2.adoc

@@ -53,18 +53,13 @@ INI file options:
 .[EMCIO] section
 PROTOCOL_VERSION = 2 :: Defaults to 2. Setting to 1 will emulate old iocontrol behaviour.
 
-EMCIO = iov2 -support-start-change :: You need to explicitly enable the start-change protocol by adding the
-  -support-start-change option; otherwise the start-change pin remains
-  low and   start-change-ack is ignored. The reason for this is better
-  backwards compatibility.
+EMCIO = iov2 -support-start-change :: You need to explicitly enable the start-change protocol by adding the -support-start-change option; otherwise the start-change pin remains low and   start-change-ack is ignored. The reason for this is better backwards compatibility.
 
 .[TASK] section
-IO_ERROR :: Printf-style template for operator error display (negative toolchanger fault codes).
-  No quoting needed. Example: `IO_ERROR = Toolchanger fault %d`. Default: toolchanger error %d.
+IO_ERROR :: Printf-style template for operator error display (negative toolchanger fault codes).  No quoting needed. Example: `IO_ERROR = Toolchanger fault %d`. Default: toolchanger error %d.
 
 .[EMC] section +
-DEBUG :: To get a (quite detailed) trace,
-  set either the RCS debugging flag (0x00000200) to turn on RCS debugging messages all over LinuxCNC or use the new iocontrol debugging bit (0x00001000) only for iov2 messages.
+DEBUG :: To get a (quite detailed) trace, set either the RCS debugging flag (0x00000200) to turn on RCS debugging messages all over LinuxCNC or use the new iocontrol debugging bit (0x00001000) only for iov2 messages.
 
 == Pins
 

docs/src/drivers/hal_gpio.adoc

@@ -94,7 +94,7 @@ The version of libgpiod-dev installed can be determined by the command "gpioinfo
 
 * 'hal_gpio.reset' - Only exported if there are pins defined in the reset list. This should be placed after the "write" function, and should be in the same thread.
 
-Typically the 'read' function will be early in the call list, before any encoder counters and the 'write' function will be later in the call list, after stepgen.make-pulses.
+Typically the 'read' function will be early in the call list, before any encoder counters and the 'write' function will be later in the call list, after `stepgen.make-pulses`.
 
 
 == Pin Identification

docs/src/getting-started/running-linuxcnc.adoc

@@ -49,7 +49,7 @@ new users and are organized around supported GUIs:
 * 'qtdragon_hd' - Touch Screen GUI, high definition
 * 'qtplasmac' - Touch Screen GUI, for plasma tables
 * 'qttouchy' - Touch Screen GUI
-* 'tklinuxcnc' - Keyboard and Mouse Gui (no longer maintained)
+* 'tklinuxcnc' - Keyboard and Mouse GUI (no longer maintained)
 * 'touchy' - Touch Screen GUI
 * 'woodpecker' - Touch Screen GUI
 A GUI configuration directory may contain subdirectories with

docs/src/getting-started/updating-linuxcnc.adoc

@@ -197,7 +197,7 @@ Versions of LinuxCNC before 2.9.0 used to handle an incorrect
 `[TASK]INTERPRETER` setting by automatically falling back to using the
 default G-code interpreter.
 
-As of 2.9.0, an incorrect `[TASK]INTERPRETER` value will cause
+Since 2.9.0, an incorrect `[TASK]INTERPRETER` value will cause
 LinuxCNC to refuse to start up.  Fix this condition by deleting the
 `[TASK]INTERPRETER` setting from your INI file, so that LinuxCNC will
 use the default G-code interpreter.

docs/src/gui/gladevcp.adoc

@@ -2817,7 +2817,7 @@ See the getting-started/running-linuxcnc section for 'Adding Configuration Selec
 
 For testing, a runtime specification of auxiliary applications may be specified using the exported environmental variable: GLADEVCP_EXTRAS.
 This variable should be a path list of one or more configuration directories separated by a (:).
-Typically, this variable would be set in a shell starting `linuxcnc` or in a user's `~/.profile startup` script.
+Typically, this variable would be set in a shell starting `linuxcnc` or in a user's `~/.profile` startup script.
 Example:
 
 ----

docs/src/gui/qtdragon.adoc

@@ -72,8 +72,7 @@ DISPLAY = qtvcp qtdragon
 
 To keep track of preferences, QtDragon looks for a preference text file.
 Add the following entry under the `[DISPLAY]` heading. +
-It can use `~` for home directory or `WORKINGFOLDER` or `CONFIGFOLDER`
- to represent QtVCP's idea of those directories: +
+It can use `~` for home directory or `WORKINGFOLDER` or `CONFIGFOLDER` to represent QtVCP's idea of those directories: +
 This example will save the file in the config folder of the launch screen.
 (Other options are possible see the QtVCP's screenoption widget docs.)