Merge branch 'trackedposedriver-stops-tracking' of https://github.com/Unity-Technologies/InputSystem into trackedposedriver-stops-tracking

Author: ritamerkl

Packages/com.unity.inputsystem/Documentation~/ProjectWideActions.md

@@ -9,7 +9,7 @@ While it's possible to have more than one Action Asset in a project, most projec
 
 The Input System's **project-wide actions** feature allows you to choose an individual Action Asset as being available project-wide, which means the actions within that asset are available more conveniently through the Input System API without needing to set up a reference to the Actions Asset.
 
-The Action Asset assigned as project-wide is also a [preloaded asset](https://docs.unity3d.com/ScriptReference/PlayerSettings.GetPreloadedAssets.html), loaded when your app starts up, and kept available until until it terminates.
+The Action Asset assigned as project-wide is also a [preloaded asset](https://docs.unity3d.com/ScriptReference/PlayerSettings.GetPreloadedAssets.html), loaded when your app starts up, and kept available until it terminates.
 
 Unless you have specific project requirements that require more than one Action Asset, the recommended workflow is to use a single Action Asset assigned as the project-wide actions, as described below.
 
@@ -40,7 +40,7 @@ When you create and assign default project-wide actions using the method describ
 
 These default actions mean that in many cases, you can start scripting with the Input System without any configuration by referring to the names of the default actions that are already configured for you. You can also rename and reconfigure the default actions, or delete these default configurations to suit your needs.
 
-If you’d like to delete all the default actions so that you can start from an empty configuration, you don’t need to delete the individual actions one-by-one. You can delete the each Action Map, which deletes all the Actions contained in the maps in one go.
+If you’d like to delete all the default actions so that you can start from an empty configuration, you don’t need to delete the individual actions one-by-one. You can delete each Action Map, which deletes all the Actions contained in the maps in one go.
 
 You can also delete all action maps, or reset all the actions back to the default values from the **more** (⋮) menu at the top right of the Input Actions section of the settings window, below the Project Settings window search field.
 

Packages/com.unity.inputsystem/Documentation~/QuickStartGuide.md

@@ -33,7 +33,7 @@ The Input System's default configuration comes with two Action Maps: "Player" an
 
 The "Player" Action Map defines several game-related actions such as "Move", "Look", "Jump" and "Attack" actions. The "UI" action map defines several user-interface-related actions such as "Navigate", "Submit" and "Cancel".
 
- Each each default action has bindings to several different types of Control. For example:
+ Each default action has bindings to several different types of Control. For example:
 
 - The "Move" action is bound to the "WSAD" keyboard keys and arrow keys, a gamepad stick, the primary 2D axis on an XR controller
 - The "Jump" action is bound to the space key, the "south" button on a gamepad, and the secondary button on an XR controller.
@@ -49,7 +49,7 @@ This workflow uses the following steps:
 
 1. Add the Input System "`using`" statement at the top of your script.
 2. Create variables to hold the Action references.
-3. In your Start method, find the and store the Action references.
+3. In your Start method, find and store the Action references.
 4. In your Update method, read the values from the Action references, and add your own code to respond accordingly.
 
 These steps are shown in the example script below: