More changes performed while translating

Author: smoe

docs/src/drivers/gm.adoc

@@ -89,7 +89,7 @@ gm.0.gpio.0.in-0
 ----
 
 indicates the state of the first pin of the first GPIO
-connector on the GM6-PCI card. Hal pins are updated by function
+connector on the GM6-PCI card. HAL pins are updated by function
 
 ----
 gm.<nr of card>.read
@@ -180,7 +180,7 @@ gm.0.encoder.0.position
 refers to the position of encoder module of axis 0.
 
 The GM6-PCI card counts the encoder signal independently from LinuxCNC.
-Hal pins are updated by function:
+HAL pins are updated by function:
 
 ----
 gm.<nr of card>.read
@@ -197,7 +197,7 @@ gm.<nr of card>.read
 | .index-enabled     | (bit, IO)          | When True, counts and position are rounded or reset
                                             (depends on index-mode) on next rising edge of channel-I.
                                             Every time position is reset because of Index, index-enabled
-                                            pin is set to 0 and remain 0 until connected hal pin does
+                                            pin is set to 0 and remain 0 until connected HAL pin does
                                             not set it.
 | .velocity          | (float, Out)       | Velocity in scaled units per second. GM encoder uses high
                                             frequency hardware timer to measure time between encoder
@@ -262,14 +262,14 @@ Connect encoder position to LinuxCNC position feedback:
 net Xpos-fb gm.0.encoder.0.position => joint.0.motor-pos-fb
 ----
 
-=== Stepgen module
+=== StepGen module
 
-The GM6-PCI motion control card has six stepgen modules, one for each joint.
+The GM6-PCI motion control card has six StepGen modules, one for each joint.
 Each module has two output signals. It can produce Step/Direction,
-Up/Down or Quadrature (A/B) pulses. Each stepgen module is connected
+Up/Down or Quadrature (A/B) pulses. Each StepGen module is connected
 to the pins of the corresponding RJ50 axis connector.
 
-Every stepgen pin and parameter name begins as follows:
+Every StepGen pin and parameter name begins as follows:
 
 ----
 gm.<nr of card>.stepgen.<nr of axis>
@@ -281,10 +281,10 @@ where nr of axis is from 0 to 5. For example:
 gm.0.stepgen.0.position-cmd
 ----
 
-refers to the position command of stepgen module of axis 0 on card 0.
+refers to the position command of StepGen module of axis 0 on card 0.
 
 The GM6-PCI card generates step pulses independently from LinuxCNC.
-Hal pins are updated by function
+HAL pins are updated by function
 
 ----
 gm.<nr of card>.write
@@ -309,10 +309,10 @@ gm.<nr of card>.write
 | Parameters         | Type and Read/Write | Parameter description
 | .step-type         | (u32, R/W)          | When 0, module produces Step/Dir signal. When 1, it
                                              produces Up/Down step signals. And when it is 2, it
-											 produces quadrature output signals.
+                                             produces quadrature output signals.
 | .control-type      | (bit, R/W)          | When True, .velocity-cmd is used as reference and velocity
                                              control calculate pulse rate output. When False, .position-cmd
-											 is used as reference and position control calculate pulse rate output.
+                                             is used as reference and position control calculate pulse rate output.
 | .invert-step1      | (bit, R/W)          | Invert the output of channel 1 (Step signal in StepDir mode)
 | .invert-step2      | (bit, R/W)          | Invert the output of channel 2 (Dir signal in StepDir mode)
 | .maxvel            | (float, R/W)        | Maximum velocity in position units per second. If it is set to 0.0,
