Fixed spelling issues in documentation (#3136)

Author: sisve

doc/source/addons/IR.rst

@@ -220,7 +220,7 @@ Access structure IRAddon via ``ADDONS:IR``.
     ===================================== ==================================== =============
      :attr:`NAME`                          :ref:`string <string>`               Name of the Servo
      :attr:`UID`                           :ref:`scalar <scalar>` (int)         Unique ID of the servo part (part.flightID).
-     :attr:`HIGHLIGHT`                     :ref:`Boolean <boolean>` (set-only)  Set Hightlight status of the part.
+     :attr:`HIGHLIGHT`                     :ref:`Boolean <boolean>` (set-only)  Set Highlight status of the part.
      :attr:`POSITION`                      :ref:`scalar <scalar>` (readonly)    Current position of the servo.
      :attr:`MINCFGPOSITION`                :ref:`scalar <scalar>` (readonly)    Minimum position for servo as defined by part creator in part.cfg
      :attr:`MAXCFGPOSITION`                :ref:`scalar <scalar>` (readonly)    Maximum position for servo as defined by part creator in part.cfg
@@ -264,7 +264,7 @@ Access structure IRAddon via ``ADDONS:IR``.
     :type: :ref:`Boolean <boolean>`
     :access: Set
 
-    Set Hightlight status of the part.
+    Set Highlight status of the part.
 
 .. attribute:: IRServo:POSITION
 
@@ -412,7 +412,7 @@ Access structure IRAddon via ``ADDONS:IR``.
 
 Example code::
 
-    print "IR Iavailable: " + ADDONS:IR:AVAILABLE.
+    print "IR available: " + ADDONS:IR:AVAILABLE.
 
     Print "Groups:".
 

doc/source/addons/KAC.rst

@@ -8,7 +8,7 @@ Kerbal Alarm Clock
 - Forum thread, including full instructions: http://forum.kerbalspaceprogram.com/threads/24786
 
 You can find out if Kerbal Alarm Clock addon is available in the
-current game installation by usng the boolean expression
+current game installation by using the boolean expression
 ``addons:available("KAC")``.
 
 Note that due to changes in Kerbal Alarm Clock, kOS can no longer support
@@ -206,7 +206,7 @@ Available Functions
 .. function:: LISTALARMS(alarmType)
 
     If `alarmType` equals "All", returns :struct:`List` of *all* :struct:`KACAlarm` objects attached to current vessel or have no vessel attached.
-    Otherwise returns :struct:`List` of all :struct:`KACAlarm` objects with `KACAlarm:TYPE` equeal to `alarmType` and attached to current vessel or have no vessel attached.::
+    Otherwise returns :struct:`List` of all :struct:`KACAlarm` objects with `KACAlarm:TYPE` equal to `alarmType` and attached to current vessel or have no vessel attached.::
 
         set al to listAlarms("All").
         for i in al

doc/source/addons/RemoteTech.rst

@@ -10,7 +10,7 @@ RemoteTech is a modification for Squad's "Kerbal Space Program" (KSP) which over
 - Documentation: http://remotetechnologiesgroup.github.io/RemoteTech/
 
 You can find out if the RemoteTech addon is available in the
-current game installation by usng the boolean expression::
+current game installation by using the boolean expression::
 
     addons:available("RT")
 
@@ -44,7 +44,7 @@ Interaction with kOS
 .. note::
 
     .. versionadded:: v1.0.2
-        kOS now supports access to connection informaion from a unified location.
+        kOS now supports access to connection information from a unified location.
         See :ref:`Connectivity Managers <connectivityManagers>` for more
         information. All of the previous implementation as detailed on this page
         remains supported.

doc/source/addons/Trajectories.rst

@@ -98,7 +98,7 @@ Access structure TRAddon via ``ADDONS:TR``.
     :type: :struct:`String`
     :access: Get
 
-    **Only gives the correct answer for Trajectries version >= 2.2.0**
+    **Only gives the correct answer for Trajectories version >= 2.2.0**
 
     *For earlier versions, it gives a hardcoded fixed answer, as follows:*
 
@@ -120,7 +120,7 @@ Access structure TRAddon via ``ADDONS:TR``.
     :type: :struct:`Scalar`
     :access: Get
 
-    **Only gives the correct answer for Trajectries version >= 2.0.0**
+    **Only gives the correct answer for Trajectories version >= 2.0.0**
 
     *For earlier versions, it gives a hardcoded fixed answer, as follows:*
 
@@ -139,7 +139,7 @@ Access structure TRAddon via ``ADDONS:TR``.
     :type: :struct:`Scalar`
     :access: Get
 
-    **Only gives the correct answer for Trajectries version >= 2.2.0**
+    **Only gives the correct answer for Trajectories version >= 2.2.0**
 
     *For earlier versions, it gives a hardcoded fixed answer, as follows:*
 
@@ -158,7 +158,7 @@ Access structure TRAddon via ``ADDONS:TR``.
     :type: :struct:`Scalar`
     :access: Get
 
-    **Only gives the correct answer for Trajectries version >= 2.2.0**
+    **Only gives the correct answer for Trajectories version >= 2.2.0**
 
     *For earlier versions, it gives a hardcoded fixed answer, as follows:*
 

doc/source/bindings.rst

@@ -475,7 +475,7 @@ calculating a complex formula, or more milliseconds activating
 actions on a PartModule, and so on, then this feature may
 help.  The ProfileResult() was meant mainly for kOS developers
 trying to internally determine which parts of the system could
-use the most optomizing.  However, as long as it was implemented
+use the most optimizing.  However, as long as it was implemented
 for that purpose, it may as well be made available to all
 the users of kOS as well.
 

doc/source/changes.rst

@@ -103,7 +103,7 @@ Can Set the RCS Deadband
 
 Addition on :attr:`RCS:DEADBAND`
 
-SteeringManager Epislon
+SteeringManager Epsilon
 :::::::::::::::::::::::
 
 Addition of :attr:`SteeringManager:TORQUEEPSILONMIN` and
@@ -169,13 +169,13 @@ CreateOrbit from position and velocity
 
 A new variant of CreateOrbit - :func:`CREATEORBIT(pos, vel, body, ut)`,
 that lets you make an orbit out of state vectors instead of
-Kepplerian values.
+Keplerian values.
 
 Ranges take fractional numbers
 ::::::::::::::::::::::::::::::
 
 :ref:`Ranges <range>` now accept fractional values for start, stop
-and step.  (Previously everthing had to be an integer.)
+and step.  (Previously everything had to be an integer.)
 
 Numerous mistake fixes
 ::::::::::::::::::::::
@@ -226,7 +226,7 @@ New Function, :func:`BODYEXISTS(name)`
 Wordwrap on Labels
 ::::::::::::::::::
 
-You can set wordrap off for labels by the new suffx, :attr:`Style:WORDWRAP`.
+You can set wordwrap off for labels by the new suffix, :attr:`Style:WORDWRAP`.
 
 CreateOrbit
 :::::::::::
@@ -404,7 +404,7 @@ and were removed.
 Document Simulate in BG
 :::::::::::::::::::::::
 
-Documented the need to have Simulate in BG enabled when playing in windwed mode,
+Documented the need to have Simulate in BG enabled when playing in windowed mode,
 on the :ref:`Telnet <telnet>` page.
 
 Stage/decouple docs
@@ -432,7 +432,7 @@ New suffixes on Body page
 :ref:`Body <body>` page now has more fleshed-out examples and documentation
 to go with the new :HASOCEAN, :HASSURFACE, and :CHILDREN suffixes
 
-New Basic tutoial
+New Basic tutorial
 :::::::::::::::::
 
 New Basic Tutorial page.
@@ -556,7 +556,7 @@ error tones, or for playing simple music.  A basic example would be::
 
 For an example of a song, check out the :ref:`Example song section of voice documentation<voicesong>`
 
-Also check out the :ref:`SKID chip documentation<skid>` for an indepth explaination.
+Also check out the :ref:`SKID chip documentation<skid>` for an indepth explanation.
 
 CommNet Support
 :::::::::::::::
@@ -662,7 +662,7 @@ Subdirectories
 See :ref:`Understanding directories <directories>`.
 
 You are now able to store subdirectories ("folders") in your volumes,
-both in the archive and in local volumes.  To accomodate the new feature
+both in the archive and in local volumes.  To accommodate the new feature
 new versions of the file manipulation commands had to be made (please
 go over the documentation in the link given above).
 
@@ -769,7 +769,7 @@ KSP 1.1 release binaries (build 1230)
 Changes in 0.19.3
 -----------------
 
-Interuptable Triggers
+Interruptible Triggers
 :::::::::::::::::::::
 
 Triggers are no longer required to complete within a single update frame,
@@ -807,7 +807,7 @@ this: ::
     }
 
 ``ON`` will now evaluate the expression instead of treating it like a variable
