Correcting the Order as displayed in dbt cloud (#4237)

## What are you changing in this pull request and why?
This PR is expected to correct the order in which instructions in the
Quickstart documents are listed to match the way it is displayed while
practically working with dbt cli.

### Open Issue for more details:
#4236

## Checklist
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.

website/snippets/quickstarts/schedule-a-job.md

@@ -24,15 +24,16 @@ Jobs are a set of dbt commands that you want to run on a schedule. For example,
 
 As the `jaffle_shop` business gains more customers, and those customers create more orders, you will see more records added to your source data. Because you materialized the `customers` model as a table, you'll need to periodically rebuild your table to ensure that the data stays up-to-date. This update will happen when you run a job.
 
-1. After creating your deployment environment, you should be directed to the page for new environment. If not, select **Deploy** in the upper left, then click **Jobs**.
-2. Click **Create one** and provide a name, for example "Production run", and link to the Environment you just created.
-3. Scroll down to "Execution Settings" and select **Generate docs on run**.
-4. Under "Commands," add this command as part of your job if you don't see them:
-      * `dbt build`
-5. For this exercise, do _not_ set a schedule for your project to run — while your organization's project should run regularly, there's no need to run this example project on a schedule. Scheduling a job is sometimes referred to as _deploying a project_.
-6. Select **Save**, then click **Run now** to run your job.
-7. Click the run and watch its progress under "Run history."
-8. Once the run is complete, click **View Documentation** to see the docs for your project.
+1. After creating your deployment environment, you should be directed to the page for a new environment. If not, select **Deploy** in the upper left, then click **Jobs**.
+2. Click **Create one** and provide a name, for example, "Production run", and link to the Environment you just created.
+3. Scroll down to the **Execution Settings** section.
+4. Under **Commands**, add this command as part of your job if you don't see it:
+   * `dbt build`
+5. Select the **Generate docs on run** checkbox to automatically [generate updated project docs](/docs/collaborate/build-and-view-your-docs) each time your job runs. 
+6. For this exercise, do _not_ set a schedule for your project to run — while your organization's project should run regularly, there's no need to run this example project on a schedule. Scheduling a job is sometimes referred to as _deploying a project_.
+7. Select **Save**, then click **Run now** to run your job.
+8. Click the run and watch its progress under "Run history."
+9. Once the run is complete, click **View Documentation** to see the docs for your project.
 
 :::tip
 Congratulations 🎉! You've just deployed your first dbt project!