docs: More changes while revisiting translations

Author: smoe

docs/src/gui/qtvcp-vismach.adoc

@@ -438,7 +438,8 @@ Z = Color([0, 0, 1, 1], [Z])
 origin = Collection([X,Y,Z])
 ----
 
- Add it to the Window class Collection so it is never moved from the origin.
+Add it to the Window class Collection so it is never moved from the origin.
+
 [source,python]
 ----
 v.model = Collection([origin, model, world])

docs/src/gui/qtvcp.adoc

@@ -133,7 +133,6 @@ All `<options>` must appear before `<screen_name>`.
 If `<screen_name>` is missing, the default screen will be loaded.
 
 QtVCP assumes the UI file and the handler file use the *same base name*.
-
 QtVCP will first search the LinuxCNC configuration directory that was launched for the files, then in the system skin folder holding standard screens.
 
 .Cycle Times
@@ -146,13 +145,12 @@ GRAPHICS_CYCLE_TIME = 100
 HALPIN_CYCLE = 100
 ----
 
-Adjusts the response rate of the GUI updates in milliseconds. +
+Adjusts the response rate of the GUI updates in milliseconds.
 Defaults to 100, useable range 50 - 200.
 
 The widgets, graphics and HAL pin update can be set separately.
 
-If the update time is not set right the screen can become unresponsive
-or very jerky.
+If the update time is not set right the screen can become unresponsive or very jerky.
 
 === Qt Designer UI File
 
@@ -169,7 +167,7 @@ A handler file is a file containing _Python_ code, which *adds to QtVCP default
 A handler file allows one to _modify defaults_, or _add logic_ to a QtVCP screen without having to modify QtVCP's core code.
 In this way you can have *custom behaviors*.
 
-If present a handler file will be loaded. +
+If present a handler file will be loaded.
 *Only one file* is allowed.
 
 === Libraries Modules
@@ -178,7 +176,8 @@ QtVCP, as built, does little more than display the screen and react to widgets.
 For more *prebuilt behaviors* there are available libraries (found in `lib/python/qtvcp/lib` in RIP LinuxCNC install).
 
 *Libraries* are prebuilt _Python modules_ that *add features* to QtVCP.
-In this way you can select what features you want - yet don't have to build common ones yourself. +
+In this way you can select what features you want - yet don't have to build common ones yourself.
+
 Such libraries include:
 
 * `audio_player`
@@ -227,8 +226,8 @@ In that folder, QtVCP will load any of the available following files:
 There are _three ways_ to customize a screen/panel.
 
 .Minor StyleSheet Changes
-Stylesheets can be used to *set Qt properties*. +
-If a widget uses properties they usually can be modified by stylesheets.
+Stylesheets can be used to *set Qt properties*.
+If a widget uses properties then they usually can be modified by stylesheets.
 
 .Example of a widget with accompanying style sheet settings.
 [source,{css}]
@@ -260,7 +259,8 @@ The default path is in the configuration directory as a hidden file using the sc
 This file will be read and executed as Python code in the *handler file context*.
 
 *Only local functions and local attributes* can be referenced.
-Global libraries can not be referenced. (usually seen as all capital words with no preceding self.)
+Global libraries can not be referenced.
+These are usually seen as all capital words with no preceding self.
 
 What can be used can vary by screen and development cycle.
 
@@ -299,14 +299,12 @@ There are several *builtin HAL panels* available.
 
 In a terminal type `qtvcp <return>` to see a list:
 
-*`test_panel`*::
-  Collection of useful widgets for testing HAL components, including speech of LED state.
+*`test_panel`*:: Collection of useful widgets for testing HAL components, including speech of LED state.
 +
 .QtVCP HAL Test Builtin Panel
 image::images/qtvcp_test_panel.png["QtVCP HAL Test Builtin Panel",align="center"]
 
-*`cam_align`*::
-  A camera display widget for rotational alignment.
+*`cam_align`*:: A camera display widget for rotational alignment.
 +
 .cam_align - Camera Alignment VCP
 image::images/qtvcp-cam-align.png["Qtscreen x1mill",align="center"]
@@ -318,8 +316,7 @@ image::images/qtvcp-cam-align.png["Qtscreen x1mill",align="center"]
 .QtVCP Sim Builtin Panel
 image::images/qtvcp_sim_panel.png["QtVCP Sim Builtin Panel",align="center"]
 
-*`vismach_mill_xyz`*::
-  3D openGL view of a 3-Axis milling machine.
+*`vismach_mill_xyz`*:: 3D OpenGL view of a 3-axis milling machine.
 +
 .QtVismach - 3-Axis Mill Builtin Panel
 image::images/qtvismach.png["QtVismach - 3-Axis Mill Builtin Panel",align="center"]