-identifer.
+identifier.
 
 Changes in 0.19.2
 -----------------
@@ -904,7 +904,7 @@ Multimode Engine and Gimbal Support
 :::::::::::::::::::::::::::::::::::
 
 :ref:`Engines <engine>` can now support multiple-mode information, and can
-acces thei gimbal information in the ``:GIMBAL`` suffix.
+access their gimbal information in the ``:GIMBAL`` suffix.
 
 DMagic Orbital Science
 ::::::::::::::::::::::
@@ -938,7 +938,7 @@ JOIN
 ::::
 
 Join suffix on :ref:`lists <list>` now lets you make a string with a
-delimeter of the list's elements.
+delimiter of the list's elements.
 
 Hours per day
 :::::::::::::
@@ -965,7 +965,7 @@ you can use along with lists.
 Run Once
 ::::::::
 
-:ref:`New ONCE argment to the run command <run_once>`
+:ref:`New ONCE argument to the run command <run_once>`
 
 Volumes and Processors integration
 ::::::::::::::::::::::::::::::::::
@@ -999,7 +999,7 @@ A major change to Cooked Steering!
 Should help people using torque-less craft like with Realism Overhaul.
 Removed the old steering logic and replaced it with a nice auto-tuning system.
 
-:ref:`SteeringManager <steeringmanager>` structure now lests you acccess and alter parts of the cooked steering system.
+:ref:`SteeringManager <steeringmanager>` structure now lets you access and alter parts of the cooked steering system.
 
 :ref:`PIDLoop <pidloop>` structure now lets you borrow the PID mechanism used by the new cooked steering, for your own purposes.
 