@@ -332,7 +332,7 @@ image::images/GM_RefSignals.png["Reference signal timing diagrams",align="center
 
 .HAL example
 
-Setting stepgen module of axis 0 to generate 1000 step pulse per position unit:
+Setting StepGen module of axis 0 to generate 1000 step pulse per position unit:
 
 ----
 setp gm.0.stepgen.0.step-type 0         # 0:stepDir, 1:UpDown, 2:Quad
@@ -349,7 +349,7 @@ setp gm.0.stepgen.0.stepspace1000       # 1000 ns = 1 us
 setp gm.0.stepgen.0.dirdelay 2000       # 2000 ns = 2 us
 ----
 
-Connect stepgen to axis 0 position reference and enable pins:
+Connect StepGen to axis 0 position reference and enable pins:
 
 ----
 net Xpos-cmd joint.0.motor-pos-cmd => gm.0.stepgen.0.position-cmd
@@ -362,7 +362,7 @@ The GM6-PCI motion control card has one enable output and one fault
 input HAL pins, both are connected to each RJ50 axis connector
 and to the CAN connector.
 
-Hal pins are updated by function:
+HAL pins are updated by function:
 
 ----
 gm.<nr of card>.read
@@ -400,7 +400,7 @@ gm.0.dac.0.value
 ----
 
 refers to the output voltage of DAC module of axis 0.
-Hal pins are updated by function:
+HAL pins are updated by function:
 
 ----
 gm.<nr of card>.write
@@ -469,7 +469,7 @@ gm.0.can-gm.0.position
 
 refers to the output position of axis 0 in position units.
 
-Hal pins are updated by function:
+HAL pins are updated by function:
 
 ----
 gm.<nr of card>.write
@@ -566,7 +566,7 @@ gm.0.joint.0.home-sw-in
 
 indicates the state of the axis 0 home switch.
 
-Hal pins are updated by function:
+HAL pins are updated by function:
 
 ----
 gm.<nr of card>.read

docs/src/gcode/g-code.adoc

@@ -142,7 +142,7 @@ rapid rate (or slower). 'G0' is typically used as a positioning move.
 
 === Rapid Velocity Rate
 
-The MAX_VELOCITY setting in the ini file [TRAJ] section defines the
+The MAX_VELOCITY setting in the INI file [TRAJ] section defines the
 maximumrapid traverse rate. The maximum rapid traverse rate can be
 higher than the individual axes MAX_VELOCITY setting during a
 coordinated move. The maximum rapid traverse rate can be slower than the
@@ -964,7 +964,7 @@ It is a good idea to include a plane selection in the preamble
 of each G-code file.
 
 The effects of having a plane selected are discussed in Section
-<<gcode:g2-g3,G2 G3 Arcs>> and Section <<gcode:g80-g89,G81 G89>>
+<<gcode:g2-g3,G2 G3 Arcs>> and Section <<gcode:g80-g89,G81 G89>>.
 
 [[gcode:g20-g21]]
 == G20, G21 Units(((G20 Units)))
@@ -985,7 +985,7 @@ desired G28 position has been stored with G28.1.
 G28 uses the values stored in <<sub:numbered-parameters,parameters>>
 5161-5169 as the X Y Z A B C U V W final point to move to. The parameter
 values are 'absolute' machine coordinates in the native machine 'units'
-as specified in the ini file. All axes defined in the ini file will be
+as specified in the INI file. All axes defined in the INI file will be
 moved when a G28 is issued. If no positions are stored with G28.1 then
 all axes will go to the <<sec:machine-coordinate-system,machine origin>>.
 
@@ -1019,14 +1019,14 @@ desired G30 position has been stored with G30.1.
 G30 functions the same as G28 but uses the values stored in
 <<sub:numbered-parameters,parameters>> 5181-5189 as the X Y Z A B C U V
 W final point to move to. The parameter values are 'absolute' machine
-coordinates in the native machine 'units' as specified in the ini file.
-All axes defined in the ini file will be moved when a G30 is issued. If
+coordinates in the native machine 'units' as specified in the INI file.
+All axes defined in the INI file will be moved when a G30 is issued. If
 no positions are stored with G30.1 then all axes will go to the
 <<sec:machine-coordinate-system,machine origin>>.
 
 [NOTE]
 G30 parameters will be used to move the tool when a M6 is programmed
-if TOOL_CHANGE_AT_G30=1 is in the [EMCIO] section of the ini file.
+if TOOL_CHANGE_AT_G30=1 is in the [EMCIO] section of the INI file.
 
 * 'G30' - makes a <<gcode:g0,rapid move>> from the current
   position to the 'absolute' position of the values in parameters
@@ -2576,8 +2576,8 @@ becomes the specified value. All of the coordinate system's origins
 'G92' uses the values stored in <<sub:numbered-parameters,parameters>>
 5211-5219 as the X Y Z A B C U V W offset values for each axis.
 The parameter values are 'absolute' machine coordinates
-in the native machine 'units' as specified in the ini file.
-All axes defined in the ini file will be offset when G92 is active.
+in the native machine 'units' as specified in the INI file.
+All axes defined in the INI file will be offset when G92 is active.
 If an axis was not entered following the G92, that axis' offset
 will be zero.