Small formatting fixes

suearkinunity · suearkinunity · commit ddba04f54b18 · 2026-06-17T13:45:52.000+01:00
diff --git a/Packages/com.unity.inputsystem/Documentation~/Debugging.md b/Packages/com.unity.inputsystem/Documentation~/Debugging.md
@@ -13,8 +13,7 @@ Learn how to investigate and troubleshoot the Input System when something isn't
 | **[Debug an action](debug-action.md)** | Verify enabled actions, bindings, and mapped controls during Play mode. |
 | **[Debug users and PlayerInput](debug-users-playerinput.md)** | Inspect InputUser and Player Input pairings, devices, and actions in the Users list. |
 | **[Debug layouts](debug-layouts.md)** | Browse registered control and device layouts in the Input Debugger. |
-| **[Trace actions](trace-actions)** | 
-Generate a log of all activity that happened on a particular set of Actions. |
+| **[Trace actions](trace-actions)** | Generate a log of all activity that happened on a particular set of Actions. |
 | **[Visualizers](visualizers.md)** | Monitor controls and actions in real time with the Visualizers sample. |
 | **[Device Simulation](device-simulation.md)** | Learn how the Unity Device Simulator feeds touchscreen input into the Input System. |
 
diff --git a/Packages/com.unity.inputsystem/Documentation~/Installation.md b/Packages/com.unity.inputsystem/Documentation~/Installation.md
@@ -3,7 +3,7 @@ uid: input-system-installation
 ---
 # Installation guide
 
-This page describes how to install and activate the Input System package for your Unity Project.
+This page describes how to install and activate the **Input System** package for your Unity Project.
 
 > [!NOTE]
 > This version of the new Input System requires the .NET 4 runtime. It doesn't work in projects using the old .NET 3.5 runtime.
@@ -45,8 +45,14 @@ When the new input backends are enabled, the `ENABLE_INPUT_SYSTEM=1` C# `#define
 
 ## Install samples
 
-The Input System package comes with a number of samples. You can install these directly from the Package Manager window in Unity (__Window > Package Manager__). To see the list of samples, select the Input System package in the Package Manager window and click the __Samples__ tab. Then click __Import__ next to any sample name to import it into the current Project.
+The package comes with a number of samples. You can install these directly from the Package Manager window in Unity (__Window > Package Manager__). 
+
+To view the list of samples:
+
+1. Select the package in the **Package Manager** window.
+1. Select the __Samples__ tab. 
+1. Select __Import__ next to any sample name to import that sample into the current project.
 
 ![Install Samples](Images/InstallSamples.png)
 
