Merge branch 'develop' into mouseevents-samles-tests

Author: ritamerkl

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

@@ -7,7 +7,7 @@ The **Input Actions Editor** allows you to edit [Action Assets](ActionAssets.md)
 
 It allows you to group collections of Actions into [Action Maps](ActionsEditor.html#configure-action-maps), which represent different input scenarios in your project (such as UI navigation, gameplay, etc.)
 
-It also alows you to define [Control Schemes](ActionBindings.md#control-schemes) which are a way to enable or disable a set of devices, or respond to which type of device is being used. This is often useful if you want to customise your UI based on whether your users are using mouse, keyboard, or gamepad as their chosen input.
+It also allows you to define [Control Schemes](ActionBindings.md#control-schemes) which are a way to enable or disable a set of devices, or respond to which type of device is being used. This is often useful if you want to customise your UI based on whether your users are using mouse, keyboard, or gamepad as their chosen input.
 
 ### Action Assets and Project-Wide Actions
 
@@ -45,8 +45,6 @@ The Input Actions editor is divided into three panels (marked A, B & C above).
 * To rename an existing Action, either long-click the name, or right-click the Action Map and select __Rename__ from the context menu.
 * To delete an existing Action, either right-click it and select __Delete__ from the context menu.
 * To duplicate an existing Action, either right-click it and select __Duplicate__ from the context menu.
-*
-
 
 ## Action type and Control type
 
@@ -56,7 +54,7 @@ If you select an Action, you can edit its properties in the right-hand pane of t
 
 #### Action Type
 
-The Action Type setting allows to to select between **Button**, **Value** or **PassThrough**.
+Use the Action Type setting to select **Button**, **Value** or **PassThrough**.
 
 These options relate to whether this action should represent a discrete on/off button-style interaction or a value that can change over time while the control is being used.
 

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

@@ -27,7 +27,6 @@ The following is a list of known limitations that the Input System currently has
 * (Windows) Pen input will not work with Wacom devices if "Windows Ink" support is turned off.
 * (Windows) HID input is not currently supported in 32-bit players. This means that devices such as the PS4 controller will not work in 32-bit standalone players. Use the 64-bit standalone player instead.
 * (Android) We only support a single Touchscreen at the moment.
-* (Stadia) The Stadia controller is only supported __in__ the Stadia player at the moment. In the editor, use the generic `Gamepad` for bindings and use any Xbox or PS4 controller for testing.
 * Joy-Cons are only supported on Switch.
 * Sensors in the PS4 controller are currently only supported on PS4.
   >NOTE: Support for NDA platforms is distributed as separate packages due to licensing restrictions. The packages, at this point, are made available separately to licensees for download and installation.