From b5db9c5c50dcdea5679f8928cf0140e5f9f03844 Mon Sep 17 00:00:00 2001
From: amanda-butler-unity
 <96449283+amanda-butler-unity@users.noreply.github.com>
Date: Fri, 16 May 2025 11:29:29 -0500
Subject: [PATCH] Update QuickStartGuide.md

Fix typos to resolve user-reported bugs DOCATT-8623 and DOCATT-8603
---
 .../com.unity.inputsystem/Documentation~/QuickStartGuide.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Packages/com.unity.inputsystem/Documentation~/QuickStartGuide.md b/Packages/com.unity.inputsystem/Documentation~/QuickStartGuide.md
index ba4f488eca..db944ed22f 100644
--- a/Packages/com.unity.inputsystem/Documentation~/QuickStartGuide.md
+++ b/Packages/com.unity.inputsystem/Documentation~/QuickStartGuide.md
@@ -33,7 +33,7 @@ The Input System's default configuration comes with two Action Maps: "Player" an
 
 The "Player" Action Map defines several game-related actions such as "Move", "Look", "Jump" and "Attack" actions. The "UI" action map defines several user-interface-related actions such as "Navigate", "Submit" and "Cancel".
 
- Each each default action has bindings to several different types of Control. For example:
+ Each default action has bindings to several different types of Control. For example:
 
 - The "Move" action is bound to the "WSAD" keyboard keys and arrow keys, a gamepad stick, the primary 2D axis on an XR controller
 - The "Jump" action is bound to the space key, the "south" button on a gamepad, and the secondary button on an XR controller.
@@ -49,7 +49,7 @@ This workflow uses the following steps:
 
 1. Add the Input System "`using`" statement at the top of your script.
 2. Create variables to hold the Action references.
-3. In your Start method, find the and store the Action references.
+3. In your Start method, find and store the Action references.
 4. In your Update method, read the values from the Action references, and add your own code to respond accordingly.
 
 These steps are shown in the example script below: