Running formatting script to pass the CI job

Author: josepmariapujol-unity

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

@@ -23,4 +23,3 @@ Learn how to investigate and troubleshoot the Input System when something isn't
 - [Testing](testing.md)
 - [Binding resolution](binding-resolution.md)
 - [Debug Player Input Component](debug-player-input-component.md)
-

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

@@ -6,4 +6,4 @@ uid: input-system-events
 | Topic | Description |
 | --- | --- |
 
-## Additional resources
+## Additional resources

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

@@ -45,14 +45,14 @@ When the new input backends are enabled, the `ENABLE_INPUT_SYSTEM=1` C# `#define
 
 ## Install samples
 
-The package comes with a number of samples. You can install these directly from the Package Manager window in Unity (__Window > Package Manager__). 
+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 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, refer to 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.

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

@@ -19,4 +19,4 @@ Use interactions to interpret specific input patterns from controls that define
 - [Bindings](bindings.md)
 - [Processors](processors.md)
 - [Configure actions](configure-actions.md)
-- [Responding to input](respond-to-input.md)
+- [Responding to input](respond-to-input.md)

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

@@ -19,4 +19,4 @@ Use an input processor to apply processing to input values and return the result
 - [Bindings](bindings.md)
 - [Interactions](Interactions.md)
 - [Configure actions](configure-actions.md)
-- [Configure bs from code](configure-bindings-from-code.md)
+- [Configure bs from code](configure-bindings-from-code.md)

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

@@ -81,7 +81,7 @@
   * [Set callbacks on actions](set-callbacks-on-actions.md)
   * [Read devices directly](read-devices-directly.md)
   * [Scripting with actions API overview](api-overview.md)
-  * [The Player Input component](player-input-component.md)			
+  * [The Player Input component](player-input-component.md)
     * [About the Player Input Component](about-player-input-component.md)
     * [Get started with the Player Input component](get-started-player-input-component.md)
     * [Select a notification behavior](select-notification-behavior.md)
@@ -96,19 +96,19 @@
     * [Configure the Player Input Manager](configure-player-input-manager-component.md)
     * [Set up split-screen local multiplayer](set-up-split-screen-local-multiplayer.md)
 * [User rebinding at runtime](user-rebinding-runtime.md)
-  * [Look up bindings](look-up-bindings.md) 						
-  *	[Display bindings](display-bindings.md)
-  * [Rebind an action at runtime](rebind-action-runtime.md)				
+  * [Look up bindings](look-up-bindings.md)
+  * [Display bindings](display-bindings.md)
+  * [Rebind an action at runtime](rebind-action-runtime.md)
   * [Save and load rebinds](save-load-rebinds.md)
   * [Restore original bindings](restore-original-bindings.md)
-* [Input settings](input-settings.md)		
+* [Input settings](input-settings.md)
   * [Create a settings asset](create-settings-asset.md)
   * [Update Mode](update-mode.md)
   * [Background behavior](background-behavior.md)
   * [Compensate orientation](compensate-orientation.md)
   * [Default value properties](default-value-properties.md)
   * [Supported devices](supported-devices.md)
-  * [Platform-specific settings](platform-specific-settings.md)				
+  * [Platform-specific settings](platform-specific-settings.md)
 * [Devices](devices.md)
   * [Types of input devices](devices-overview.md)
   * [Pointer devices](devices-pointers.md)
@@ -171,7 +171,7 @@
       * [Synthesize a device state change](synthesize-device-state-change.md)
     * [Working with devices](working-with-devices.md)
       * [Monitor devices](monitor-devices.md)
-      * [Manually add and remove devices](manually-add-remove-devices.md)					
+      * [Manually add and remove devices](manually-add-remove-devices.md)
   * [Custom devices](custom-devices.md)
     * [Input events](input-events.md)
       * [Types of events](types-of-events.md)
@@ -187,7 +187,7 @@
       * [Step 3 The Update method](step-3-update-method.md)
       * [Step 4 Device registration and creation](step-4-device-registration-creation.md)
       * [Step 5 current and all (optional)](step-5-current-all-optional.md)
-      * [Step 6 Device Commands (Optional)](step-6-device-commands-optional.md)		
+      * [Step 6 Device Commands (Optional)](step-6-device-commands-optional.md)
 * [Input for user interfaces](ui-input.md)
   * [Supported UI systems](supported-ui-systems.md)
     * [Understand UI system compatibility](understand-ui-compatibility.md)
@@ -236,7 +236,7 @@
   * [Visualizers](visualizers.md)
     * [Visualise input controls](visualise-input-controls.md)
     * [Visualise actions](visualise-actions.md)
