From 07b58a08971daf077e77c7c60c3eb0a295e6ee94 Mon Sep 17 00:00:00 2001
From: Aaron Raff <aaronraffdev@gmail.com>
Date: Wed, 4 Oct 2023 17:17:43 -0400
Subject: [PATCH 1/4] ci-jobs: document temp schema macro limitation

Converts the "Temporary schemas aren't dropping" section into a list of
items. The first item remains the same, but a new item was added to note
that schemas will not be dropped unless they were written to as a result
of running a dbt model.
---
 website/docs/docs/deploy/ci-jobs.md | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md
index fb603e2864e..4a95a8bf8df 100644
--- a/website/docs/docs/deploy/ci-jobs.md
+++ b/website/docs/docs/deploy/ci-jobs.md
@@ -94,10 +94,18 @@ If you're experiencing any issues, review some of the common questions and answe
 <details>
   <summary>Temporary schemas aren't dropping</summary>
   <div>
-    <div>If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates you have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.<br></br><br></br> To resolve this, change your macro so that the temporary PR schema name contains the required prefix. For example: 
+    <div>If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of two issues:
+      <ul>
+        <li> You have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.<br></br><br></br> To resolve this, change your macro so that the temporary PR schema name contains the required prefix. For example:
     <br></br><br></br>
-      • ✅ Temporary PR schema name contains the prefix <code>dbt_cloud_pr_</code> (like <code>dbt_cloud_pr_123_456_marketing</code>) <br></br>
-      • ❌ Temporary PR schema name doesn't contain the prefix <code>dbt_cloud_pr_</code> (like <code>marketing</code>). <br></br>
+        ✅ Temporary PR schema name contains the prefix <code>dbt_cloud_pr_</code> (like <code>dbt_cloud_pr_123_456_marketing</code>) <br></br>
+        ❌ Temporary PR schema name doesn't contain the prefix <code>dbt_cloud_pr_</code> (like <code>marketing</code>). <br></br>
+        </li>
+        <br/>
+        <li>
+          A macro is creating a schema, but no dbt models are writing to that schema. dbt Cloud does not drop temporary schemas that were not written to as a result of running a dbt model.
+        </li>
+      </ul>
     </div>
   </div>
 </details>
@@ -153,6 +161,3 @@ If you're experiencing any issues, review some of the common questions and answe
       If you're on a Virtual Private dbt Enterprise plan using security features like ingress PrivateLink or IP Allowlisting, registering CI hooks may not be available and can cause the job to fail silently.</div>
    </div>
 </details>
-
-
-

From 045f5c3f67c126a22db9b23d7274c28e8f1c16e3 Mon Sep 17 00:00:00 2001
From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
Date: Fri, 6 Oct 2023 13:04:19 -0700
Subject: [PATCH 2/4] Update website/docs/docs/deploy/ci-jobs.md

---
 website/docs/docs/deploy/ci-jobs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md
index 4a95a8bf8df..de8285a5e5b 100644
--- a/website/docs/docs/deploy/ci-jobs.md
+++ b/website/docs/docs/deploy/ci-jobs.md
@@ -98,7 +98,7 @@ If you're experiencing any issues, review some of the common questions and answe
       <ul>
         <li> You have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.<br></br><br></br> To resolve this, change your macro so that the temporary PR schema name contains the required prefix. For example:
     <br></br><br></br>
-        ✅ Temporary PR schema name contains the prefix <code>dbt_cloud_pr_</code> (like <code>dbt_cloud_pr_123_456_marketing</code>) <br></br>
+        ✅ Temporary PR schema name contains the prefix <code>dbt_cloud_pr_</code> (like <code>dbt_cloud_pr_123_456_marketing</code>). <br></br>
         ❌ Temporary PR schema name doesn't contain the prefix <code>dbt_cloud_pr_</code> (like <code>marketing</code>). <br></br>
         </li>
         <br/>

From 7be1c64b446bc818e92957971d20002f0d46eef5 Mon Sep 17 00:00:00 2001
From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
Date: Fri, 6 Oct 2023 13:06:16 -0700
Subject: [PATCH 3/4] Update website/docs/docs/deploy/ci-jobs.md

---
 website/docs/docs/deploy/ci-jobs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md
index de8285a5e5b..86c71b9b313 100644
--- a/website/docs/docs/deploy/ci-jobs.md
+++ b/website/docs/docs/deploy/ci-jobs.md
@@ -103,7 +103,7 @@ If you're experiencing any issues, review some of the common questions and answe
         </li>
         <br/>
         <li>
-          A macro is creating a schema, but no dbt models are writing to that schema. dbt Cloud does not drop temporary schemas that were not written to as a result of running a dbt model.
+          A macro is creating a schema but there are no dbt models writing to that schema. dbt Cloud doesn't drop temporary schemas that weren't written to as a result of running a dbt model.
         </li>
       </ul>
     </div>

From b2ddeae5d14e3a35d0febcc121cdb31ea6b74bfb Mon Sep 17 00:00:00 2001
From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
Date: Fri, 6 Oct 2023 13:06:36 -0700
Subject: [PATCH 4/4] Update website/docs/docs/deploy/ci-jobs.md

---
 website/docs/docs/deploy/ci-jobs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md
index 86c71b9b313..30a858c64e7 100644
--- a/website/docs/docs/deploy/ci-jobs.md
+++ b/website/docs/docs/deploy/ci-jobs.md
@@ -94,7 +94,7 @@ If you're experiencing any issues, review some of the common questions and answe
 <details>
   <summary>Temporary schemas aren't dropping</summary>
   <div>
-    <div>If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of two issues:
+    <div>If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of these issues:
       <ul>
         <li> You have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.<br></br><br></br> To resolve this, change your macro so that the temporary PR schema name contains the required prefix. For example:
     <br></br><br></br>