Style changes to dbt-versions directory (#8082)

Author: matthewshaver

website/docs/docs/dbt-versions/2022-release-notes.md

@@ -175,7 +175,7 @@ The audit log includes details such as who performed the action, what the action
 
 ### Credentials no longer accidentally wiped when editing an environment
 
-We resolved a bug where when updating unencrypted fields (e.g. threads, schema name) in an environment setting would cause secret fields (e.g. password, keypair, credential details) to be deleted from that environment. Now users can freely update environment settings without fear of unintentionally wiping credentials.
+We resolved a bug where when updating unencrypted fields (for example, threads, schema name) in an environment setting would cause secret fields (for example, password, keypair, credential details) to be deleted from that environment. Now users can freely update environment settings without fear of unintentionally wiping credentials.
 
 ### Email verification
 

website/docs/docs/dbt-versions/cloud-release-tracks.md

@@ -75,7 +75,7 @@ dbt Labs has extended the critical support period of <Constant name="core" /> v1
 
 If you're running dbt version v1.6 or older, please know that your version of dbt Core has reached [end-of-life (EOL)](/docs/dbt-versions/core#eol-version-support) and is no longer supported. We strongly recommend that you update to a newer version as soon as reasonably possible.
 
-dbt Labs has extended the "Critical Support" period of dbt Core v1.7 for dbt Enterprise-tier customers while we work through the migration with those customers to Release Tracks. In the meantime, this means that v1.7 will continue to be accessible in dbt for Enteprise customers, jobs and environments on v1.7 for those customers will not be automatically migrated to "Latest," and dbt Labs will continue to fix critical bugs and security issues.
+dbt Labs has extended the "Critical Support" period of dbt Core v1.7 for dbt Enterprise-tier customers while we work through the migration with those customers to Release Tracks. In the meantime, this means that v1.7 will continue to be accessible in dbt for Enterprise customers, jobs and environments on v1.7 for those customers will not be automatically migrated to "Latest," and dbt Labs will continue to fix critical bugs and security issues.
 
 Starting in October 2024, dbt accounts on the Developer and Starter (formerly Teams) plans have been migrated to release tracks from older dbt Core versions. If your account was migrated to the "Latest" release track and you notice new failures in scheduled jobs, please [contact dbt support](/docs/dbt-support#dbt-cloud-support) to report the problem or request an extension.
 

website/docs/docs/dbt-versions/compatible-track-changelog.md

@@ -64,8 +64,8 @@ Release date: August 12, 2025
 ### Notable dbt Core OSS changes
 
 This compatible upgrade brings in a minor update to `dbt-core`, from `dbt-core==1.9.8` to `dbt-core==1.10.8`. Some noteworthy changes from this minor version include:
-* Introduction of several new [deprecations](/reference/deprecations) that warn about project incompatibilities between dbt Core and Fusion engines.
-* Support for defining `meta` and `tags` within `config` of columns and exposures, as well as defining `freshness` within `config` of sources. These changes lead to manifest.json minor schema evolutions which may cause an intermittent increase in false positives during `state:modified` comparisons.
+- Introduction of several new [deprecations](/reference/deprecations) that warn about project incompatibilities between dbt Core and Fusion engines.
+- Support for defining `meta` and `tags` within `config` of columns and exposures, as well as defining `freshness` within `config` of sources. These changes lead to manifest.json minor schema evolutions which may cause an intermittent increase in false positives during `state:modified` comparisons.
 
 ### dbt cloud-based platform 
 

website/docs/docs/dbt-versions/core-upgrade/04-upgrading-to-v1.11.md

@@ -55,6 +55,6 @@ These warnings help you proactively identify and update deprecated configuration
 ## Quick hits
 
 You will find these quick hits in dbt Core v1.11:
-* The `dbt ls` command can now write out nested keys. This makes it easier to debug and troubleshoot your project. Example: `dbt ls --output json --output-keys config.materialized`
-* Manifest metadata now includes `run_started_at`, providing better tracking of when dbt runs were initiated.
+- The `dbt ls` command can now write out nested keys. This makes it easier to debug and troubleshoot your project. Example: `dbt ls --output json --output-keys config.materialized`
+- Manifest metadata now includes `run_started_at`, providing better tracking of when dbt runs were initiated.
 

website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.7.md

@@ -40,7 +40,7 @@ To retain the behavior prior to v1.7, there are two main options:
 ### MetricFlow enhancements
 
 - Automatically create metrics on measures with [`create_metric: true`](/docs/build/semantic-models).
-- Optional [`label`](/docs/build/semantic-models) in semantic_models, measures, dimensions and entities.
+- Optional [`label`](/docs/build/semantic-models) in semantic_models, measures, dimensions, and entities.
 - New configurations for semantic models - [enable/disable](/reference/resource-configs/enabled), [group](/reference/resource-configs/group), and [meta](/reference/resource-configs/meta).
 - Support `fill_nulls_with` and `join_to_timespine` for metric nodes.
 - `saved_queries` extends governance beyond the semantic objects to their consumption.

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/12-upgrading-to-v1.4.md

@@ -21,7 +21,7 @@ dbt Labs is committed to providing backward compatibility for all versions 1.x.
 
 ### For consumers of dbt artifacts (metadata)
 
-The manifest schema version has updated to `v8`. These changes are relevant for people who parse or analyze the contents of the `manifest.json` file, or who have custom code accessing the [`model`](/reference/dbt-jinja-functions/model) or [`graph`](/reference/dbt-jinja-functions/graph) variables, e.g. `{{ model.root_path }}`.
+The manifest schema version has updated to `v8`. These changes are relevant for people who parse or analyze the contents of the `manifest.json` file, or who have custom code accessing the [`model`](/reference/dbt-jinja-functions/model) or [`graph`](/reference/dbt-jinja-functions/graph) variables, for example, `{{ model.root_path }}`.
 
 Relevant changes:
 - The `root_path` attribute has been removed for non-seed nodes to reduce duplicative information.

website/docs/docs/dbt-versions/release-notes.md

@@ -169,7 +169,7 @@ The following features are new or enhanced as part of our [dbt Developer day](ht
 
 ## February 2025
 
-- **Enhancement**: The [Python SDK](/docs/dbt-cloud-apis/sl-python) added a new timeout parameter to Semantic Layer client and to underlying GraphQL clients to specify timeouts. Set a timeout number or use the `total_timeout` parameter in the global `TimeoutOptions` to control connect, execute and close timeouts granularly. `ExponentialBackoff.timeout_ms` is now deprecated.
+- **Enhancement**: The [Python SDK](/docs/dbt-cloud-apis/sl-python) added a new timeout parameter to Semantic Layer client and to underlying GraphQL clients to specify timeouts. Set a timeout number or use the `total_timeout` parameter in the global `TimeoutOptions` to control connect, execute, and close timeouts granularly. `ExponentialBackoff.timeout_ms` is now deprecated.
 - **New**: The [Azure DevOps](/docs/cloud/git/connect-azure-devops) integration for <Constant name="git" /> now supports [Entra service principal apps](/docs/cloud/git/setup-service-principal) on <Constant name="cloud" /> Enterprise accounts. Microsoft is enforcing MFA across user accounts, including service users, which will impact existing app integrations. This is a phased rollout, and dbt Labs recommends [migrating to a service principal](/docs/cloud/git/setup-service-principal#migrate-to-service-principal) on existing integrations once the option becomes available in your account.
 - **New**: Added the `dbt invocation` command to the [dbt CLI](/docs/cloud/cloud-cli-installation). This command allows you to view and manage active invocations, which are long-running sessions in the dbt CLI. For more information, see [dbt invocation](/reference/commands/invocation).
 - **New**: Users can now switch themes directly from the user menu, available [in Preview](/docs/dbt-versions/product-lifecycles#dbt-cloud). We have added support for **Light mode** (default), **Dark mode**, and automatic theme switching based on system preferences. The selected theme is stored in the user profile and will follow users across all devices.

website/docs/docs/dbt-versions/release-notes/99-dbt-cloud-changelog-2019-2020.md

@@ -57,7 +57,7 @@ This release adds a few new pieces of connective tissue, notably OAuth for BigQu
 
 - Update IP allowlist
 - User can OAuth for BigQuery in profile credentials
-- Adding SparkAdapter backend models, mappers and services
+- Adding SparkAdapter backend models, mappers, and services
 - Added BigQuery OAuth integration
 - Adding db index for owner_thread_id
 
@@ -339,7 +339,7 @@ This release includes dbt 0.17.0 and a number of IDE quality of life improvement
 
 - Added dbt 0.17.0
 - Added the ability to create a new folder in the IDE
-- Added gitignore status to file system and display dbt artifacts, including directories dbt_modules, logs and target
+- Added gitignore status to file system and display dbt artifacts, including directories dbt_modules, logs, and target
 - (Cloud only) Added rollbar and update some various error handling clean up
 - (On-premises only) Admin site: allow Repository's Pull Request Template field to be blank
 - (On-premises only) Added AWS KMS support