-  * [Device Simulation](device-simulation.md)			
+  * [Device Simulation](device-simulation.md)
 * [Testing](testing.md)
   * [Set up test assemblies](set-up-test-assemblies.md)
   * [Set up test fixtures](set-up-test-fixtures.md)
@@ -251,14 +251,14 @@
   * [Control items](control-items.md)
   * [Override layout definitions](override-layout-definitions.md)
   * [Precompiled layouts](precompiled-layouts.md)
-    * [Create a precompiled layout](create-precompiled-layout.md)				
+    * [Create a precompiled layout](create-precompiled-layout.md)
 * [User management](user-management.md)
   * [About user management](about-user-management.md)
   * [Create a user paired with an input device](create-user-paired-with-input-device.md)
-  * [Handle loss of a device](handle-loss-of-device.md)	
+  * [Handle loss of a device](handle-loss-of-device.md)
 * [Migrate from the old input system](migrate-from-old-input-system.md)
   * [Enable the correct input system](enable-correct-input-system.md)
-  * [Corresponding old and new APIs](corresponding-old-new-api.md)			
+  * [Corresponding old and new APIs](corresponding-old-new-api.md)
 * [How do I...?](HowDoI.md)
 * [Architecture](Architecture.md)
 * [Contribute to the Input System source code](Contributing.md)

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

@@ -21,4 +21,4 @@ The descriptions below describe these main workflows and link to more detailed d
 |[**Directly read device states**](Workflow-Direct.md)|This workflow is a simplified, script-only approach which bypasses the actions and bindings features entirely. Instead your script explicitly references specific device controls (such as "left gamepad stick") and reads the values directly. This is suitable for **fast prototyping**, or single fixed platform scenarios. It is a **less flexible** workflow because it bypasses some of the main input system features.|
 
 > [!NOTE]
-> Because the Input System has multiple workflows, the code samples used throughout this documentation also vary, often demonstrating techniques using various workflows. For example, some code samples may use Action references, and some may use the workflow of reading input directly from devices.
+> Because the Input System has multiple workflows, the code samples used throughout this documentation also vary, often demonstrating techniques using various workflows. For example, some code samples may use Action references, and some may use the workflow of reading input directly from devices.

Packages/com.unity.inputsystem/Documentation~/about-action-assets.md

@@ -12,5 +12,4 @@ The Input System creates an action asset when you set up the [default project-wi
 
 ## Action maps
 
-Actions assets allow you to group sets of related actions into [action maps](./create-edit-delete-action-maps.md). For example, in an open-world city game, you might create separate action maps for different situations such as exploring on foot, driving a car, flying an aircraft, or navigating UI interfaces. This means, for most common scenarios, you don't need to use more than one Input action asset. 
-
+Actions assets allow you to group sets of related actions into [action maps](./create-edit-delete-action-maps.md). For example, in an open-world city game, you might create separate action maps for different situations such as exploring on foot, driving a car, flying an aircraft, or navigating UI interfaces. This means, for most common scenarios, you don't need to use more than one Input action asset.

Packages/com.unity.inputsystem/Documentation~/about-action-control-types.md

@@ -16,11 +16,10 @@ The **action type** influences how the Input System processes state changes for
 
 ## Control type
 
-The **control type** determines the type of value that should be sent to the action, such as an in integer or float value, or a 1D, 2D, or 3D axis. 
+The **control type** determines the type of value that should be sent to the action, such as an in integer or float value, or a 1D, 2D, or 3D axis.
 
 The control type that you select has the effect of filtering the available controls to only those that are capable of providing the values appropriate for that control.
 
 For example, if you select **2D axis** as the control type, only those types of controls that can supply a 2D vector as value are available as options for the binding control path, such as a thumb stick or Dpad.
 
 There are more specific control types available which further filter the available bindings, such as **Stick**, **Dpad** or **Touch**. If you select one of these control types, the list of available controls is further limited to only those controls of those specific types when you [select a binding for your action](add-duplicate-delete-binding.md).
-

Packages/com.unity.inputsystem/Documentation~/about-responding-to-input.md

@@ -11,7 +11,7 @@ The Input System offers various ways to respond to input at runtime, from the re
 Working with the Input System's [recommended workflow](workflows.md) in your project involves two phases which you must approach in this order:
 
 1. Configure your project's actions.
-2. Implement responses to actions. 
+2. Implement responses to actions.
 
 ### Configure your project's actions
 
@@ -36,4 +36,3 @@ For most common scenarios, especially action games where the user's input has a
 The Input System also allows you to read device states directly, which bypasses many of the features such as actions and bindings. This workflow is suitable for fast prototyping, or single fixed platform scenarios, but is a less flexible workflow because it bypasses some useful Input System features.
 
 Refer to [Read devices directly](read-devices-directly.md) for further information about this workflow.
-