Reversions up to UISupport.md

Author: unitALG

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

@@ -131,7 +131,7 @@ __Motion Usage__
 
 #### Play Mode Input Behavior
 
-__Play Mode Input Behavior__ determines how input is handled in the Editor when in play mode. Unlike in built players, in the Unity Editor the input back-ends keep running for as long as the Editor is active, regardless of whether a Game View window is focused or not. This setting determines how input should behave when focus is __not__ on any Game View – and thus [`Application.isFocused`](xref:UnityEngine.Application.isFocused) is false and the player considered to be running in the background.
+__Play Mode Input Behavior__ determines how input is handled in the Editor when in play mode. Unlike in built players, in the Unity Editor the input back-ends keep running for as long as the Editor is active, regardless of whether a Game View window is focused or not. This setting determines how input should behave when focus is __not__ on any Game View – and thus [`Application.isFocused`](https://docs.unity3d.com/ScriptReference/Application-isFocused.html) is false and the player considered to be running in the background.
 
 |Setting|Description|
 |-------|-----------|

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

@@ -8,7 +8,7 @@ Touch support is divided into:
 * high-level support implemented in the [`EnhancedTouch.Touch`](#enhancedtouchtouch-class) class.
 
 > [!NOTE]
-> You should not use [`Touchscreen`](#touchscreen-device) for polling. If you want to read out touches similar to [`UnityEngine.Input.touches`](xref:UnityEngine.Input.touches), see [`EnhancedTouch`](#enhancedtouchtouch-class). If you read out touch state from [`Touchscreen`](#touchscreen-device) directly inside of the `Update` or `FixedUpdate` methods, your app will miss changes in touch state.
+> You should not use [`Touchscreen`](#touchscreen-device) for polling. If you want to read out touches similar to [`UnityEngine.Input.touches`](https://docs.unity3d.com/ScriptReference/Input-touches.html), see [`EnhancedTouch`](#enhancedtouchtouch-class). If you read out touch state from [`Touchscreen`](#touchscreen-device) directly inside of the `Update` or `FixedUpdate` methods, your app will miss changes in touch state.
 
 Touch input is supported on Android, iOS, Windows, and the Universal Windows Platform (UWP).
 
@@ -60,7 +60,7 @@ If you bind a single Action to input from multiple touches, you should set the A
 
 ## `EnhancedTouch.Touch` Class
 
-The [`EnhancedTouch.Touch`](xref:UnityEngine.InputSystem.EnhancedTouch.Touch) class provides a polling API for touches similar to [`UnityEngine.Input.touches`](xref:UnityEngine.Input.touches). You can use it to query touches on a frame-by-frame basis.
+The [`EnhancedTouch.Touch`](xref:UnityEngine.InputSystem.EnhancedTouch.Touch) class provides a polling API for touches similar to [`UnityEngine.Input.touches`](https://docs.unity3d.com/ScriptReference/Input-touches.html). You can use it to query touches on a frame-by-frame basis.
 
 Because the API comes with a certain overhead due to having to record touches as they happen, you must explicitly enable it. To do this, call [`EnhancedTouchSupport.Enable()`](xref:UnityEngine.InputSystem.EnhancedTouch.EnhancedTouchSupport.Enable):
 

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

@@ -113,7 +113,7 @@ For each of these types of input, input is sourced and combined from a specific
 
 To the UI, a pointer is a position from which clicks and scrolls can be triggered to interact with UI elements at the pointer's position. Pointer-type input is sourced from [point](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.point), [leftClick](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.leftClick), [rightClick](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.rightClick), [middleClick](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.middleClick), and [scrollWheel](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.scrollWheel).
 
-The UI input module does not have an association between pointers and cursors. In general, the UI is oblivious to whether a cursor exists for a particular pointer. However, for mouse and pen input, the UI input module will respect [Cusor.lockState](xref:UnityEngine.Cursor.lockState) and pin the pointer position at `(-1,-1)` whenever the cursor is locked. This behavior can be changed through the [Cursor Lock Behavior](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.cursorLockBehavior) property of the [InputSystemUIInputModule](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule).
+The UI input module does not have an association between pointers and cursors. In general, the UI is oblivious to whether a cursor exists for a particular pointer. However, for mouse and pen input, the UI input module will respect [Cursor.lockState](https://docs.unity3d.com/ScriptReference/Cursor-lockState.html) and pin the pointer position at `(-1,-1)` whenever the cursor is locked. This behavior can be changed through the [Cursor Lock Behavior](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule.cursorLockBehavior) property of the [InputSystemUIInputModule](xref:UnityEngine.InputSystem.UI.InputSystemUIInputModule).
 
 Multiple pointer Devices may feed input into a single UI input module. Also, in the case of [Touchscreen](xref:UnityEngine.InputSystem.Touchscreen), a single Device can have the ability to have multiple concurrent pointers (each finger contact is one pointer).
 
@@ -257,7 +257,7 @@ Whether such ambiguities exist depends on *how* UIs are used. For example, you c
 
 * All interaction is performed through UI elements. A 2D/3D scene is rendered in the background but all interaction is performed through UI events (including those such as 'background' clicks on the `Canvas`).
 * UI is overlaid over a 2D/3D scene but the UI elements cannot be interacted with directly.
-* UI is overlaid over a 2D/3D scene but there is a clear "mode" switch that determines if interaction is picked up by UI or by the game. For example, a first-person game on desktop may employ a [cursor lock](xref:UnityEngine.Cursor.lockState) and direct input to the game while it is engaged whereas it may leave all interaction to the UI while the lock is not engaged.
+* UI is overlaid over a 2D/3D scene but there is a clear "mode" switch that determines if interaction is picked up by UI or by the game. For example, a first-person game on desktop may employ a [cursor lock](https://docs.unity3d.com/ScriptReference/Cursor-lockState.html) and direct input to the game while it is engaged whereas it may leave all interaction to the UI while the lock is not engaged.
 
 When ambiguities arise, they do so differently for [pointer-type](#pointer-type-input) and [navigation-type](#navigation-type-input).