diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md
index 4ebbf83bf5f..58f5ba2b21c 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 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.
+
 ## 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.
diff --git a/website/docs/reference/resource-configs/bigquery-configs.md b/website/docs/reference/resource-configs/bigquery-configs.md
index 8f323bc4236..94d06311c55 100644
--- a/website/docs/reference/resource-configs/bigquery-configs.md
+++ b/website/docs/reference/resource-configs/bigquery-configs.md
@@ -596,9 +596,9 @@ with events as (
 
 <VersionBlock firstVersion="1.4">
 
-#### Copying ingestion-time partitions
+#### Copying partitions
 
-If you have configured your incremental model to use "ingestion"-based partitioning (`partition_by.time_ingestion_partitioning: True`), you can opt to use a legacy mechanism for inserting and overwriting partitions. While this mechanism doesn't offer the same visibility and ease of debugging as the SQL `merge` statement, it can yield significant savings in time and cost for large datasets. Behind the scenes, dbt will add or replace each partition via the [copy table API](https://cloud.google.com/bigquery/docs/managing-tables#copy-table) and partition decorators.
+If you are replacing entire partitions in your incremental runs, you can opt to do so with the [copy table API](https://cloud.google.com/bigquery/docs/managing-tables#copy-table) and partition decorators rather than a `merge` statement. While this mechanism doesn't offer the same visibility and ease of debugging as the SQL `merge` statement, it can yield significant savings in time and cost for large datasets because the copy table API does not incur any costs for inserting the data - it's equivalent to the `bq cp` gcloud command line interface (CLI) command.
 
 You can enable this by switching on `copy_partitions: True` in the `partition_by` configuration. This approach works only in combination with "dynamic" partition replacement.