More changes triggered while translating.

Author: smoe

docs/src/config/pncconf.adoc

@@ -149,7 +149,7 @@ search' button. This pops up the help output page with a list of all the PCI
 devices that can be found. In there should be a reference to a parallel port
 device with a list of addresses. One of those addresses should work. Not all
 PCI parallel ports work properly. Either type can be selected as 'in' (maximum
-amount of input pins) or 'out' (maximum amount of output pins)
+amount of input pins) or 'out' (maximum amount of output pins).
 
 GUI Front-end list::
 This specifies the graphical display screens LinuxCNC will use.
@@ -337,7 +337,7 @@ Defaults and Options::
    this checkbox.
 * Popup Tool Prompt
 ** Choose between an on screen prompt for tool changes or export standard signal
-   names for a User supplied custom tool changer Hal file
+   names for a User supplied custom tool changer HAL file
 * Leave spindle on during tool change:
 ** Used for lathes
 * Force individual manual homing
@@ -824,15 +824,15 @@ The first selection is components that pncconf uses internally.
 You may configure pncconf to load extra instances of the components for your
 custom HAL file.
 
-Select the number of instances your custom file will need, pncconf will add
+Select the number of instances your custom file will need, PnCconf will add
 what it needs after them.
 
-Meaning if you need 2 and pncconf needs 1 pncconf will load 3 instances and use
+Meaning if you need 2 and PnCconf needs 1 PnCconf will load 3 instances and use
 the last one.
 
 Custom Component Commands::
 
-This selection will allow you to load HAL components that pncconf does not use.
+This selection will allow you to load HAL components that PnCconf does not use.
 Add the loadrt or loadusr command, under the heading 'loading command'
 Add the addf command under the heading 'Thread command'.
 The components will be added to the thread between reading of inputs and writing
@@ -887,7 +887,7 @@ have the option to move them around later.
 
 Custom Signal Names::
 
-The Hal Components page can be used to load components needed by a user for
+The HAL Components page can be used to load components needed by a user for
 customization.
 
 Loading Custom Firmware::
@@ -900,8 +900,9 @@ to PnCconf's preference file. By default this path searches the desktop for
 a folder named custom_firmware and a file named firmware.py.
 
 The hidden preference file is in the user's home file, is
-named .pncconf-preferences and require one to select 'show hidden files' to see
-and edit it. The contents of this file can be seen when you first load PnCconf -
+named .pncconf-preferences and require one to select 'show hidden files' in your
+file manager to see and edit it or on the command line you use 'ls' with the '-a' option.
+The contents of this file can be seen when you first load PnCconf -
 press the help button and look at the output page.
 
 Ask on the LinuxCNC mail-list or forum for info about converting custom firmware.

docs/src/config/python-interface.adoc

@@ -126,7 +126,7 @@ machine angular units per deg, reflects [TRAJ]ANGULAR_UNITS INI value.
   currently executing command.
 
 *current_line*:: '(returns integer)' -
-  currently executing line, int.
+  currently executing line.
 
 *current_vel*:: '(returns float)' -
   current velocity in user units per second.

docs/src/config/stepconf.adoc

@@ -71,7 +71,7 @@ image::images/stepconf-base_en.png["Basic Information Page",align="center"]
   Otherwise, select 'Other' and find the timing values in your
   driver's data sheet and enter them as 'nano seconds' in the 'Driver Timing Settings'.
   If the data sheet gives a value in microseconds, multiply by 1000.
-  For example, enter 4.5us as 4500ns.
+  For example, enter 4.5 µs as 4500 ns.
 +
 A list of some popular drives, along with their timing values, is on the
 LinuxCNC.org Wiki under
@@ -152,7 +152,7 @@ with software stepping. If the max latency is more like 30-50
 microseconds, you can still get good results, but your maximum step
 rate might be a little disappointing, especially if you use
 microstepping or have very fine pitch leadscrews. If the numbers are
-100 us  or more (100,000 nanoseconds), then the PC is not a good
+100 µs  or more (100,000 nanoseconds), then the PC is not a good
 candidate for software stepping. Numbers over 1 millisecond (1,000,000
 nanoseconds) mean the PC is not a good candidate for LinuxCNC, regardless of
 whether you use software stepping or not.