@@ -1159,13 +1159,13 @@ Docking port, element, and vessel references
 
 You can now get a list of docking ports on any element or vessel using
 the DOCKINGPORTS suffix.  Vessels also expose a list of their elements
-(the ELEMENTS suffix) and an element will refernce it's parent vessel
+(the ELEMENTS suffix) and an element will reference it's parent vessel
 (the VESSEL suffix).
 
 New sounds and terminal features
 ::::::::::::::::::::::::::::::::
 
-For purely cosmetic purpopses, there are new sound features and
+For purely cosmetic purposes, there are new sound features and
  a few terminal tweaks.
 
 - A terminal keyclick option for the in-game GUI terminal.
@@ -1274,7 +1274,7 @@ that a manual user can do by using the right-click menus.
 Kerbal Alarm Clock support
 ::::::::::::::::::::::::::
 
-If you have the Kerbal Alarm Clock Mod isntalled, you can now
+If you have the Kerbal Alarm Clock Mod installed, you can now
 :ref:`query and manipulate its alarms <KAC>` from within your
 kOS scripts.
 

doc/source/commands/communication.rst

@@ -157,8 +157,8 @@ Connectivity Managers
         support both CommNet and RemoteTech. Other mods may be supported or
         provide their own support in the future.
 
-kOS can implement communications over a variaty of connectivity configurations.
-We refer to these options as "Connectivity Managers." You can slect the active
+kOS can implement communications over a variety of connectivity configurations.
+We refer to these options as "Connectivity Managers." You can select the active
 manager from the :ref:`kOS section of KSP's Difficulty Settings<settingsWindow>`.
 If the currently selected manager no longer is available, or if a new manager
 becomes available, you will be prompted with a dialog box to select the manager

doc/source/commands/flight/cooked.rst

@@ -56,7 +56,7 @@ The special LOCK variables for cooked steering
 
     IF you have the *Breaking Ground DLC* for Kerbal Space Program, please
     be aware that even though you can set up control groups to make parts
-    such as propellors and engines react to the throttle, they will not
+    such as propellers and engines react to the throttle, they will not
     react to ``lock throttle``.  This is because the DLC ignores the
     autopilot API in using this feature.  It only pays attention to the
     actual pilot controls, not the autopilot controls overriding them.
@@ -116,7 +116,7 @@ Like all ``LOCK`` expressions, the steering and throttle continually update on t
     **About** ``lock steering`` **and** ``SAS`` **:**  While kOS had previously supported
     enabling SAS at the same time as locking steering, this functionality broke
     when the underlying KSP method was changed in a version upgrade.  It is our
-    hope to evenentually restore this functionality.  Please check github issue
+    hope to eventually restore this functionality.  Please check github issue
     `#2117 <https://github.com/KSP-KOS/KOS/issues/2117>`_ for updates.
 
 .. _LOCK WHEELTHROTTLE:
@@ -366,8 +366,8 @@ settings that might help solve some problems, in the list below:
 
   - **explanation**: Once it's
     at the desired orientation and it has mostly zeroed the rotational
-    velocity, it's trying to hold it there with microadjustments to the
-    controls, and those microadjustments are "too tight".
+    velocity, it's trying to hold it there with micro-adjustments to the
+    controls, and those micro-adjustments are "too tight".
 
 - **problem**: The vessel is having a hard time holding on to its
   ``lock steering`` direction during a burn when you have physics

doc/source/commands/flight/pilot.rst

@@ -10,7 +10,7 @@ that these suffixes refer to the player's actual input controls, rather
 than kOS's own controls that are layered on top of them, overriding them.
 
 Please note that the *Breaking Ground DLC* parts that can be configured
