From 956ee2af5c99fa3111b214db6f4cffdd39acd668 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Wed, 17 Jan 2024 10:43:03 +0000
Subject: [PATCH] Update content-style-guide.md

replacing the word to with on
---
 contributing/content-style-guide.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md
index 0360ef0e84c..58f5ba2b21c 100644
--- a/contributing/content-style-guide.md
+++ b/contributing/content-style-guide.md
@@ -532,9 +532,9 @@ dbt Core | CLI, dbt CLI
 
 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 
+For example, to explain that a feature is available on 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..” 
 - "Enterprise plans can access XYZ..." to keep users closer to the documentation. 
 
 This will signal users to check their plan or account status independently.