@@ -231,7 +231,7 @@ image::images/stepconf-axis-x_en.png["Axis X Configuration Page",align="center"]
   Information computed based on the values entered above.
   The greatest 'Pulse rate at max speed' determines the 'BASE_PERIOD'.
   Values above 20000Hz may lead to slow response time or even lockups (the fastest usable pulse rate varies from computer to computer)
-* 'Axis SCALE' - The number that will be used in the ini file [SCALE] setting.
+* 'Axis SCALE' - The number that will be used in the INI file [SCALE] setting.
   This is how many steps per user unit.
 * 'Test this axis' - (((Test this axis)))
   This will open a window to allow testing for each axis. This can be used after filling out all the information for this axis.
@@ -375,8 +375,8 @@ For 'Speed' enter the measured speed, and for 'PWM' enter the S-number divided b
 Because most spindle drivers are somewhat nonlinear in their response
 curves, it is best to:
 
-- Make sure the two calibration speeds are not too close together in RPM
-- Make sure the two calibration speeds are in the range of speeds you will typically use while milling
+- Make sure the two calibration speeds are not too close together in RPM.
+- Make sure the two calibration speeds are in the range of speeds you will typically use while milling.
 
 For instance, if your spindle will go from 0 RPM to 8000 RPM,
 but you generally use speeds from 400 RPM (10%) to 4000 RPM (100%),
