Update website/docs/docs/deploy/deploy-environments.md

Co-authored-by: Ly Nguyen <[email protected]>

website/docs/docs/deploy/deploy-environments.md

@@ -57,7 +57,7 @@ Some customers prefer to connect Development and Staging to their `main` branch
 
 ### Why use a staging environment
 
-There are three primary motivations for using a Staging environment:
+These are the primary motivations for using a Staging environment:
 1. An additional validation layer before changes are deployed into Production. You can deploy, test, and explore your dbt models in Staging.
 2. Clear isolation between development workflows and production data. It enables developers to work in metadata-powered ways, using features like deferral and cross-project references, without accessing data in production deployments.
 3. Provide developers with the ability to create, edit, and trigger ad hoc jobs in the Staging environment, while keeping the Production environment locked down using [environment-level permissions](/docs/cloud/manage-access/environment-permissions).