Missing UIDs

Author: suearkinunity

Packages/com.unity.inputsystem/Documentation~/create-custom-composite-binding.md

@@ -1,4 +1,6 @@
-
+---
+uid: input-system-create-custom-composite-binding
+---
 # Create custom composite bindings
 
 You can define new types of Composites, and register them with the API. Unity treats these the same as predefined types, which the Input System internally defines and registers in the same way.
@@ -97,4 +99,4 @@ public class CustomParameterEditor : InputParameterEditor<CustomComposite>
     }
 }
 #endif
-```
+```

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

@@ -1,4 +1,6 @@
-
+---
+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.

Packages/com.unity.inputsystem/Documentation~/multiplayer-event-system-component-input.md

@@ -1,3 +1,6 @@
+---
+uid: input-system-multiplayer-event-system-component
+---
 ## Multiplayer Event System component reference
 
 Use the Multiplayer Event System component to configure input for a specific user in a multiplayer application.
@@ -10,4 +13,4 @@ Use the Multiplayer Event System component to configure input for a specific use
 |**Send Navigation Events**| Define whether the Event System should send navigation events such as move, submit, and cancel. |
 |**Drag Threshold**| Define the soft area for dragging in pixels. |
 |**Player Root**| Define which part of the hierarchy belongs to the current user. |
-|**Add Default Input Modules**| Add the default Input System components to the same GameObject as this Multiplayer Event System component.|
+|**Add Default Input Modules**| Add the default Input System components to the same GameObject as this Multiplayer Event System component.|

Packages/com.unity.inputsystem/Documentation~/timing-input-events-queue.md

@@ -1,3 +1,6 @@
+---
+uid: timing-input-events-queue
+---
 # The input events queue
 
 The Input System receives information from hardware input devices as a stream of events. These events represent either system events received from the input device, or snapshots in time based on frequent samples from the device.

Packages/com.unity.inputsystem/Documentation~/timing-missed-duplicate-events.md

@@ -1,3 +1,6 @@
+---
+uid: timing-missed-duplicate-events
+---
 # Avoid missed or duplicate discrete events
 
 Discrete events are simple on/off events that occur when a user presses or releases a control such as a gamepad button, key, mouse, or touch press. This is in contrast to continuously changing values like those from gamepad stick movement. You can poll for these types of discrete event by using [`WasPressedThisFrame`](xref:UnityEngine.InputSystem.InputAction) or [`WasReleasedThisFrame`](xref:UnityEngine.InputSystem.InputAction). However, you can get incorrect results such as missing an event or appearing to receive multiple, if you check for them at the wrong time.

Packages/com.unity.inputsystem/Documentation~/timing-mixed-scenarios.md

@@ -1,3 +1,6 @@
+---
+uid: timing-mixed-scenarios
+---
 # Mixed timing scenarios with fixed and dynamic input
 
 There are some situations where you might set the Update Mode **process in Dynamic Update** even when using input code in `FixedUpdate`, to minimize input latency, as described in the [previous section](./timing-optimize-fixed-update.md).

Packages/com.unity.inputsystem/Documentation~/timing-optimize-dynamic-update.md

@@ -1,3 +1,6 @@
+---
+uid: timing-optimize-dynamic-update
+---
 # Optimize for dynamic update (non-physics) scenarios
 
 If you're not working with the physics system or using `FixedUpdate`, always set the input system to process input in sync with the frame rate and `Update()` calls. This is the default setting, but to check or set this, go to  **Project Settings** \> **Input System Package** \> **Input Settings**, and set **Update Mode** to **Process Events in Dynamic Update**.

Packages/com.unity.inputsystem/Documentation~/timing-optimize-fixed-update.md

@@ -1,3 +1,6 @@
+---
+uid: timing-optimize-fixed-update
+---
 # Optimize for fixed-timestep or physics-based scenarios
 
 If you are working with the physics system or using `FixedUpdate` to control your game in a scenario where a small amount of input latency is acceptable (for example, a few frames), the simplest approach is to set the [input system update mode](./timing-select-mode.md) to **Process Events in Fixed Update**. This means your input code in `FixedUpdate` will operate as expected.

Packages/com.unity.inputsystem/Documentation~/timing-select-mode.md

@@ -1,3 +1,6 @@
+---
+uid: timing-select-mode
+---
 # Select an appropriate input processing mode
 
 The Input System **Update Mode** controls when the input system processes queued input events.