More changes performed while translating

Author: smoe

docs/src/drivers/hostmot2.adoc

@@ -225,7 +225,7 @@ The above configuration produced this printout.
 
 [NOTE]
 That the I/O Pin nnn will correspond to the pin number shown on
-the HAL Configuration screen for GPIOs. Some of the Stepgen, Encoder
+the HAL Configuration screen for GPIOs. Some of the StepGen, Encoder
 and PWMGen will also show up as GPIOs in the HAL Configuration screen.
 
 == PIN Files
@@ -465,7 +465,7 @@ GPIO pins default to input.
 
 == StepGen
 
-Stepgens have names like 'hm2_<BoardType>.<BoardNum>.stepgen.<Instance>.'.
+StepGens have names like 'hm2_<BoardType>.<BoardNum>.stepgen.<Instance>'.
 'Instance' is a two-digit number that corresponds to the HostMot2 stepgen
 instance number.
 There are 'num_stepgens' instances, starting with 00.
@@ -475,13 +475,13 @@ time), but currently only uses two: Step and Direction outputs.
 footnote:[At present, the firmware supports multi-phase stepper outputs,
 but the driver doesn't. Interested volunteers are solicited.]
 
-The stepgen representation is modeled on the stepgen software
-component. Stepgen default is active high step output (high during step
+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.
 
-Each stepgen instance has the following pins and parameters:
+Each StepGen instance has the following pins and parameters:
 
 === Pins
 
@@ -564,7 +564,7 @@ output run 'dmesg' as described above.
 == PWMGen
 
 PWMgens have names like
-'hm2_<BoardType>.<BoardNum>.pwmgen.<Instance>.'. 'Instance' is a
+'hm2_<BoardType>.<BoardNum>.pwmgen.<Instance>'. 'Instance' is a
 two-digit number that corresponds to the HostMot2 pwmgen instance
 number. There are 'num_pwmgens' instances, starting with 00.
 

docs/src/drivers/shuttle.adoc

@@ -71,8 +71,7 @@ of the device (the order in which the driver found them), for example
 '<Prefix>.button-<ButtonNumber>' (bit out)::
   These pins are True (1) when the button is pressed.
 '<Prefix>.button-<ButtonNumber>-not' (bit out)::
-  These pins have the inverse of the button state, so they're True
-  (1) when the button is not pressed.
+  These pins have the inverse of the button state, so they're True (1) when the button is not pressed.
 '<Prefix>.counts' (s32 out)::
   Accumulated counts from the jog wheel (the inner wheel).
 '<Prefix>.spring-wheel-s32' (s32 out)::

docs/src/drivers/vfs11.adoc

@@ -31,14 +31,14 @@ component vfs11_vfd, named spindle-vfd
 
 == Command Line Options
 
-'vfs11_vfd' is mostly configured through inifile options. The command
+'vfs11_vfd' is mostly configured through INI file options. The command
 line options are:
 
 * '-n or --name <halname>' : set the HAL component name
-* '-I or --ini <inifilename>' : take configuration from this ini file.
+* '-I or --ini <inifilename>' : take configuration from this INI file.
   Defaults to environment variable INI_FILE_NAME.
 * '-S or --section <section name>' : take configuration from this
-  section in the ini file. Defaults to 'VFS11'.
+  section in the INI file. Defaults to 'VFS11'.
 * '-d or --debug' enable debug messages on console output.
 * '-m or --modbus-debug' enable modbus messages on console output
 * '-r or --report-device' report device properties on console at startup
@@ -81,7 +81,7 @@ option.
   put the VFD into emergency-stopped status. No operation possible until
   cleared with err-reset or powercycling.
 * '<n>.frequency-command' (float, out)
-  current target frequency in HZ as set through speed-command (which is
+  current target frequency in Hz as set through speed-command (which is
   in RPM), from the VFD
 * '<n>.frequency-out' (float, out)
   current output frequency of the VFD
@@ -222,7 +222,7 @@ TARGET=1
 # for RECONNECT_DELAY seconds
 RECONNECT_DELAY=1
 
-# misc flags
+# misc. parameters
 DEBUG=10
 MODBUS_DEBUG=0
 POLLCYCLES=10
@@ -338,7 +338,7 @@ The Ubuntu +libmodbus5+ and +libmodbus-dev+ packages are
 only available starting from Ubuntu 12 ('Precise Pengolin'). Moreover,
 these packages lack support for the MODBUS_RTS_MODE_*
 flags. Therefore, building vfs11_vfd using this library might generate
-a warning if RTS_MODE= is specified in the ini file.
+a warning if RTS_MODE= is specified in the INI file.
 
 To use the full functionality on lucid and precise:
 
@@ -348,7 +348,7 @@ To use the full functionality on lucid and precise:
   https://github.com/stephane/libmodbus/blob/master/README.rst[here].
 
 Libmodbus does not build on Ubuntu Hardy, hence vfs11_vfd is not
-available on hardy.
+available on Hardy.
 
 // Michael Haberler; loosely based on gs2_vfd by Steve Padnos and John Thornton.
 

docs/src/examples/gs2-example.adoc

@@ -11,7 +11,7 @@ GS2 VFD to drive a spindle.
 The spindle speed and direction is controlled by LinuxCNC.
 
 Using the GS2 component involves very little to set up. We start with
-a Stepconf Wizard generated config. Make sure the pins with "Spindle
+a StepConf Wizard generated config. Make sure the pins with "Spindle
 CW" and "Spindle PWM" are set to unused in the parallel port setup
 screen.
 
@@ -48,15 +48,15 @@ based on your physical requirements but these are beyond the scope of
 this manual. Refer to the GS2 manual that came with the drive for more
 information on the drive parameters.
 
-* The communications switches must be set to RS-232C
-* The motor parameters must be set to match the motor
+* The communications switches must be set to RS-232C.
+* The motor parameters must be set to match the motor.
 * P3.00 (Source of Operation Command) must be set to Operation
-  determined by RS-485 interface, 03 or 04
+  determined by RS-485 interface, 03 or 04.
 * P4.00 (Source of Frequency Command) must be set to Frequency
-  determined by RS232C/RS485 communication interface, 05
-* P9.01 (Transmission Speed) must be set to 9600 baud, 01
+  determined by RS232C/RS485 communication interface, 05.
+* P9.01 (Transmission Speed) must be set to 9600 baud, 01.
 * P9.02 (Communication Protocol) must be set to "Modbus RTU mode,
-  8 data bits, no parity, 2 stop bits", 03
+  8 data bits, no parity, 2 stop bits", 03.
 
 A PyVCP panel based on this example is <<gs2-rpm-meter,here>>.
 

docs/src/gui/pyvcp-examples.adoc

@@ -199,7 +199,7 @@ net my-jogspeed halui.axis.jog-speed <= pyvcp.jog-speed-f
 
 After resetting the E-Stop and putting it into jog mode and moving the
 jog speed slider in the PyVCP panel to a value greater than zero the
-PyVCP jog buttons should work. You can not jog when running a g code
+PyVCP jog buttons should work. You can not jog when running a G-code
 file or while paused or while the MDI tab is selected.
 
 == Port Tester