@@ -389,7 +389,7 @@ image::images/stepconf-options_en.png["Advanced Options Configuration",align="ce
 
 * 'Include Halui' - This will add the Halui user interface component. See the
   <<cha:hal-user-interface,HALUI Chapter>> for more information on.
-* 'Include pyVCP' - This option adds the pyVCP panel base file or a sample file
+* 'Include PyVCP' - This option adds the PyVCP panel base file or a sample file
   to work on. See the <<cha:pyvcp,PyVCP Chapter>> for more information.
 * 'Include ClassicLadder PLC' - This option will add the ClassicLadder PLC
   (Programmable Logic Controller). See the

docs/src/drivers/hostmot2.adoc

@@ -479,7 +479,7 @@ The stepgen representation is modeled on the stepgen software
 component. Stepgen default is active high step output (high during step
 time low during step space). To invert a StepGen output pin you invert
 the corresponding GPIO pin that is being used by StepGen. To find the
-GPIO pin being used for the StepGen output run dmesg as shown above.
+GPIO pin being used for the StepGen output run 'dmesg' as shown above.
 
 Each stepgen instance has the following pins and parameters:
 
@@ -542,7 +542,7 @@ Each stepgen instance has the following pins and parameters:
 
 The Step and Direction pins of each StepGen have two additional
 parameters. To find which I/O pin belongs to which step and direction
-output run dmesg as described above.
+output run 'dmesg' as described above.
 
 * 'invert_output' - (Bit, RW) This parameter only has an effect if the
   'is_output' parameter is true.
@@ -571,7 +571,7 @@ number. There are 'num_pwmgens' instances, starting with 00.
 In HM2, each pwmgen uses three output I/O pins: Not-Enable, Out0, and
 Out1. To invert a PWMGen output pin you invert the corresponding GPIO
 pin that is being used by PWMGen. To find the GPIO pin being used for
-the PWMGen output run dmesg as shown above.
+the PWMGen output run 'dmesg' as shown above.
 
 The function of the Out0 and Out1 I/O pins varies with output-type
 parameter (see below).
@@ -639,7 +639,7 @@ component. Each pwmgen instance has the following pins and parameters:
 === Output Parameters
 
 The output pins of each PWMGen have two additional parameters. To find
-which I/O pin belongs to which output run dmesg as described above.
+which I/O pin belongs to which output run 'dmesg' as described above.
 
 * 'invert_output' - (Bit, RW) This parameter only has an effect if the
   'is_output' parameter is true. If this parameter is true, the output
@@ -822,7 +822,7 @@ load. The examples are a good place to start and will save you time.
 Just pick the proper example from the LinuxCNC Configuration Selector and
 save a copy to your computer so you can edit it. To see the exact pins
 and parameters that your configuration gave you, open the Show HAL
-Configuration window from the Machine menu, or do dmesg as outlined
+Configuration window from the Machine menu, or do 'dmesg' as outlined
 above.
 
 // vim: set syntax=asciidoc:

docs/src/drivers/mb2hal.adoc

@@ -23,7 +23,7 @@ device:
 . Now there is a third option that consists of a "generic" driver
   configured by text file, this is called MB2HAL.
 
-Why MB2HAL ?
+Why MB2HAL?
 Consider using Mb2hal if:
 
 * You have to write a new driver and you don't know anything about
@@ -108,7 +108,7 @@ One of: even, odd, none. Ignored if `LINK_TYPE=tcp`.
 |`SERIAL_STOP`    | Integer | If `LINK_TYPE=serial` | Stop bits.
 One of 1, 2. Ignored if `LINK_TYPE=tcp`.
 |`SERIAL_DELAY_MS`| Integer | If `LINK_TYPE=serial` | Serial port delay
-in ms between transactions of this section only.
+between transactions of this section only.
 In ms. Defaults to 0. Ignored if `LINK_TYPE=tcp`.
 |`MB_SLAVE_ID`    | Integer | Yes | Modbus slave number.
 |`FIRST_ELEMENT`  | Integer | Yes | The first element address.
@@ -164,32 +164,18 @@ correspond to:
 
 Modbus protocol exceptions:
 
-* 0x01 - ILLEGAL_FUNCTION        - the FUNCTION code received in the
-  query is not allowed or invalid.
-* 0x02 - ILLEGAL_DATA_ADDRESS    - the DATA ADDRESS received in the
-                                   query is not an allowable address for
-                                   the slave or is invalid.
-* 0x03 - ILLEGAL_DATA_VALUE      - a VALUE contained in the data query
-                                   field is not an allowable value or is
-                                   invalid.
-* 0x04 - SLAVE_DEVICE_FAILURE    - SLAVE (or MASTER) device unrecoverable
-                                   FAILURE while attempting to perform
-                                   the requested action.
+* 0x01 - ILLEGAL_FUNCTION        - the FUNCTION code received in the query is not allowed or invalid.
+* 0x02 - ILLEGAL_DATA_ADDRESS    - the DATA ADDRESS received in the query is not an allowable address for the slave or is invalid.
+* 0x03 - ILLEGAL_DATA_VALUE      - a VALUE contained in the data query field is not an allowable value or is invalid.
+* 0x04 - SLAVE_DEVICE_FAILURE    - SLAVE (or MASTER) device unrecoverable FAILURE while attempting to perform the requested action.
 * 0x04 - SERVER_FAILURE          - (see above).
-* 0x05 - ACKNOWLEDGE             - This response is returned to
-                                   PREVENT A TIMEOUT in the master.
-                                   A long duration of time is required
-                                   to process the request in the slave.
-* 0x06 - SLAVE_DEVICE_BUSY       - The slave (or server) is BUSY.
-                                   Retransmit the request later.
+* 0x05 - ACKNOWLEDGE             - This response is returned to PREVENT A TIMEOUT in the master. A long duration of time is required to process the request in the slave.
+* 0x06 - SLAVE_DEVICE_BUSY       - The slave (or server) is BUSY.  Retransmit the request later.
 * 0x06 - SERVER_BUSY             - (see above).
-* 0x07 - NEGATIVE_ACKNOWLEDGE    - Unsuccessful programming request
-                                   using function code 13 or 14.
+* 0x07 - NEGATIVE_ACKNOWLEDGE    - Unsuccessful programming request using function code 13 or 14.
 * 0x08 - MEMORY_PARITY_ERROR     - SLAVE parity error in MEMORY.
 * 0x0A (-10) - GATEWAY_PROBLEM_PATH   - Gateway path(s) not available.
-* 0x0B (-11) - GATEWAY_PROBLEM_TARGET - The target device failed to
-                                        respond (generated by master,
-                                        not slave).
+* 0x0B (-11) - GATEWAY_PROBLEM_TARGET - The target device failed to respond (generated by master, not slave).
 
 Program or connection:
 

docs/src/drivers/opto22.adoc

@@ -140,13 +140,14 @@ designating it as a HEX number).
 
 Another example: To set the port for 8 outputs and 16 inputs (the
 same as a Mesa card). Here is the 24 bits represented in a BINARY
-number. Bit 1 is the rightmost number.
+number. Bit 1 is the rightmost number:
 
-  000000000000000011111111
-
-16 zeros for the 16 inputs and 8 ones for the 8 outputs
+.16 zeros for the 16 inputs and 8 ones for the 8 outputs
+----
+000000000000000011111111
+----
 
-Which converts to FF on the calculator so 0xff is the number to use
+This converts to FF on the calculator, so 0xff is the number to use
 for portconfig0 and/or portconfig1 when loading the driver.
 
 == Pin Numbering