Merge pull request #1870 from luzpaz/typos/configs

configs: fix various typos

Author: c-morley

configs/attic/demo_mazak/demo_mazak.ini

@@ -103,7 +103,7 @@ MAX_LINEAR_ACCELERATION = 20.0
 
 [EMCIO]
 # change tools in the upper left corner of the table
-# to avoid hitting the vise or workpiece with the tool
+# to avoid hitting the vice or workpiece with the tool
 TOOL_CHANGE_POSITION = -13.75 7.5 -0.022
 # Name of IO controller program, e.g., io
 EMCIO =     io

configs/sim/axis/moveoff/moveoff_display_7.xml

@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!-- this is an example, the values are not
-likelly to be suitable for a real machine
+likely to be suitable for a real machine
 -->
 <pyvcp>
   <vbox>

configs/sim/axis/orphans/iocontrol-removed/python/customtask.py

@@ -296,7 +296,7 @@ def emcToolSetOffset(self,pocket,toolno,offset,diameter,frontangle,backangle,ori
         self.io.tool.toolTable[pocket].backangle = backangle
         self.io.tool.toolTable[pocket].offset = offset
 
-        if debug(): print("new tool enttry: ",str(self.io.tool.toolTable[pocket]))
+        if debug(): print("new tool entry: ",str(self.io.tool.toolTable[pocket]))
 
         if self.io.tool.toolInSpindle  == toolno:
             self.io.tool.toolTable[0] = self.io.tool.toolTable[pocket]

configs/sim/axis/orphans/pysubs/customtask.py

@@ -290,7 +290,7 @@ def emcToolSetOffset(self,pocket,toolno,offset,diameter,frontangle,backangle,ori
         self.io.tool.toolTable[pocket].backangle = backangle
         self.io.tool.toolTable[pocket].offset = offset
 
-        if debug(): print("new tool enttry: ",str(self.io.tool.toolTable[pocket]))
+        if debug(): print("new tool entry: ",str(self.io.tool.toolTable[pocket]))
 
         if self.io.tool.toolInSpindle  == toolno:
             self.io.tool.toolTable[0] = self.io.tool.toolTable[pocket]

configs/sim/axis/vismach/5axis/bridgemill/5axis.ini

@@ -72,7 +72,7 @@ TOOL_TABLE = 5axis.tbl
 [KINS]
 # Note: Supported coordinates are XYZBCW but the W coordinate
 #       motion is incorporated into the X,Y,Z axes.
-#       Use of the W coordinate requies a joint (5)
+#       Use of the W coordinate requires a joint (5)
 #       in order to allow display of W values.
 #       Use immediate homing for this joint (JOINT_5)
 # Note: 5axiskins is misnomer

configs/sim/axis/xhc-hb04/README

@@ -134,7 +134,7 @@ Note: halui MDI commands are defined in a [HALUI] stanza:
 MDI_COMMAND = G0 X0 Y0 Z0
 MDI_COMMAND = M101
 
-The commands are assigned to pins (Type=bit, Dir=IN) named halui.mdi-command-nn whre
+The commands are assigned to pins (Type=bit, Dir=IN) named halui.mdi-command-nn where
 nn corresponds to their ordered appearance beginning with nn=00.  (man halui for more information)
 ----------------------------------
 A application named monitor-xhc-hb04 is included to monitor disconnects and reconnects of the pendant.  This script runs in the background and will pop up a message when the pendant is disconnected or reconnected.  Usage is optional; if used it is specified with ini file entry:

configs/sim/gmoccapy/gmoccapy_plasma/plasma.py

@@ -2,7 +2,7 @@
 # -*- coding:UTF-8 -*-
 """
     This file will control some options of the gmoccapy plasma screen
-    and demonstrats at the same time the possibilities you have introducing
+    and demonstrates at the same time the possibilities you have introducing
     your own handler files and functions to that screen, showing the
     possibilities to modify the layout and behavior
 

configs/sim/gmoccapy/gmoccapy_plasma/signals.py

@@ -2,7 +2,7 @@
 # -*- coding:UTF-8 -*-
 """
     This file will control some options of the gmoccapy plasma screen
-    and demonstrats at the same time the possibilities you have introducing
+    and demonstrates at the same time the possibilities you have introducing
     your own handler files and functions to that screen, showing the
     possibilities to modify the layout and behavior
 

configs/sim/gmoccapy/lathe_configs/README

@@ -33,7 +33,7 @@ However it only works for whole numbers: 100/2 will become 50 but
 3.14149/2 is interpreted as 3 and 14 thousand halves so won't work.
 
 Notes on adding your own cycles:
-Greate a new G-code subroutine in the same format as the existing ones.
+Create a new G-code subroutine in the same format as the existing ones.
 In Glade add a new tab to the 'tabs1' notebook and give it a name matching
 the new cycle.
 Edit the action button (inside an eventbox) to call the new G-code sub.

configs/sim/gmoccapy/lathe_configs/lathemacro.ui

@@ -2532,7 +2532,7 @@
                     <property name="height_request">20</property>
                     <property name="visible">True</property>
                     <property name="can_focus">True</property>
-                    <property name="tooltip_markup" translatable="yes">&lt;!--1084,672--&gt;Finish Diamter</property>
+                    <property name="tooltip_markup" translatable="yes">&lt;!--1084,672--&gt;Finish Diameter</property>
                     <property name="halign">start</property>
                     <property name="valign">start</property>
                     <property name="invisible_char">●</property>