-For a more comprehensive demo project for the Input System, see the [InputSystem_Warriors](https://github.com/UnityTechnologies/InputSystem_Warriors) GitHub repository.
+For a more comprehensive demo project for the Input System, refer to the [InputSystem_Warriors](https://github.com/UnityTechnologies/InputSystem_Warriors) GitHub repository.
diff --git a/Packages/com.unity.inputsystem/Documentation~/apply-interactions-actions.md b/Packages/com.unity.inputsystem/Documentation~/apply-interactions-actions.md
@@ -17,7 +17,7 @@ To apply interactions in the Input Action Editor:
 1. Select an Action to edit, so that the right pane of the window displays the properties for that Action. 
 1. Select the plus icon on the __Interactions__ foldout to open a list of all available Interactions types. 
 1. Select an Interaction type to add an Interaction instance of that type. The Interaction now appears in the __Interactions__ foldout. 
-1. If the Interaction has any parameters, you can now edit them at this stage.
+1. If the Interaction has any parameters, you can edit them at this stage.
 
 ## Apply Interactions to Actions in code
 
diff --git a/Packages/com.unity.inputsystem/Documentation~/apply-interactions-bindings.md b/Packages/com.unity.inputsystem/Documentation~/apply-interactions-bindings.md
@@ -15,7 +15,7 @@ If you're using [project-wide actions](actions-editor.md), or [Input action asse
 1. Once you have [created some bindings](actions-editor.md#bindings), select the binding you want to add Interactions to, so that the right pane of the window displays the properties for that binding. 
 1. Select the plus icon on the __Interactions__ foldout to open a list of all available Interactions types. 
 1. Select an Interaction type to add an Interaction instance of that type. The Interaction now appears in the __Interactions__ foldout. 
-1. If the Interaction has any parameters, you can now edit them at this stage.
+1. If the Interaction has any parameters, you can edit them at this stage.
 
 ![Binding Processors](Images/BindingProcessors.png)
 
diff --git a/Packages/com.unity.inputsystem/Documentation~/assign-project-wide-actions.md b/Packages/com.unity.inputsystem/Documentation~/assign-project-wide-actions.md
@@ -4,7 +4,7 @@ uid: input-system-existing-project-wide
 
 # Assign an existing action asset as project-wide
 
-To assign an existing Actions Asset as project-wide, do one of the following:
+To assign an existing actions asset as project-wide, do one of the following:
 
 1. Go to **Edit** > **Project Settings** > **Input System Package**
 2. Drag the asset from your Project window into the **Project-wide Actions** field.
diff --git a/Packages/com.unity.inputsystem/Documentation~/configure-bindings-from-code.md b/Packages/com.unity.inputsystem/Documentation~/configure-bindings-from-code.md
@@ -300,7 +300,7 @@ myAction.AddCompositeBinding("3DVector(mode=2)")
     .With("Right", "<Gamepad>/leftStick/right");
 ```
 
-The 3D vector Composite has four Part Bindings.
+The 3D vector Composite has six Part Bindings.
 
 |Part Binding|Type|Description|
 |----|----|-----------|
diff --git a/Packages/com.unity.inputsystem/Documentation~/configure-ui-input-action-map.md b/Packages/com.unity.inputsystem/Documentation~/configure-ui-input-action-map.md
@@ -27,7 +27,7 @@ To see the specific actions and types that the [UI Input Module](xref:UnityEngin
 
 ## Reset the UI action map
 
-> !IMPORTANT]
+> [!IMPORTANT]
 > These instructions reset both the UI action map and the Player action map to their default bindings.
 
 To reset the UI action map to its default bindings:
diff --git a/Packages/com.unity.inputsystem/Documentation~/create-custom-composite-binding.md b/Packages/com.unity.inputsystem/Documentation~/create-custom-composite-binding.md
@@ -7,7 +7,7 @@ You can define new types of Composites, and register them with the API. Unity tr
 
 To define a new type of Composite, create a class based on [`InputBindingComposite<TValue>`](xref:UnityEngine.InputSystem.InputBindingComposite-1).
 
-> [!Important]
+> [!IMPORTANT] 
 > Composites must be __stateless__. This means that you cannot store local state that changes depending on the input being processed. For __stateful__ processing on bindings, refer to [interactions](write-custom-interactions.md).
 
 ```CSharp
diff --git a/Packages/com.unity.inputsystem/Documentation~/create-events.md b/Packages/com.unity.inputsystem/Documentation~/create-events.md
@@ -39,7 +39,8 @@ InputSystem.QueueStateEvent(Touchscreen.current,
     new TouchState { touchId = 1, phase = TouchPhase.Ended, position = new Vector2(123, 234) });
 ```
 
->__IMPORTANT:__ [Touch IDs](xref:UnityEngine.InputSystem.Controls.TouchControl) cannot be 0! A valid touch must have a non-zero touch ID. Concurrent touches must each have a unique ID. After a touch has ended, its ID can be reused &ndash; although it is recommended to not do so.
+> [!IMPORTANT]
+> [Touch IDs](xref:UnityEngine.InputSystem.Controls.TouchControl) cannot be 0! A valid touch must have a non-zero touch ID. Concurrent touches must each have a unique ID. After a touch has ended, its ID can be reused &ndash; although it is recommended to not do so.
 
 If the exact format of the state used by a given Device is not known, the easiest way to send input to it is to simply create a [`StateEvent`](xref:UnityEngine.InputSystem.LowLevel.StateEvent) from the Device itself:
 
diff --git a/Packages/com.unity.inputsystem/Documentation~/create-precompiled-layout.md b/Packages/com.unity.inputsystem/Documentation~/create-precompiled-layout.md
@@ -20,7 +20,7 @@ Once generated, you can register the precompiled layout with the Input System us
 InputSystem.RegisterPrecompiledLayout<MyPrecompiledDevice>(MyPrecompiledDevice.metadata);
 ```
 
-> [!Important]
+> [!IMPORTANT] 
 > It is very important that this method is called with all relevant layout registrations being in the same state as at the time the layout was precompiled. There is no internal check whether the precompiled layout will still generate an identical result to the non-precompiled version.
 
 Once registered, a precompiled layout is automatically used whenever the layout that the precompiled layout is based on is instantiated.
diff --git a/Packages/com.unity.inputsystem/Documentation~/index.md b/Packages/com.unity.inputsystem/Documentation~/index.md
@@ -9,13 +9,16 @@ The **Input System** allows your users to control your game or app using a devic
 
 Unity supports input through two separate systems, one older, and one newer.
 
-The older system, which is built-in to the editor, is called the [Input Manager](https://docs.unity3d.com/Manual/class-InputManager.html). The Input Manager is part of the core Unity platform and is the default, if you do not install this Input System Package.
+The older system, which is built-in to the editor, is called the [Input Manager](https://docs.unity3d.com/Manual/class-InputManager.html). The Input Manager is part of the core Unity platform and is the default, if you do not install the Input System package.
 
-This **Input System package** is a newer, more flexible system, which allows you to use any kind of Input Device to control your Unity content. It's intended to be a replacement for Unity's classic Input Manager. It is referred to as "The Input System Package", or just **The Input System**. To use it, you must [install it into your project using the Package Manager](Installation.md).
+This **Input System package** is a newer, more flexible system, which allows you to use any kind of Input Device to control your Unity content. It's intended to be a replacement for Unity's classic Input Manager. It is referred to as the "Input" System Package, or just **The Input System**. To use it, you must [install it into your project using the Package Manager](Installation.md).
 
-During the installation process for the Input System package, the installer offers to automatically deactivate the older built-in system. ([Read more](Installation.md))
+> [!TIP]
+> During the installation process for the **Input System** package, the installer offers to automatically deactivate the older built-in system. 
 
-To get started, see the [Installation](Installation.md) and [Workflows](workflows.md) sections. For a demo project, see the [Warriors demo](https://github.com/UnityTechnologies/InputSystem_Warriors) on GitHub.
+To get started, refer to the [Installation](Installation.md) and [Workflows](workflows.md) sections. 
+
+For a demo project, refer tp the [Warriors demo](https://github.com/UnityTechnologies/InputSystem_Warriors) on GitHub.
 
 ![Screenshot of the Input Actions Editor window displaying the default action map, Actions, and Action Properties. They are displayed in 3 columns side-by-side in that order.](Images/ActionsEditor.png)<br/>
 *The Input Actions Editor, displaying some of the default actions that come pre-configured with the Input System package.*
diff --git a/Packages/com.unity.inputsystem/Documentation~/interactive-rebinding.md b/Packages/com.unity.inputsystem/Documentation~/interactive-rebinding.md
@@ -9,7 +9,8 @@ Runtime rebinding allows users of your application to set their own bindings.
 
 To allow users to choose their own bindings interactively, use the  [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) class. Call the [`PerformInteractiveRebinding()`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions) method on an Action to create a rebinding operation. This operation waits for the Input System to register any input from any Device which matches the Action's expected Control type, then uses [`InputBinding.overridePath`](xref:UnityEngine.InputSystem.InputBinding) to assign the Control path for that Control to the Action's bindings. If the user actuates multiple Controls, the rebinding operation chooses the Control with the highest [magnitude](controls.md#control-actuation).
 
->IMPORTANT: You must dispose of [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) instances with `Dispose()`, so that they don't leak memory on the unmanaged memory heap.
+> [!IMPORTANT] 
+> You must dispose of [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) instances with `Dispose()`, so that they don't leak memory on the unmanaged memory heap.
 
 ```C#
     void RemapButtonClicked(InputAction actionToRebind)
diff --git a/Packages/com.unity.inputsystem/Documentation~/rebind-action-runtime.md b/Packages/com.unity.inputsystem/Documentation~/rebind-action-runtime.md
@@ -10,7 +10,8 @@ Runtime rebinding allows users of your application to set their own bindings.
 
 To allow users to choose their own bindings interactively, use the  [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) class. Call the [`PerformInteractiveRebinding()`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions) method on an Action to create a rebinding operation. This operation waits for the Input System to register any input from any Device which matches the Action's expected Control type, then uses [`InputBinding.overridePath`](xref:UnityEngine.InputSystem.InputBinding) to assign the Control path for that Control to the Action's bindings. If the user actuates multiple Controls, the rebinding operation chooses the Control with the highest [magnitude](controls.md#control-actuation).
 
->IMPORTANT: You must dispose of [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) instances with `Dispose()`, so that they don't leak memory on the unmanaged memory heap.
+> [!IMPORTANT] 
+> You must dispose of [`InputActionRebindingExtensions.RebindingOperation`](xref:UnityEngine.InputSystem.InputActionRebindingExtensions.RebindingOperation) instances with `Dispose()`, so that they don't leak memory on the unmanaged memory heap.
 
 ```C#
     void RemapButtonClicked(InputAction actionToRebind)
diff --git a/Packages/com.unity.inputsystem/Documentation~/set-up-test-fixtures.md b/Packages/com.unity.inputsystem/Documentation~/set-up-test-fixtures.md
@@ -40,7 +40,8 @@ class MyTests : InputTestFixture
 }
 ```
 
->__IMPORTANT:__ If you do this, do __not__ add a `[SetUp]` or `[TearDown]` method. Doing so will cause the methods in [`InputTestFixture`](xref:UnityEngine.InputSystem.InputTestFixture) to not be called, thus leading to the test fixture not properly initializing or shutting down. Instead, override the `Setup` and/or `TearDown` method inherited from `InputTestFixture`.
+> [!IMPORTANT] 
+> If you do this, do __not__ add a `[SetUp]` or `[TearDown]` method. Doing so will cause the methods in [`InputTestFixture`](xref:UnityEngine.InputSystem.InputTestFixture) to not be called, thus leading to the test fixture not properly initializing or shutting down. Instead, override the `Setup` and/or `TearDown` method inherited from `InputTestFixture`.
 
 Alternatively, you can instantiate it in your fixture:
 
diff --git a/Packages/com.unity.inputsystem/Documentation~/ui-input-module-reference.md b/Packages/com.unity.inputsystem/Documentation~/ui-input-module-reference.md
@@ -10,7 +10,6 @@ The properties on the UI Input Module correspond to the [`InputSystemUIInputModu
 
 |**Property**|**Description**|
 |--------|-----------|
-<!-- |Send Pointer Hover to Parent | TODO: No description available | -->
 |**Move Repeat Delay**|The initial delay (in seconds) between generating an initial [IMoveHandler.OnMove](https://docs.unity3d.com/Packages/com.unity.ugui@1.0/api/UnityEngine.EventSystems.IMoveHandler.html) navigation event and generating repeated navigation events when the __Move__ action stays actuated.|
 |**Move Repeat Rate**|The interval (in seconds) between generating repeat navigation events when the __Move__ action stays actuated. Note that this is capped by the frame rate; there will not be more than one move repeat event each frame so if the frame rate dips below the repeat rate, the effective repeat rate will be lower than this setting.|
 |**XR Tracking Origin** | Define the transform that represents the real-world transform for tracking devices. |
