Fix typos

Found via `codespell -q 3 -S *.po,*.pot,*.ts,./.git/logs,./share,./docs/man/es,./configs/attic,*_fr.*,*_es.*,README_es -L ans,ba,bulle,componentes,doubleclick,dout,dum,fo,halp,ihs,inout,parm,parms,ro,ser,te,ue,wille,wonte`

TODO

@@ -2,7 +2,7 @@ TODO for the joints_axes branch
 
 * clean up joints/axes throughout the whole code (lots of parts already done)
 * define a unified jogging way (both for joints and axes)
-* implement joint-limits for carthesian moves (requires simulating the speed in userspace)
+* implement joint-limits for cartesian moves (requires simulating the speed in userspace)
 * update configs
 (and many other probably..)
 

docs/README.adoc

@@ -174,7 +174,7 @@ make -C src translateddocs
 ```
 
 Once this is completed, the files in docs/po/ will be updated, and
-should be commited into git and pulled into Weblate.
+should be committed into git and pulled into Weblate.
 
 === How to add a new translation language
 

docs/man/man1/mdro.1

@@ -114,7 +114,7 @@ when \fBmdro\fR starts:
  mdro.index-enable.3
 
 In this example, the first row will be labeled "X" and will show the data associated
-with pin mdro.axis.0. In many configurations, mdro.axis.0 can be conneted
+with pin mdro.axis.0. In many configurations, mdro.axis.0 can be connected
 directly to x-pos-fb in the POSTGUI-HAL file. The index pins should be
 connected to the corresponding index-enable pins from the DRO.
 

docs/man/man1/xhc-hb04.1

@@ -118,7 +118,7 @@ in the xhc\-hb04 (loadusr) command.
 
 .SH Input Pins (to the pendant LCD display)
 .TP
-(float in) \fIxhc\-hb04.[xyza].pos\-absolute\fR Absolule position display.
+(float in) \fIxhc\-hb04.[xyza].pos\-absolute\fR Absolute position display.
 (typically connect to: halui.axis.N.pos\-feedback). The LCD display
 for pos\-absolute is fixed format with a sign, 4 number digits and 3
 fraction digits (+XXXX.XXX), require: \-9999.999 <= value <= 9999.999.

docs/man/man9/hostmot2.9

@@ -630,7 +630,7 @@ e: (Encoder):
  (float, r/w) hm2_XXXX.N.ssi.MM.<name>.scale: (float, r.w) The encoder scale in
 counts per machine unit.
  (u32, r/w) hm2_XXXX.N.ssi.MM.<name>.counts\-per\-rev (u32, r/w) Used to emulate
-the index behaviour of an incemental+index encoder. This would normally be set
+the index behaviour of an incremental+index encoder. This would normally be set
 to the actual counts per rev of the encoder, but can be any whole number of
 revs. Integer divisors or multipliers of the true PPR might be useful for 
 index-homing. Non-integer factors might be appropriate where there is a 

docs/man/man9/stepgen.9

@@ -152,7 +152,7 @@ The minimum time between a forward step and a reverse step, in nanoseconds.
 There are five timing parameters which control the output waveform.  No step type
 uses all five, and only those which will be used are exported to HAL.  The values
 of these parameters are in nano-seconds, so no recalculation is needed when
-changing thread periods.  In the timing diagrams that follow, they are identfied
+changing thread periods.  In the timing diagrams that follow, they are identified
 by the following numbers:
 .P
 (1) \fBstepgen.n.steplen\fR

docs/src/config/ini-config.adoc

@@ -309,7 +309,7 @@ User Manual.
 
 [NOTE]
 The following [DISPLAY] items are used by GladeVCP, see the
-<<gladevcp:embeding-tab,embedding a tab>> section of the GladeVCP Chapter.
+<<gladevcp:embedding-tab,embedding a tab>> section of the GladeVCP Chapter.
 
 * 'EMBED_TAB_NAME=GladeVCP demo'
 * 'EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -x {XID} -u ./gladevcp/hitcounter.py ./gladevcp/manual-example.ui'

docs/src/config/stepconf.adoc

@@ -259,7 +259,7 @@ Using the buttons provided, jog the axis to near the center of travel.
 Take care because with a low acceleration value,
 it can take a surprising distance for the axis to decelerate to a stop.
 
-After gaging the amount of travel available,
+After gauging the amount of travel available,
 enter a safe distance in Test Area, keeping in mind that
 after a stall the motor may next start to move in an unexpected direction.
 Then click Run.

docs/src/drivers/hostmot2.adoc

@@ -730,7 +730,7 @@ following pins and parameters:
 * 'scale' - (Float, RW) Converts from 'count' units to 'position' units.
   A quadrature encoder will normally have 4 counts per pulse so a 100 PPR
   encoder would be 400 counts per revolution. In '.counter-mode' a 100
-  PPR encoder would have 100 counts per revelution as it only uses the
+  PPR encoder would have 100 counts per revolution as it only uses the
   rising edge of A and direction is B.
 
 * 'vel-timeout' - (Float, RW) When the encoder is moving slower than one

docs/src/drivers/mb2hal.adoc

@@ -147,7 +147,7 @@ could become `mb2hal.plcin.01`. The name must not exceed 28 characters.
 *NOTE:* when using names be careful that
 you don't end up with two transactions using the same name.
 |`MAX_UPDATE_RATE`| Float | No | Maximum update rate in Hz. Defaults to
-0.0 (0.0 = as soon as available = infinit).
+0.0 (0.0 = as soon as available = infinite).
 *NOTE:* This is a maximum rate and the actual rate may be lower. If you
 want to calculate it in ms use (1000 / required_ms).
 Example: 100 ms = `MAX_UPDATE_RATE=10.0`,

docs/src/drivers/mitsub-vfd.adoc

@@ -14,7 +14,7 @@
 
 This is a userspace HAL program, written in python, to control VFD's from
 Mitsubishi. +
-Specifcally the A500 F500 E500 A500 D700 E700 F700 series - others may work. +
+Specifically the A500 F500 E500 A500 D700 E700 F700 series - others may work. +
 mitsub_vfd supports serial control using the RS485 protocol. +
 Conversion from USB or serial port to RS485 requires special hardware. +
 [NOTE]

docs/src/getting-started/getting-linuxcnc.adoc

@@ -126,7 +126,7 @@ https://help.ubuntu.com/community/HowToMD5SUM[How To MD5SUM]
 
 == Write the image to a bootable device
 
-The Raspbery Pi image is a completes SD card image and should be
+The Raspberry Pi image is a completes SD card image and should be
 written to an SD card in
 https://www.raspberrypi.org/documentation/installation/installing-images/README.md[the normal way].
 

docs/src/gui/gladevcp.adoc

@@ -354,8 +354,8 @@ might not be needed in your setup. The relative path specifier ../../nc_files/gl
 is constructed to work with directories copied by the configuration picker and when
 using a run-in-place setup.
 
-[[gladevcp:embeding-tab]]
-=== Embeding as a Tab
+[[gladevcp:embedding-tab]]
+=== Embedding as a Tab
 
 To do so, edit your .ini file and add to the DISPLAY and HAL sections of ini
 file as follows:
@@ -1383,7 +1383,7 @@ grid size::
   Defaults to 0
 use default mouse controls::
   This disables the default mouse controls. +
-  This is most useful when using a touchscreen as the default controls do not work well. You can programatically
+  This is most useful when using a touchscreen as the default controls do not work well. You can programmatically
   add controls using python and the handler file technique. +
   Default = true.
 view::

docs/src/gui/gmoccapy.adoc

@@ -144,7 +144,7 @@ PREFERENCE_FILE_PATH = gmoccapy_preferences
 
 gmoccapy 3 does support the following command line options:
 
- * -user_mode : If set, the setup button will be disabled, so normal machine opperators are not able to edit the settings of the machine *
+ * -user_mode : If set, the setup button will be disabled, so normal machine operators are not able to edit the settings of the machine *
  * -logo <path to logo file> : If given, the logo will hide the jog button tab in manual mode, this is only useful for machines with hardware button for jogging and increment selection +
 
 The line PREFERENCE_FILE_PATH gives the location and name of the preferences file to be used.
@@ -1578,7 +1578,7 @@ Details about how exactly an IconTheme is built can be found at https://specific
 
 Start by creating an empty directory with the name of the icon theme. Place the directory in one of gmoccapy's IconTheme directories.
 Then we need a file called index.theme in the root folder of our icon theme which contains the required metadata for the theme.
-Thats a simple text file with at least the following sections:
+That's a simple text file with at least the following sections:
 
     [Icon Theme]
     Name=YOUR_THEME_NAME
@@ -1589,7 +1589,7 @@ Thats a simple text file with at least the following sections:
 * Name: The name of your icon theme
 * Comment: A description of your icon theme
 * Inherits: A icon theme can derive from another icon theme, the default is hicolor
-* Directories: A comma separted list of all the directories of your icon theme
+* Directories: A comma separated list of all the directories of your icon theme
 
 Each directory usually contains all the icons of the theme in a specific size, for example 16x16/actions should contain all icons with the category "actions" in the size 16x16 pixels as pixel-graphics (e.g. png files).
 A special case is the directory called "scalable/actions", this contains scalable icons not tied to a specific size (e.g. svg files).
@@ -1610,7 +1610,7 @@ Fo each directory we also have to write a section in the index.theme file:
     Context=Actions
 ----
 
-* Size: Nominal icon size in this direcotry
+* Size: Nominal icon size in this directory
 * Type: Fixed, Threshold or Scalable
 * Context: Intended "category" of icons
 

docs/src/gui/gscreen.adoc

@@ -137,7 +137,7 @@ Some will load the theme that is the same name in the config file. The sample
 Inside this folder is another folder call gtk-2.0, inside that is the theme 
 files. If you add this file, Gscreen will default to this theme on start up.
 gscreen-gaxis has a sample custom theme that looks for certain named widgets 
-and changes the visual behaivor of those specific widgets. The Estop and 
+and changes the visual behavior of those specific widgets. The Estop and 
 machine-on buttons use different colors then the rest of the buttons so that
 they stand out. This is done in the handler file by giving them specific names
 an by adding specific commands in the theme's gtkrc file.
@@ -529,7 +529,7 @@ MESSAGE_TYPE = yesnodialog
 MESSAGE_PINNAME = yndialogtest
 
 # This pops up a dialog that requires an ok response and it shows in the status bar and
-# the destop notify popup.
+# the desktop notify popup.
 MESSAGE_BOLDTEXT = This is the short text
 MESSAGE_TEXT = This is the longer text of the both type test. It can be longer then the status bar text
 MESSAGE_DETAILS = BOTH DETAILS

docs/src/gui/qtvcp-development.adoc

@@ -138,7 +138,7 @@ self.SETTINGS_ = the Qsettings object
 ----
 
 When making a custom widget, import and sub class the
-'_HalWidgetBase' class for this behaivor:
+'_HalWidgetBase' class for this behavior:
 
 === Dialogs
 

docs/src/gui/qtvcp-libraries.adoc

@@ -661,7 +661,7 @@ MESSAGE_TYPE = yesnodialog
 MESSAGE_PINNAME = yndialogtest
 
 # This pops up a dialog that requires an ok response and it shows in the status bar and
-# the destop notify popup.
+# the desktop notify popup.
 MESSAGE_BOLDTEXT = This is the short text
 MESSAGE_TEXT = This is the longer text of the both type test. It can be longer then the status bar text
 MESSAGE_DETAILS = BOTH DETAILS
@@ -694,7 +694,7 @@ This module allows one to load and save preference data permanently to storage m
 The screenoptions widget can automatically set up the preference system. +
 qtvcp searches for the screenoption widget first and if found calls `\_pref_init()`. +
 This will create the preference object and return it to qtvcp to pass to all the widgets and +
-add it to the window object attributes. In this case the preferences object would be accesable +
+add it to the window object attributes. In this case the preferences object would be accessible +
 from the handler file's initialized_ method as self.w.PREFS_ +
 Also all widgets can have access to a specific preference file at initialization time. +
 

docs/src/gui/qtvcp-widgets.adoc

@@ -2193,7 +2193,7 @@ to add actions.
 * add_tool() - adds a blank dummy tool (99) that the user can edit to
   suit.
 * delete_tools() - deletes the currently checkbox selected tools
-* get_checked_list() - returns a list of tools selected by checkboxs.
+* get_checked_list() - returns a list of tools selected by checkboxes.
 * set_all_unchecked() - uncheck all selected tools.
 
 [source,python]

docs/src/hal/halmodule.adoc

@@ -213,7 +213,7 @@ hal.connect("pinname","signal_name")
 
 === disconnect
 
-Disonnect a pin from a signal. +
+Disconnect a pin from a signal. +
 
 .Example
 ----

docs/src/hal/rtcomps.adoc

@@ -355,7 +355,7 @@ rates of 10 kHz to perhaps up to 50 kHz.
 
 The base thread should be 1/2 count speed to allow for noise and timing
 variation. For example if you have a 100 pulse per revolution encoder on the
-spindle and your maximnum RPM is 3000 the maximum base thread should be 25 µs.
+spindle and your maximum RPM is 3000 the maximum base thread should be 25 µs.
 A 100 pulse per revolution encoder will have 400 counts. The spindle speed
 of 3000 RPM = 50 RPS (revolutions per second). 400 * 50 = 20,000 counts per
 second or 50 µs between counts.

docs/src/man/man1/hy_gt_vfd.1.adoc

@@ -50,7 +50,7 @@ P0.03::
 
 P0.04::
 
-    Set Upper Frequence Limit to the maximum frequency you want the VFD
+    Set Upper Frequency Limit to the maximum frequency you want the VFD
     to output, in Hz.  This should be the same as the value in P0.03.
 
 P0.05::
@@ -73,7 +73,7 @@ P2.02 = ???::
 P2.03 = ???::
 
     Set Motor Rated Speed to the motor's speed in RPM at its rated
-    maximum frequence.
+    maximum frequency.
 
 P2.04 = ???::
 

docs/src/plasma/qtplasmac.adoc

@@ -678,7 +678,7 @@ DISPLAY = qtvcp -f qtplasmac
 
 *[TRAJ]* Section
 
-This variable  is mandatory.
+This variable is mandatory.
 
 [source,{ini}]
 ----
@@ -728,7 +728,7 @@ The following sections will give a general overview of the QtPlasmaC layout.
 
 === Exiting QtPlasmaC
 
-Exiting or shuting down QtPlasmaC is done by either of:
+Exiting or shutting down QtPlasmaC is done by either:
 
 . Click the window shutdown button on the window title bar
 . Long press the *POWER* button on the MAIN Tab.
@@ -1649,11 +1649,11 @@ If an alignment laser has been set up then it is possible to use the laser durin
 
 Path tolerance is set with a G64 command and a following P value. The P value corresponds to the amount that the actual cut path followed by the machine may deviate from the programmed cut path.
 
-The default LinuxCNC path tolerence is set for maximum speed which will severely round corners when used with normal plasma cutting speeds.
+The default LinuxCNC path tolerance is set for maximum speed which will severely round corners when used with normal plasma cutting speeds.
 
 It is recommended that the path tolerance is set by placing the appropriate G64 command and P value in the header of each G-Code file.
 
-The provided G-Code filter program will test for the existance of a G64 Pn command prior to the first motion command. If no G64 command is found it will insert a G64 P0.1 command which sets the path tolerance to 0.1mm. For a imperial config the command will be G64 P0.004.
+The provided G-Code filter program will test for the existence of a G64 Pn command prior to the first motion command. If no G64 command is found it will insert a G64 P0.1 command which sets the path tolerance to 0.1mm. For a imperial config the command will be G64 P0.004.
 
 For Metric:
 [source,{ngc}]
@@ -2001,7 +2001,7 @@ M2 (end job)
 
 QtPlasmaC has the ability to automatically modify the G-Code to reduce the velocity and/or apply *Over cut* which can be useful when cutting holes.
 
-For valid hole sensing it is required that all values in the G2 or G3 G-Code line are explicit, an error dialog will be dispalyed if any values are mathematically calculated.
+For valid hole sensing it is required that all values in the G2 or G3 G-Code line are explicit, an error dialog will be displayed if any values are mathematically calculated.
 
 QtPlasmaC Hole Sensing is disabled by default. It can be enabled/disabled by using the following G-Code parameters to select the desired hole sensing mode:
 

nc_files/macros/lathe/facing.ngc

@@ -10,7 +10,7 @@
 ; #4 feed/rpm
 ; #5 Face Z length
 ; #6 face angle
-; #7 tool numbber
+; #7 tool number
 
 ;Facing
 

nc_files/ngcgui_lib/iquad.ngc

@@ -86,7 +86,7 @@ o<line>  call [#<x2>][#<y2>][#<x3>][#<y3>]
          #<cos23>    = #<_line:cos>
          #<sin23>    = #<_line:sin>
 
-         (compute angles at line interesctions:)
+         (compute angles at line intersections:)
 o<dot>   call [#<x4>][#<y4>][#<x1>][#<y1>][#<x2>][#<y2>]
          #<ang412> = #<_dot:ang>
 o<dot>   call [#<x1>][#<y1>][#<x2>][#<y2>][#<x3>][#<y3>]

nc_files/ngcgui_lib/qpocket.ngc

@@ -253,7 +253,7 @@ o<line>  call [#<x4i>][#<y4i>][#<x1i>][#<y1i>]
          #<cos41> = #<_line:cos>
          #<sin41> = #<_line:sin>
 
-         ;compute angles at line interesctions:
+         ;compute angles at line intersections:
 o<dot>   call [#<x1i>][#<y1i>][#<x2i>][#<y2i>][#<x3i>][#<y3i>]
          #<ang123> = #<_dot:ang>
 o<dot>   call [#<x2i>][#<y2i>][#<x3i>][#<y3i>][#<x4i>][#<y4i>]

share/axis/tcl/combobox.tcl

@@ -319,7 +319,7 @@ proc ::combobox::SetClassBindings {} {
 #
 #    I'm not convinced these are the proper bindings. Ideally all
 #    bindings should be on "Combobox", but because of my juggling of
-#    bindtags I'm not convinced thats what I want to do. But, it all
+#    bindtags I'm not convinced that's what I want to do. But, it all
 #    seems to work, its just not as robust as it could be.
 #
 # Arguments:

src/emc/kinematics/scorbot-kins.c

@@ -96,7 +96,7 @@ int kinematicsForward(
     j2_vector.tran.z = L1_LENGTH * sin(TO_RAD * joints[1]);
     // rtapi_print("fwd: j2=(%f, %f, %f)\n", j2_vector.tran.x, j2_vector.tran.y, j2_vector.tran.z);
 
-    // Link 2 connectes j2 (elbow) to j3 (wrist).
+    // Link 2 connects j2 (elbow) to j3 (wrist).
     // J3 is the controlled point.
     r = L2_LENGTH * cos(TO_RAD * joints[2]);
     j3_vector.tran.x = r * cos(TO_RAD * joints[0]);

src/emc/motion/axis.c

@@ -7,7 +7,7 @@
 
 typedef struct {
     double pos_cmd;                 /* commanded axis position */
-    double teleop_vel_cmd;          /* comanded axis velocity */
+    double teleop_vel_cmd;          /* commanded axis velocity */
     double max_pos_limit;           /* upper soft limit on axis pos */
     double min_pos_limit;           /* lower soft limit on axis pos */
     double vel_limit;               /* upper limit of axis speed */

src/emc/motion/motion.h

@@ -564,7 +564,7 @@ Suggestion: Split this in to an Error and a Status flag register..
    memory, and it reports motion controller status to higher level
    code in user space.  For the most part, this structure contains
    higher level variables - low level stuff is made visible to the
-   HAL and troubleshooting, etc, is done using the HAL oscilliscope.
+   HAL and troubleshooting, etc, is done using the HAL oscilloscope.
 */
 
 /*! \todo FIXME - this struct is broken into two parts... at the top are

src/emc/rs274ngc/interp_g7x.cc

@@ -12,7 +12,7 @@
 #endif
 
 ////////////////////////////////////////////////////////////////////////////////
-// Ancient compiler work-arounds
+// Ancient compiler workarounds
 ////////////////////////////////////////////////////////////////////////////////
 
 #if __cplusplus < 201402L

src/emc/rs274ngc/interp_internal.hh

@@ -770,7 +770,7 @@ struct setup
   int value_returned;                // the last NGC procedure did/did not return a value
   int call_level;                    // current subroutine level
   context sub_context[INTERP_SUB_ROUTINE_LEVELS];
-  int call_state;                  //  enum call_states - inidicate Py handler reexecution
+  int call_state;                  //  enum call_states - indicate Py handler reexecution
   offset_map_type offset_map;      // store label x name, file, line
 
   bool adaptive_feed;              // adaptive feed is enabled

src/emc/rs274ngc/rs274ngc_pre.cc

@@ -2652,7 +2652,7 @@ int Interp::on_abort(int reason, const char *message)
 // spun out from interp_o_word so we can use it to test ngc file accessibility during
 // config file parsing (REMAP... ngc=<basename>)
 // Will expand ~ to user's home path
-// searchs this sequence until it finds a match:
+// searches this sequence until it finds a match:
 // 1) checks if path is already the full path
 // 2) tries adding the INI defined program prefix to path
 // 3) tries adding the INI defined subroutine prefix to path

src/emc/task/emctaskmain.cc

@@ -115,7 +115,7 @@ static RCS_TIMER *timer = 0;
 static int emcTaskNoDelay = 0;
 // flag signifying that on the next loop, there should be no delay.
 // this is set when transferring trajectory data from userspace to kernel
-// space, annd reset otherwise.
+// space, and reset otherwise.
 static int emcTaskEager = 0;
 
 static int no_force_homing = 0; // forces the user to home first before allowing MDI and Program run