More changes performed while translating

Author: smoe

docs/src/config/ini-config.adoc

@@ -627,7 +627,7 @@ implemented and the results of using it are unpredictable.
 This section is a custom section and is not used by LinuxCNC directly. Most
 configurations use values from this section to load the motion controller. For
 more information on the motion controller see the <<sec:motion,Motion>>
-Section.
+section.
 
 * 'EMCMOT = motmod' - the motion controller name is typically used here.
 * 'BASE_PERIOD = 50000' - the 'Base' task period in nanoseconds.

docs/src/config/iov2.adoc

@@ -53,7 +53,7 @@ the realtime I/O provided by link:../man/man9/motion.9.html[motion] instead.
 
 INI file options:
 
-* [EMCIO] Section
+* [EMCIO] section
 
 * PROTOCOL_VERSION = 2 
   Defaults to 2. Setting to 1 will emulate old iocontrol behaviour. 
@@ -64,13 +64,13 @@ INI file options:
   low and   start-change-ack is ignored. The reason for this is better
   backwards compatibility. 
 
-* [TASK] Section
+* [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.
 
-* [EMC] Section
+* [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

docs/src/gcode/m-code.adoc

@@ -61,8 +61,7 @@ to stop after each line of input anyway.
 * 'M2' - end the program. Pressing `Cycle Start` ("R" in the Axis GUI)
   will restart the program at the beginning of the file.
 * 'M30' - exchange pallet shuttles and end the program.
-  Pressing `Cycle Start` will start the program
-  at the beginning of the file.
+  Pressing `Cycle Start` will start the program at the beginning of the file.
 
 Both of these commands have the following effects:
 
@@ -83,7 +82,7 @@ will start the program at the beginning of the file.
 
 [WARNING]
 Using % to wrap the G-code does not do the same thing as a 'Program End'.
-See <<gcode:file-requirements,File Requirements>> for more information
+See the section on <<gcode:file-requirements,File Requirements>> for more information
 on what using % does not do.
 
 [[mcode:m60]]
@@ -168,15 +167,15 @@ When the tool change is complete:
 * If the selected tool was not in the spindle before the tool change,
   the tool that was in the spindle (if there was one) will be placed
   back into the tool changer magazine.
-* If configured in the .ini file some axis positions may move when a M6
+* If configured in the INI file some axis positions may move when a M6
   is issued. See the <<sub:ini:sec:emcio,EMCIO section>> for more
   information on tool change options.
 * No other changes will be made. For example, coolant will continue to
   flow during the tool change unless it has been turned off by an 'M9'.
 
 [NOTE]
 The 'T-' word is an integer number designating the tool pocket number in
-the carousel (not its index)
+the carousel (not its index).
 
 [WARNING]
 The tool length offset is not changed by 'M6', use '<<gcode:g43,G43>>' after the
@@ -602,7 +601,7 @@ The suggested use is at the beginning of a O-word subroutine as in the
 following example. Using 'M73' this way enables designing subroutines
 which need to modify modal state but will protect the calling program
 against inadvertent modal changes. Note the use of
-<<gcode:predefined-named-parameters, predefined named parameters>> in
+<<gcode:predefined-named-parameters,predefined named parameters>> in
 the 'showstate' subroutine.
 
 [source,{ngc}]
@@ -698,7 +697,7 @@ as its two arguments.
 
 Execution of the G-code file pauses until the external program exits.
 Any valid executable file can be used. The file must be located in the search
-path specified in the ini file configuration.
+path specified in the INI file configuration.
 See the <<sub:ini:sec:display,Display>> section for more information on search paths.
 
 After creating a new M1nn program, the GUI should be restarted so that the

docs/src/ladder/classic-ladder.adoc

@@ -157,7 +157,7 @@ loadusr classicladder
 ----
 
 NOTE: Only one .clp file can be loaded. If you need to divide your ladder
-use Sections.
+then use sections.
 
 To load a ladder file:
 
@@ -211,8 +211,8 @@ for call coils.
 
 === Section Display
 
-When you first start up ClassicLadder you get an empty Section
-Display window. Displayed is one empty rung.
+When you first start up ClassicLadder you get an empty Section Display window.
+Displayed is one empty rung.
 
 [[cap:section-display-default]]
 .Section Display Default Window
@@ -1145,14 +1145,14 @@ like the following. If not, use the Eraser to remove unwanted sections.
 .Section Display with Rung
 image::images/Section_Display_Build02.png["Section Display with Rung",align="center"]
 
-Now click on the OK button in the Editor window. Now your Section
-Display should look like this.
+Now click on the OK button in the Editor window.
+Now your Section Display should look like this:
 
 [[cap:section-display-finished]]
 .Section Display Finished
 image::images/Section_Display_Build03.png["Section Display Finished",align="center"]
 
-To save the new file select Save As and give it a name. The .clp
+To save the new file select 'Save As' and give it a name. The .clp
 extension will be added automatically. It should default to the running
 config directory as the place to save it.