diff --git a/website/docs/reference/resource-configs/bigquery-configs.md b/website/docs/reference/resource-configs/bigquery-configs.md
index 88ae6e9d193..b943f114861 100644
--- a/website/docs/reference/resource-configs/bigquery-configs.md
+++ b/website/docs/reference/resource-configs/bigquery-configs.md
@@ -265,7 +265,7 @@ If your model has `partition_by` configured, you may optionally specify two addi
-### Clustering Clause
+### Clustering clause
BigQuery tables can be [clustered](https://cloud.google.com/bigquery/docs/clustered-tables) to colocate related data.
@@ -286,7 +286,7 @@ select * from ...
-Clustering on a multiple columns:
+Clustering on multiple columns:
@@ -303,11 +303,11 @@ select * from ...
-## Managing KMS Encryption
+## Managing KMS encryption
[Customer managed encryption keys](https://cloud.google.com/bigquery/docs/customer-managed-encryption) can be configured for BigQuery tables using the `kms_key_name` model configuration.
-### Using KMS Encryption
+### Using KMS encryption
To specify the KMS key name for a model (or a group of models), use the `kms_key_name` model configuration. The following example sets the `kms_key_name` for all of the models in the `encrypted/` directory of your dbt project.
@@ -328,7 +328,7 @@ models:
-## Labels and Tags
+## Labels and tags
### Specifying labels
@@ -373,8 +373,6 @@ models:
-
-
### Specifying tags
@@ -434,7 +432,7 @@ The `incremental_strategy` config can be set to one of two values:
### Performance and cost
The operations performed by dbt while building a BigQuery incremental model can
-be made cheaper and faster by using [clustering keys](#clustering-keys) in your
+be made cheaper and faster by using a [clustering clause](#clustering-clause) in your
model configuration. See [this guide](https://discourse.getdbt.com/t/benchmarking-incremental-strategies-on-bigquery/981) for more information on performance tuning for BigQuery incremental models.
**Note:** These performance and cost benefits are applicable to incremental models
@@ -673,7 +671,7 @@ select ...
-## Authorized Views
+## Authorized views
If the `grant_access_to` config is specified for a model materialized as a
view, dbt will grant the view model access to select from the list of datasets