Style updates to core directory (#8075)

Author: matthewshaver

website/docs/docs/core/connect-data-platform/bigquery-setup.md

@@ -292,7 +292,7 @@ my-profile:
 ### Dataset locations
 
 The location of BigQuery datasets can be configured using the `location` configuration in a BigQuery profile.
-`location` may be either a multi-regional location (e.g. `EU`, `US`), or a regional location (e.g. `us-west2` ) as per [the BigQuery documentation](https://cloud.google.com/bigquery/docs/locations) describes.
+`location` may be either a multi-regional location (for example, `EU`, `US`), or a regional location (for example, `us-west2` ) as per [the BigQuery documentation](https://cloud.google.com/bigquery/docs/locations) describes.
 Example:
 
 ```yaml

website/docs/docs/core/connect-data-platform/clickhouse-setup.md

@@ -37,7 +37,7 @@ clickhouse-service:
       schema: [ default ]  # ClickHouse database for dbt models
 
       # optional
-      host: [ <your-clickhouse-host> ]  # Your clickhouse cluster url e.g., abc123.clickhouse.cloud. Defaults to `localhost`.
+      host: [ <your-clickhouse-host> ]  # Your clickhouse cluster url for example, abc123.clickhouse.cloud. Defaults to `localhost`.
       port: [ 8123 ]  # Defaults to 8123, 8443, 9000, 9440 depending on the secure and driver settings 
       user: [ default ]  # User for all database operations
       password: [ <empty string> ]  # Password for the user

website/docs/docs/core/connect-data-platform/dremio-setup.md

@@ -169,5 +169,5 @@ For descriptions of the configurations in these profiles, see [Configurations](#
 | `port` | Yes | `9047` | Port for Dremio Software cluster API endpoints. | 
 | `user` | Yes | None | The username of the account to use when logging into the Dremio cluster. | 
 | `password` | Yes, if you are not using the pat configuration. | None | The password of the account to use when logging into the Dremio cluster. | 
-| `pat` | Yes, if you are not using the user and password configurations. | None | The personal access token to use for authenticating to Dremio. See [Personal Access Tokens](https://docs.dremio.com/software/security/personal-access-tokens/) for instructions about obtaining a token. The use of a personal access token takes precedence if values for the three configurations user, password and pat are specified. | 
+| `pat` | Yes, if you are not using the user and password configurations. | None | The personal access token to use for authenticating to Dremio. See [Personal Access Tokens](https://docs.dremio.com/software/security/personal-access-tokens/) for instructions about obtaining a token. The use of a personal access token takes precedence if values for the three configurations user, password, and pat are specified. | 
 | `use_ssl` | Yes | `true` | Acceptable values are `true` and `false`. If the value is set to true, ensure that full wire encryption is configured in your Dremio cluster. See [Prerequisites for Dremio Software](#prerequisites-for-dremio-software). | 

website/docs/docs/core/connect-data-platform/hive-setup.md

@@ -85,7 +85,7 @@ your_profile_name:
 
 </File>
 
-Note: When creating workload user in CDP, make sure the user has CREATE, SELECT, ALTER, INSERT, UPDATE, DROP, INDEX, READ and WRITE permissions. If you need the user to execute GRANT statements, you should also configure the appropriate GRANT permissions for them. When using Apache Ranger, permissions for allowing GRANT are typically set using "Delegate Admin" option. For more information, see [`grants`](/reference/resource-configs/grants) and [on-run-start & on-run-end](/reference/project-configs/on-run-start-on-run-end).
+Note: When creating workload user in CDP, make sure the user has CREATE, SELECT, ALTER, INSERT, UPDATE, DROP, INDEX, READ, and WRITE permissions. If you need the user to execute GRANT statements, you should also configure the appropriate GRANT permissions for them. When using Apache Ranger, permissions for allowing GRANT are typically set using "Delegate Admin" option. For more information, see [`grants`](/reference/resource-configs/grants) and [on-run-start & on-run-end](/reference/project-configs/on-run-start-on-run-end).
 
 ### Kerberos
 

website/docs/docs/core/connect-data-platform/impala-setup.md

@@ -91,7 +91,7 @@ your_profile_name:
 
 </File>
 
-Note: When creating workload user in CDP ensure that the user has CREATE, SELECT, ALTER, INSERT, UPDATE, DROP, INDEX, READ and WRITE permissions. If the user is required to execute GRANT statements, see for instance (/reference/resource-configs/grants) or (/reference/project-configs/on-run-start-on-run-end) appropriate GRANT permissions should be configured. When using Apache Ranger, permissions for allowing GRANT are typically set using "Delegate Admin" option. 
+Note: When creating workload user in CDP ensure that the user has CREATE, SELECT, ALTER, INSERT, UPDATE, DROP, INDEX, READ, and WRITE permissions. If the user is required to execute GRANT statements, see for instance (/reference/resource-configs/grants) or (/reference/project-configs/on-run-start-on-run-end) appropriate GRANT permissions should be configured. When using Apache Ranger, permissions for allowing GRANT are typically set using "Delegate Admin" option. 
 
 ### Kerberos
 

website/docs/docs/core/connect-data-platform/maxcompute-setup.md

@@ -88,7 +88,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: access_key # credential type, Optional, default is 'access_key'
       access_key_id: accessKeyId # AccessKeyId
@@ -106,7 +106,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: sts # credential type
       access_key_id: accessKeyId # AccessKeyId
@@ -125,7 +125,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: ram_role_arn # credential type
       access_key_id: accessKeyId # AccessKeyId
@@ -148,7 +148,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: oidc_role_arn # credential type
       access_key_id: accessKeyId # AccessKeyId
@@ -181,7 +181,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: ecs_ram_role # credential type
       role_name: roleName # `role_name` is optional. It will be retrieved automatically if not set. It is highly recommended to set it up to reduce requests.
@@ -199,7 +199,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: credentials_uri # credential type
       credentials_uri: http://local_or_remote_uri/ # Credentials URI
@@ -216,7 +216,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: bearer # credential type
       bearer_token: bearerToken # BearerToken
@@ -231,7 +231,7 @@ jaffle_shop: # this needs to match the profile in your dbt_project.yml file
     dev:
       type: maxcompute
       project: dbt-example # Replace this with your project name
-      schema: default # Replace this with schema name, e.g. dbt_bilbo
+      schema: default # Replace this with schema name, for example, dbt_bilbo
       endpoint: http://service.cn-shanghai.maxcompute.aliyun.com/api # Replace this with your maxcompute endpoint
       auth_type: chain
 ```

website/docs/docs/core/connect-data-platform/oracle-setup.md

@@ -453,7 +453,7 @@ Oracle's Autonomous Database Serverless (ADB-S) users can run dbt-py models usin
 
 ### Features
 - User Defined Python function is run in an ADB-S spawned Python 3.12.1 runtime
-- Access to external Python packages available in the Python runtime. For e.g. `numpy`, `pandas`, `scikit_learn` etc
+- Access to external Python packages available in the Python runtime. For example, `numpy`, `pandas`, `scikit_learn` etc
 - Integration with Conda 24.x to create environments with custom Python packages
 - Access to Database session in the Python function
 - DataFrame read API to read `TABLES`, `VIEWS`, and ad-hoc `SELECT` queries as DataFrames

website/docs/docs/core/connect-data-platform/postgres-setup.md

@@ -99,7 +99,7 @@ If `dbt-postgres` encounters an operational error or timeout when opening a new
 `psycopg2-binary` is installed by default when installing `dbt-postgres`.
 Installing `psycopg2-binary` uses a pre-built version of `psycopg2` which may not be optimized for your particular machine.
 This is ideal for development and testing workflows where performance is less of a concern and speed and ease of install is more important.
-However, production environments will benefit from a version of `psycopg2` which is built from source for your particular operating system and architecture. In this scenario, speed and ease of install is less important as the on-going usage is the focus.
+However, production environments will benefit from a version of `psycopg2` which is built from source for your particular operating system, and architecture. In this scenario, speed and ease of install is less important as the on-going usage is the focus.
 
 
 To use `psycopg2`:

website/docs/docs/core/connect-data-platform/spark-setup.md

@@ -53,7 +53,7 @@ $ python -m pip install "dbt-spark[session]"
 dbt-spark can connect to Spark clusters by four different methods:
 
 - [`odbc`](#odbc) is the preferred method when connecting to Databricks. It supports connecting to a SQL Endpoint or an all-purpose interactive cluster.
-- [`thrift`](#thrift) connects directly to the lead node of a cluster, either locally hosted / on premise or in the cloud (e.g. Amazon EMR).
+- [`thrift`](#thrift) connects directly to the lead node of a cluster, either locally hosted / on premise or in the cloud (for example, Amazon EMR).
 - [`http`](#http) is a more generic method for connecting to a managed service that provides an HTTP endpoint. Currently, this includes connections to a Databricks interactive cluster.
 
 
@@ -98,7 +98,7 @@ your_profile_name:
 
 ### Thrift
 
-Use the `thrift` connection method if you are connecting to a Thrift server sitting in front of a Spark cluster, e.g. a cluster running locally or on Amazon EMR.
+Use the `thrift` connection method if you are connecting to a Thrift server sitting in front of a Spark cluster, for example, a cluster running locally or on Amazon EMR.
 
 <File name='~/.dbt/profiles.yml'>
 
@@ -115,8 +115,8 @@ your_profile_name:
       # optional
       port: [port]              # default 10001
       user: [user]
-      auth: [e.g. KERBEROS]
-      kerberos_service_name: [e.g. hive]
+      auth: [for example, KERBEROS]
+      kerberos_service_name: [for example, hive]
       use_ssl: [true|false]   # value of hive.server2.use.SSL, default false
       server_side_parameters:
         "spark.driver.memory": "4g" 
@@ -126,7 +126,7 @@ your_profile_name:
 
 ### HTTP
 
-Use the `http` method if your Spark provider supports generic connections over HTTP (e.g. Databricks interactive cluster).
+Use the `http` method if your Spark provider supports generic connections over HTTP (for example, Databricks interactive cluster).
 
 <File name='~/.dbt/profiles.yml'>