Fixing formatting

Author: suearkinunity

Packages/com.unity.inputsystem/Documentation~/debug-layouts.md

@@ -4,5 +4,4 @@ uid: input-system-debug-layouts
 
 # Debug layouts
 
-The [__Layouts__](layouts.md) list in the Input Debugger window displays a breakdown of all registered [Control and Device layouts](layouts.md). This is the database of supported hardware and the knowledge of how to represent a given piece of input hardware. It's useful when you want to [create a new Device mapping](hid-create-custom-layout.md) and see how the Input System represents it.
-
+The [__Layouts__](layouts.md) list in the Input Debugger window displays a breakdown of all registered [Control and Device layouts](layouts.md). This is the database of supported hardware and the knowledge of how to represent a given piece of input hardware. It's useful when you want to [create a new Device mapping](hid-create-custom-layout.md) and see how the Input System represents it.

Packages/com.unity.inputsystem/Documentation~/debug-users-playerinput.md

@@ -4,5 +4,4 @@ uid: input-system-debug-users-playerinput
 
 # Debug users and PlayerInput
 
-When there are [`InputUser`](user-management.md) instances (if you use `PlayerInput`, each `PlayerInput` instance implicitly creates one), the Input Debugger's __Users__ list displays each instance along with its paired Devices and active Actions. The listed Devices and Actions work the same way as those displayed in the [__Devices__](debug-device.md) and [__Actions__](debug-action.md) lists in the debugging window.
-
+When there are [`InputUser`](user-management.md) instances (if you use `PlayerInput`, each `PlayerInput` instance implicitly creates one), the Input Debugger's __Users__ list displays each instance along with its paired Devices and active Actions. The listed Devices and Actions work the same way as those displayed in the [__Devices__](debug-device.md) and [__Actions__](debug-action.md) lists in the debugging window.

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

@@ -11,15 +11,15 @@ Learn about supported input devices and their unique features in this section.
 | **Topic** | **Description** |
 | :--- | :--- |
 | **[Types of input devices](devices-overview.md)**|Connect devices to your application.|
-| **[Pointer devices](devices-pointers.md)** | Configure devices that track input on a 2D surface, such as mice, or pens. |
+| **[Pointer devices](devices-pointers.md)** | Configure devices that track input on a 2D surface, such as mice, or pens.|
 | **[Keyboards](devices-keyboard.md)** | Configure devices that use a set of key controls.|
-| **[Joysticks](devices-joysticks.md)** | Configure devices that have at least one input stick and one button. |
-| **[Gamepads](devices-gamepads.md)** | Configure devices that have a D-pad and four face buttons. |
-| **[Sensors](devices-sensors.md)** | Configure devices that measure environmental input. |
-| **[Human Interface Device specification](hid-specification.md)** | Use the Human Interface Device specification to implement peripheral user input devices connected to computers with USB or Bluetooth. |
+| **[Joysticks](devices-joysticks.md)** | Configure devices that have at least one input stick and one button.|
+| **[Gamepads](devices-gamepads.md)** | Configure devices that have a D-pad and four face buttons.|
+| **[Sensors](devices-sensors.md)** | Configure devices that measure environmental input.|
+| **[Human Interface Device specification](hid-specification.md)** | Use the Human Interface Device specification to implement peripheral user input devices connected to computers with USB or Bluetooth.|
 | **[Supported devices reference](supported-devices-reference.md)** | Explore platform support for each compatible device. |
-| **[Devices (scripting)](devices-scripting.md)** | Learn how to manage devices in code. |
-| **[Custom devices](custom-devices.md)** | Create events and custom devices. |
+| **[Devices (scripting)](devices-scripting.md)** | Learn how to manage devices in code.|
+| **[Custom devices](custom-devices.md)** | Create events and custom devices.|
 
 ## Additional resources
 

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

@@ -1,6 +1,7 @@
 ---
 uid: input-system-index
 ---
+
 # Input System
 
 The **Input System** allows your users to control your game or app using a device, touch, or gestures.
@@ -14,7 +15,7 @@ The older system, which is built-in to the editor, is called the [Input Manager]
 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).
 
 > [!TIP]
-> During the installation process for the **Input System** package, the installer offers to automatically deactivate the older built-in system. 
+> During the installation process for the **Input System** package, the installer offers to automatically deactivate the older built-in system.
 
 To get started, refer to the [Workflows](workflows.md) section to decide how to use Input:
 
@@ -25,4 +26,4 @@ To get started, refer to the [Workflows](workflows.md) section to decide how to
 For a demo project, refer to 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.*
+*The Input Actions Editor, displaying some of the default actions that come pre-configured with the Input System package.*

Packages/com.unity.inputsystem/Documentation~/supported-devices.md

@@ -37,4 +37,4 @@ Under **Improved Shortcut Support**, two independent options control how the Inp
 
 Both options default to **off**. If **Action Priority Shortcut Resolution** is on, it **takes precedence** over complexity-based resolution even if **Complexity-Based Shortcut Resolution** is also enabled.
 
-For more detail on complexity ordering, see [Multiple input sequences (such as keyboard shortcuts)](xref:input-system-action-bindings#multiple-input-sequences-such-as-keyboard-shortcuts).
+For more detail on complexity ordering, see [Multiple input sequences (such as keyboard shortcuts)](xref:input-system-action-bindings#multiple-input-sequences-such-as-keyboard-shortcuts).

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

@@ -30,7 +30,6 @@ The Input System supports several different workflows, each with its own advanta
 
 **Link**: [Watch video 2/7](https://www.youtube.com/watch?v=Cd2Erk_bsRY) (YouTube)
 
-
 ## Mobile controls
 
 **Description**: The third video in the series demonstrates how to add mobile touch controls to your game using Unity’s Input System:
@@ -40,7 +39,6 @@ The Input System supports several different workflows, each with its own advanta
 
 **Link**: [Watch Video 3/7](https://www.youtube.com/watch?v=aI-r7ILNDug) (YouTube)
 
-
 ## UI toolkit with the Input System
 
 **Description**: The fourth video in the series demonstrates how to integrate the Input System with UI Toolkit:
@@ -59,7 +57,6 @@ The Input System supports several different workflows, each with its own advanta
 
 **Link**: [Watch Video 5/7](https://www.youtube.com/watch?v=JfuqMaOiNPs) (YouTube)
 
-
 ## Player Input Component
 
 **Description**: The sixth video in the series explores preparing a local multiplayer scene, where two or more players share the same computer and screen but use separate controllers: