From f764515ce5db92b1cb9b8ded5f484964414aa97a Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Tue, 10 Oct 2023 18:04:36 +0100
Subject: [PATCH] Update about-cloud-develop-defer.md

---
 website/docs/docs/cloud/about-cloud-develop-defer.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md
index 951ee08db62..cc254216863 100644
--- a/website/docs/docs/cloud/about-cloud-develop-defer.md
+++ b/website/docs/docs/cloud/about-cloud-develop-defer.md
@@ -30,12 +30,14 @@ One key difference between using `--defer` in the Cloud CLI vs the IDE is that d
 
 Cloud CLI offers additional flexibility for declaring which environment is used as the source of deferral artifacts. You can set a `defer-env-id` key in either your `dbt_project.yml` file or your `dbt_cloud.yml` file.
 
+**In the `dbt_cloud.yml` file:**
+
 ```yml
 dever-env-id: '123456'
 ```
+**In the dbt_project.yml file:**
 
 ```yml
-# in dbt_project.yml
 dbt_cloud:
   dever-env-id: '123456'
 ```