Formatting

Author: suearkinunity

Packages/com.unity.inputsystem/Documentation~/interactive-rebinding.md

@@ -3,7 +3,8 @@ uid: input-system-interactive-rebinding
 ---
 ## Interactive rebinding
 
->__Note:__ To download a sample project which demonstrates how to set up a rebinding user interface with Input System APIs, open the Package Manager, select the Input System Package, and choose the sample project "Rebinding UI" to download.
+> [!NOTE]
+> To download a sample project which demonstrates how to set up a rebinding user interface with Input System APIs, open the Package Manager, select the Input System Package, and choose the sample project "Rebinding UI" to download.
 
 Runtime rebinding allows users of your application to set their own bindings.
 

Packages/com.unity.inputsystem/Documentation~/rebind-action-runtime.md

@@ -4,7 +4,8 @@ uid: input-system-rebind-at-runtime
 
 # Rebind an action at runtime 
 
->__Note:__ To download a sample project which demonstrates how to set up a rebinding user interface with Input System APIs, open the Package Manager, select the Input System Package, and choose the sample project "Rebinding UI" to download.
+> [!NOTE]
+> To download a sample project which demonstrates how to set up a rebinding user interface with Input System APIs, open the Package Manager, select the Input System Package, and choose the sample project "Rebinding UI" to download.
 
 Runtime rebinding allows users of your application to set their own bindings.
 

Packages/com.unity.inputsystem/Documentation~/set-up-test-fixtures.md

@@ -6,7 +6,8 @@ uid: input-system-set-up-test-fixtures
 
 Use [`InputTestFixture`](xref:UnityEngine.InputSystem.InputTestFixture) to create an isolated version of the Input System for tests. The fixture sets up a blank, default-initialized version of the Input System for each test, and restores the Input System to its original state after the test completes. The default-initialized version has all built-in registrations (such as layout and processors), but doesn't have any pre-existing Input Devices.
 
->__NOTE:__ [`InputTestFixture`](xref:UnityEngine.InputSystem.InputTestFixture) will not have custom registrations performed from Unity startup code such as `[InitializeOnLoad]` or `[RuntimeInitializeOnLoadMethod]`. Layouts needed during tests have to be manually registered as part of the test setup.
+> [!NOTE]
+> [`InputTestFixture`](xref:UnityEngine.InputSystem.InputTestFixture) will not have custom registrations performed from Unity startup code such as `[InitializeOnLoad]` or `[RuntimeInitializeOnLoadMethod]`. Layouts needed during tests have to be manually registered as part of the test setup.
 
 You can use the fixture as a base class for your own fixture: