Fix: Updated dever-env-id to defer-env-id in Cloud CLI docs (#4338)

## What are you changing in this pull request and why?
<!---
Describe your changes and why you're making them. If linked to an open
issue or a pull request on dbt Core, then link to them here! 

To learn more about the writing conventions used in the dbt Labs docs,
see the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
-->

Ref issue: #4337

This PR fixes a typo in our Cloud CLI docs, updating `dever-env-id` to
`defer-env-id`.


![image](https://github.com/dbt-labs/docs.getdbt.com/assets/16456253/e94a78c2-fc31-4742-97ad-ed4b4e8ebfcc)

Straightforward :)

I admittedly have not tested this, and I'm not even sure how - but
hoping this is straightforward and perhaps doesn't require versioning?

## Checklist
<!--
Uncomment if you're publishing docs for a prerelease version of dbt
(delete if not applicable):
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
-->
- [ ] 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.
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):
- [ ] Add page to `website/sidebars.js`
- [ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):
- [ ] Remove page from `website/sidebars.js`
- [ ] Add an entry `website/static/_redirects`
- [ ] [Ran link
testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally)
to update the links that point to the deleted page

website/docs/docs/cloud/about-cloud-develop-defer.md

@@ -17,29 +17,29 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr
   - This can be set for one deployment environment per dbt Cloud project.
 - You must have a successful job run first.
 
-When using 'defer', it compares artifacts from the most recent successful production job, excluding CI jobs.
+When using defer, it compares artifacts from the most recent successful production job, excluding CI jobs.
 
 ### Defer in the dbt Cloud IDE
 
-To enable 'Defer' in the dbt Cloud IDE, toggle the **Defer to production** button on the command bar. Once enabled, dbt Cloud will:
+To enable defer in the dbt Cloud IDE, toggle the **Defer to production** button on the command bar. Once enabled, dbt Cloud will:
 
 1. Pull down the most recent manifest from the Production environment for comparison
 2. Pass the `--defer` flag to the command (for any command that accepts the flag)
 
 For example, if you were to start developing on a new branch with [nothing in your development schema](/reference/node-selection/defer#usage), edit a single model, and run `dbt build -s state:modified` —  only the edited model would run. Any `{{ ref() }}` functions will point to the production location of the referenced models.
 
-<Lightbox src="/img/docs/dbt-cloud/defer-toggle.jpg" width="100%" title="Select the 'Defer to production' toggle on the botom right of the command bar to enable defer in the dbt Cloud IDE."/>
+<Lightbox src="/img/docs/dbt-cloud/defer-toggle.jpg" width="100%" title="Select the 'Defer to production' toggle on the bottom right of the command bar to enable defer in the dbt Cloud IDE."/>
 
 ### Defer in dbt Cloud CLI
 
-One key difference between using `--defer` in the dbt Cloud CLI and the dbt Cloud IDE is that `--defer` is *automatically* enabled in the dbt Cloud CLI for all invocations, comparing with production artifacts. You can disable it with the `--no-defer` flag.
+One key difference between using `--defer` in the dbt Cloud CLI and the dbt Cloud IDE is that `--defer` is *automatically* enabled in the dbt Cloud CLI for all invocations, compared with production artifacts. You can disable it with the `--no-defer` flag.
 
-The dbt Cloud CLI offers additional flexibility by letting you choose the source environment for deferral artifacts. You can set a `defer-env-id` key in either your `dbt_project.yml` or `dbt_cloud.yml` file. If you do not provide a `defer-env-id` setting, the dbt Cloud CLI will use artifacts from your dbt Cloud environment marked 'Production'. 
+The dbt Cloud CLI offers additional flexibility by letting you choose the source environment for deferral artifacts. You can set a `defer-env-id` key in either your `dbt_project.yml` or `dbt_cloud.yml` file. If you do not provide a `defer-env-id` setting, the dbt Cloud CLI will use artifacts from your dbt Cloud environment marked "Production". 
 
 <File name="dbt_cloud.yml">
 
   ```yml
-dever-env-id: '123456'
+defer-env-id: '123456'
 ```
 
 </File>
@@ -49,7 +49,7 @@ dever-env-id: '123456'
 
 ```yml
 dbt_cloud:
-  dever-env-id: '123456'
+  defer-env-id: '123456'
 ```
 
 </File>