numerics

Signed-off-by: Faeka Ansari <[email protected]>

docs/docs/20-quickstart.md

@@ -431,7 +431,7 @@ the previous section.
   Kargo uses [semver](https://github.com/masterminds/semver#checking-version-constraints) to handle semantic versioning constraints.
   :::
 
-1. Use the CLI to view our `Warehouse` resource:
+4. Use the CLI to view our `Warehouse` resource:
 
     ```shell
     kargo get warehouses --project kargo-demo
@@ -444,7 +444,7 @@ the previous section.
     kargo-demo           13s
     ```
 
-1. Use the CLI to view our three `Stage` resources:
+5. Use the CLI to view our three `Stage` resources:
 
     ```shell
     kargo get stages --project kargo-demo
@@ -459,7 +459,7 @@ the previous section.
     uat                                       NotApplicable   20s
     ```
 
-1. After a few seconds, our `Warehouse`, which subscribes to the
+6. After a few seconds, our `Warehouse`, which subscribes to the
    `public.ecr.aws/nginx/nginx` container image, also should have already
    produced `Freight`:
 
@@ -487,7 +487,7 @@ the previous section.
     version of the `public.ecr.aws/nginx/nginx` container image.
     :::
 
-4. We'll use it later, so save the ID of the `Freight` to an environment
+7. We'll use it later, so save the ID of the `Freight` to an environment
    variable:
 
     ```shell
@@ -497,7 +497,7 @@ the previous section.
      For additional details and a visual overview, please refer to the Kargo dashboard.
   ![Argo-dashboard-screenshot](../static/img/kargo-dashboard-projects.png)
 
-5. Now, let's _promote_ the `Freight` into the `test` `Stage`:
+8. Now, let's _promote_ the `Freight` into the `test` `Stage`:
 
     ```shell
     kargo promote --project kargo-demo --freight-alias $FREIGHT_ALIAS --stage test
@@ -662,7 +662,7 @@ the previous section.
     ]
     ```
 
-1. If we look at our `Freight` in greater detail, we'll see that by virtue of
+9. If we look at our `Freight` in greater detail, we'll see that by virtue of
    the `test` `Stage` having achieved a `Healthy` state, the `Freight` is now
    _verified_ in `test`, which designates it as eligible for promotion to the
    next `Stage` -- in our case, `uat`.
@@ -715,7 +715,7 @@ our `uat` and `prod` `Stage`s both subscribe to other, _upstream_ `Stage`s,
 thereby forming a _pipeline_:
 
 1. `uat` subscribes to `test`
-1. `prod` subscribes to `uat`.
+2. `prod` subscribes to `uat`.
 
 We leave it as an exercise to the reader to use the `kargo promote` command
 to progress the `Freight` from `test` to `uat` and again from `uat` to `prod`.