@@ -332,6 +329,7 @@ loadusr qtvcp test_panel
 ----
 
 But more typically like this:
+
 [source,{hal}]
 ----
 loadusr -Wn test_panel qtvcp test_panel
@@ -427,8 +425,7 @@ Necesitará privilegios de superusuario para copiar el archivo en la carpeta.
 ////
 
 .Add `qtvcp_plugin.py` link to the Qt Designer Search Path
-Then you must add a link to the `qtvcp_plugin.py` in one of the folders
-that Qt Designer will search into.
+Then you must add a link to the `qtvcp_plugin.py` in one of the folders that Qt Designer will search into.
 
 In a _RIP_ version of LinuxCNC `qtvcp_plugin.py` will be:
 
@@ -499,8 +496,7 @@ On the Object inspector click on the _ScreenOptions_. +
 Then switch to the Property Editor and, under the _ScreenOptions_ heading, toggle *`filedialog_option`*.
 //TODO Explain what this FileDialo_option does
 
-Drag and drop a *`GCodeGraphics`* _widget_ and a *`GcodeEditor`*
-_widget_. +
+Drag and drop a *`GCodeGraphics`* _widget_ and a *`GcodeEditor`* _widget_. +
 Place and resize them as you see fit leaving some room for buttons.
 
 .Add Action Buttons

docs/src/hal/halshow.adoc

@@ -98,7 +98,7 @@ _Reload tree view_ is useful when new components are loaded during runtime and s
 .Halshow: Show Tab
 image::images/halshow-show-tab.png["Halshow: Show Tab",align="center"]
 
-Clicking on the node name in the tree, e.g. "Components", will show you (under the "Show" tab) all that HAL knows about the contents of that node.
+Clicking on the node name, "Components" in the tree for example, will show you (under the "Show" tab) all that HAL knows about the contents of that node.
 Figure <<fig:halshow-show-tab,Halshow Show Tab>> shows a list exactly like you will see if you click the "Components" name.
 The information display is exactly like those shown in traditional text based HAL analysis tools.
 The advantage here is that we have mouse click access, access that can be as broad or as focused as you need.
@@ -152,7 +152,8 @@ _Watch's_ refresh rate is a bit slow to see stepper pulses, but you can use it f
 
 .New in 2.9
 ****
-The pins and signals that are writable have buttons for manipulation on the right side. Pins that are linked to a signal have disabled buttons.
+The pins and signals that are writable have buttons for manipulation on the right side.
+Pins that are linked to a signal have disabled buttons.
 To set these values, the corresponding pin has to be unlinked from the signal.
 That can be done by right-click on the signal name and select "Unlink pin", see <<cap:watch-tab-context-menu,Watch Tach Context Menu>>.
 
@@ -189,8 +190,7 @@ They will persist as long as LinuxCNC remains up but are gone as soon as LinuxCN
 The command entry has a BASH-like history (during the session), so you can restore inserted commands with the arrow up key.
 ****
 
-The entry box labeled "HAL Command:" will accept any of the commands listed for halcmd.
-These include:
+The entry box labeled "HAL Command:" will accept any of the commands listed for halcmd. These include:
 
 - `loadrt`, `unloadrt` (load/unload real-time module)
 - `loadusr`, `unloadusr` (load/unload non-realtime component)
@@ -246,7 +246,7 @@ ID Type        Name
 02 User   iocontrol
 ----
 
-Sure enough there it is. Notice that its ID is 08.
+Sure enough, there it is. Notice that its ID is 08.
 Next we need to find out what functions are available with it so we look at functions:
 
 ----
@@ -265,8 +265,8 @@ Owner  CodeAddr      Arg  FP Users Name
   04   E0B614AD E0DC7448 YES     1 stepgen.update-freq
 ----
 
-Here we look for owner #08 and see a function named ddt.0.
-We should be able to add ddt.0 to the servo thread and it will do its math each time the servo thread is updated.
+Here we look for owner #08 and see a function named `ddt.0`.
+We should be able to add `ddt.0` to the servo thread and it will do its math each time the servo thread is updated.
 Once again we look up the addf command and find that it uses three arguments like this:
 
 [source,{hal}]
@@ -294,7 +294,7 @@ image::images/halshow-2.png["Addf command",align="center"]
 Next we need to connect ddt to something.
 But how do we know what pins are available?
 The answer is to look under pins.
-There we find ddt and see this:
+There we find `ddt` and see this:
 
 ----
 Component Pins: