diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md
index 4ebbf83bf5f..0360ef0e84c 100644
--- a/contributing/content-style-guide.md
+++ b/contributing/content-style-guide.md
@@ -519,6 +519,7 @@ enter (in the command line) | type (in the command line)
 email | e-mail
 on dbt | on a remote server
 person, human | client, customer
+plan(s), account | organization, customer
 press (a key) | hit, tap
 recommended limit | soft limit
 sign in | log in, login
@@ -529,6 +530,15 @@ dbt Cloud CLI | CLI, dbt CLI
 dbt Core | CLI, dbt CLI
 </div></b>
 
+Note, let's make sure we're talking to our readers and keep them close to the content and documentation (second person). 
+
+For example, to explain that a feature is available to a particular dbt Cloud plan, you can use:
+- “XYZ is available on Enterprise plans”,
+- “If you're on an Enterprise plan, you can access XYZ..” or 
+- "Enterprise plans can access XYZ..." to keep users closer to the documentation. 
+
+This will signal users to check their plan or account status independently.
+
 ## Links
 
 Links embedded in the documentation are about trust. Users trust that we will lead them to sites or pages related to their reading content. In order to maintain that trust, it's important that links are transparent, up-to-date, and lead to legitimate resources.