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

Co-authored-by: Jo Dawes <[email protected]>

Author: duckets

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

@@ -14,7 +14,7 @@ Because a device can cause events at times when the input system can't process t
 
 Unity’s player loop repeats at frequent intervals depending on how fast your game or app is running. The player loop repeats once per frame, and performs the Update and FixedUpdate calls. However, the player loop in your game or app usually runs at a rate that's different to the rate of incoming events from input controls, which tend to have their own rate of operation.
 
-This means that each time an Update cycle occurs while a user is moving an input control, there's likely to be a queue of events representing the gradual change in values that occurred between the last frame and the current frame. This queue is processed at the beginning of the next Update or FixedUpdate, depending on which [**Input Update Mode**](./timing-select-mode.md) you're using.
+This means that each time an Update cycle occurs while a user is moving an input control, there's likely to be a queue of events representing the gradual change in values that occurred between the last frame and the current frame. This queue is processed at the beginning of the next Update or FixedUpdate, depending on which [**Input Update Mode**](timing-select-mode.md) you're using.
 
 ## Event grouping and processing