-to respond to the throttle, such as electric motors and propellor pitches
+to respond to the throttle, such as electric motors and propeller pitches
 will only respond to the settings described here on this page, and NOT
 the settings described in the :ref:`raw control <raw>` page, or the
 settings in ``lock throttle`` or ``lock steering``.  SQUAD designed
@@ -35,7 +35,7 @@ settings that "stay put" and don't reset to center when the pilot lets
 go of the stick.  For example, while ``PILOTPITCH`` matches whatever
 temporary position the pilot's stick is in, ``PILOTPITCHTRIM`` stays
 where it was last set.  Thus ``PILOTPITCHTRIM`` is settable here,
-while ``PILOTPITCH`` is not.  The docmentation below marks which
+while ``PILOTPITCH`` is not.  The documentation below marks which
 suffixes are indeed set-able.  Through the use of these trim-able
 settings, it is possible to control the ship in a way that still
 lets the pilot temporarily grab the controls for a second to override
@@ -139,7 +139,7 @@ what kOS is doing.
     lets go of the controls.
 
     RP-1 Special Case:  If using the RP-1 mod, and flying a "sounding rocket"
-    where the avionics controls are insuficcient to steer but are good
+    where the avionics controls are insufficient to steer but are good
     enough to ignite engines, then ``lock throttle`` does not work to
     activate those engines, but this suffix can do it.  RP-1 actively
     suppresses the normal ability for an autopilot to control the throttle
@@ -164,7 +164,7 @@ what kOS is doing.
 
     Get-only.
 
-    Returns the pilot's rotation input  about the logintudinal axis of the ship left-wing-down :math:`(-1)` or left-wing-up :math:`(+1)`.
+    Returns the pilot's rotation input  about the longitudinal axis of the ship left-wing-down :math:`(-1)` or left-wing-up :math:`(+1)`.
 
 .. _SHIP CONTROL PILOTROTATION:
 .. object:: SHIP:CONTROL:PILOTROTATION

doc/source/commands/flight/raw.rst

@@ -50,7 +50,7 @@ Breaking Ground DLC
 -------------------
 
 Please note that the *Breaking Ground DLC* parts that can be configured
-to respond to the control axes, such as electric motors and propellor
+to respond to the control axes, such as electric motors and propeller
 pitches, will only respond to the settings described on the 
 :ref:`pilot controls page <pilot>` and NOT the settings described
 here on this :ref:`raw control <raw>` page, nor will it respond to
@@ -198,7 +198,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
 
     The reason why this trim does nothing and you have to use the pilot
     trim instead is because KSP only looks at the trim when its part of
-    the *pilot's* own control structure, not an autpilot's control structure.
+    the *pilot's* own control structure, not an autopilot's control structure.
 
     *Warning*:
     Setting this value can cause :ref:`:NEUTRAL <SHIP CONTROL NEUTRAL>` to
@@ -215,7 +215,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
 
     The reason why this trim does nothing and you have to use the pilot
     trim instead is because KSP only looks at the trim when its part of
-    the *pilot's* own control structure, not an autpilot's control structure.
+    the *pilot's* own control structure, not an autopilot's control structure.
 
     *Warning*:
     Setting this value can cause :ref:`NEUTRAL <SHIP CONTROL NEUTRAL>` to
@@ -232,7 +232,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
 
     The reason why this trim does nothing here is because KSP only looks at the
     trim when its part of the *pilot's* own control structure, not an
-    autpilot's control structure.
+    autopilot's control structure.
 
     *Warning*:
     Setting this value can cause :ref:`NEUTRAL <SHIP CONTROL NEUTRAL>` to
@@ -288,7 +288,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
 
     The reason why this trim does nothing here is because KSP only looks at the
     trim when its part of the *pilot's* own control structure, not an
-    autpilot's control structure.
+    autopilot's control structure.
 
     *Warning*:
     Setting this value can cause :ref:`NEUTRAL <SHIP CONTROL NEUTRAL>` to
@@ -305,7 +305,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
 
     The reason why this trim does nothing here is because KSP only looks at the
     trim when its part of the *pilot's* own control structure, not an
-    autpilot's control structure.
+    autopilot's control structure.
 
     *Warning*:
     Setting this value can cause :ref:`NEUTRAL <SHIP CONTROL NEUTRAL>` to
@@ -340,7 +340,7 @@ These "Raw" controls allow you the direct control of flight parameters while the
     The two terms ``NEUTRAL`` and ``NEUTRALIZE`` are synonyms.  (They used to
     be two separate suffixes, one for getting and one for setting, but
     that made no sense so they were combined but both spellings were
-    retained for backward compantiblity with old scripts.)
+    retained for backward compatibility with old scripts.)
 
 
 Unlocking controls