Fix various typos

website/docs/docs/build/packages.md

@@ -161,7 +161,7 @@ Where `name: 'dbt_utils'` specifies the subfolder of `dbt_packages` that's creat
 
 ### Native private packages <Lifecycle status='beta'/> 
 
-dbt Cloud supports private packages from [supported](#prerequisites) Git repos leveraging an exisiting [configuration](/docs/cloud/git/git-configuration-in-dbt-cloud) in your environment. Previously, you had to configure a [token](#git-token-method) to retrieve packages from your private repos.  
+dbt Cloud supports private packages from [supported](#prerequisites) Git repos leveraging an existing [configuration](/docs/cloud/git/git-configuration-in-dbt-cloud) in your environment. Previously, you had to configure a [token](#git-token-method) to retrieve packages from your private repos.
 
 #### Prerequisites
 

website/docs/docs/cloud-integrations/about-snowflake-native-app.md

@@ -46,7 +46,7 @@ App users are able to access all information that's available to the API service
 ## Procurement
 The dbt Snowflake Native App is available on the [Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZTYZSRT2R3). Purchasing it includes access to the Native App and a dbt Cloud account that's on the Enterprise plan. Existing dbt Cloud Enterprise customers can also access it. If interested, contact your Enterprise account manager.
 
-If you're interested, please [contact us](matilto:sales_snowflake_marketplace@dbtlabs.com) for more information. 
+If you're interested, please [contact us](mailto:sales_snowflake_marketplace@dbtlabs.com) for more information.
 
 ## Support
 If you have any questions about the dbt Snowflake Native App, you may [contact our Support team](mailto:dbt-snowflake-marketplace@dbtlabs.com) for help. Please provide information about your installation of the Native App, including your dbt Cloud account ID and Snowflake account identifier. 

website/docs/docs/cloud/git/setup-azure.md

@@ -155,7 +155,7 @@ The service user's permissions will also power which repositories a team can sel
 
 While it's common to enforce multi-factor authentication (MFA) for normal user accounts, service user authentication must not need an extra factor. If you enable a second factor for the service user, this can interrupt production runs and cause a failure to clone the repository. In order for the OAuth access token to work, the best practice is to remove any more burden of proof of identity for service users.
 
-As a result, MFA must be explicity disabled in the Office 365 or Microsoft Entra ID administration panel for the service user.  Just having it "un-connected" will not be sufficient, as dbt Cloud will be prompted to set up MFA instead of allowing the credentials to be used as intended.
+As a result, MFA must be explicitly disabled in the Office 365 or Microsoft Entra ID administration panel for the service user.  Just having it "un-connected" will not be sufficient, as dbt Cloud will be prompted to set up MFA instead of allowing the credentials to be used as intended.
 
 
 **To disable MFA for a single user using the Office 365 Administration console:**

website/docs/docs/cloud/manage-access/external-oauth.md

@@ -144,7 +144,7 @@ Adjust the other settings as needed to meet your organization's configurations i
 1. Navigate back to the dbt Cloud **Account settings** —> **Integrations** page you were on at the beginning. It’s time to start filling out all of the fields.
    1. `Integration name`: Give the integration a descriptive name that includes identifying information about the Okta environment so future users won’t have to guess where it belongs.
    2. `Client ID` and `Client secrets`: Retrieve these from the Okta application page.
-   <Lightbox src="/img/docs/dbt-cloud/gather-clientid-secret.png" width="60%" title="TThe client ID and secret highlighted in the Okta app" />
+   <Lightbox src="/img/docs/dbt-cloud/gather-clientid-secret.png" width="60%" title="The client ID and secret highlighted in the Okta app" />
    3. Authorize URL and Token URL: Found in the metadata URI.
    <Lightbox src="/img/docs/dbt-cloud/gather-authorization-token-endpoints.png" width="60%" title="The authorize and token URLs highlighted in the metadata URI" />
 

website/docs/docs/cloud/manage-access/invite-users.md

@@ -66,7 +66,7 @@ Once the user completes this process, their email and user information will popu
 
 * Is there a limit to the number of users I can invite? _Your ability to invite users is limited to the number of licenses you have available._
 * Why are users are clicking the invitation link and getting an `Invalid Invitation Code` error? _We have seen scenarios where embedded secure link technology (such as enterprise Outlooks [Safe Link](https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/safe-links-about?view=o365-worldwide) feature) can result in errors when clicking on the email link. Be sure to include the `getdbt.com` URL in the allowlists for these services._
-* Can I have a mixure of users with SSO and username/password authentication? _Once SSO is enabled, you will no longer be able to add local users. If you have contractors or similar contingent workers, we recommend you add them to your SSO service._
+* Can I have a mixture of users with SSO and username/password authentication? _Once SSO is enabled, you will no longer be able to add local users. If you have contractors or similar contingent workers, we recommend you add them to your SSO service._
 * What happens if I need to resend the invitation? _From the Users page, click on the invite record, and you will be presented with the option to resend the invitation._
 * What can I do if I entered an email address incorrectly? _From the Users page, click on the invite record, and you will be presented with the option to revoke it. Once revoked, generate a new invitation to the correct email address._
 

website/docs/docs/cloud/manage-access/mfa.md

@@ -58,7 +58,7 @@ Choose the next steps based on your preferred enrollment selection:
 
 2. Follow the instructions in the modal window and click **Use security key**.
 
-<Lightbox src="/img/docs/dbt-cloud/create-security-key.png" title="Example of the Seciruty Key activation window." />
+<Lightbox src="/img/docs/dbt-cloud/create-security-key.png" title="Example of the Security Key activation window." />
 
 3. Scan the QR code or insert and touch activate your USB key to begin the process. Follow the on-screen prompts.
 

website/docs/docs/collaborate/data-tile.md

@@ -63,7 +63,7 @@ Follow these steps to set up your data health tile:
 6. Navigate back to dbt Explorer and select an exposure.
 7. Below the **Data health** section, expand on the toggle for instructions on how to embed the exposure tile (if you're an account admin with develop permissions). 
 8. In the expanded toggle, you'll see a text field where you can paste your **Metadata Only token**.
-<Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-example.jpg" width="85%" title="Expand the toggle to embded data health tile into your dashboard." />
+<Lightbox src="/img/docs/collaborate/dbt-explorer/data-tile-example.jpg" width="85%" title="Expand the toggle to embed data health tile into your dashboard." />
 
 9. Once you’ve pasted your token, you can select either **URL** or **iFrame** depending on which you need to add to your dashboard.
 

website/docs/docs/collaborate/explore-multiple-projects.md

@@ -27,7 +27,7 @@ When viewing a downstream (child) project that imports and refs public models fr
 - Clicking on a model opens a side panel containing general information about the model, such as the specific dbt Cloud project that produces that model, description, package, and more.
 - Double-clicking on a model from another project opens the resource-level lineage graph of the parent project, if you have the permissions to do so.
 
-<Lightbox src="/img/docs/collaborate/dbt-explorer/cross-project-child.png" width="100%" height="100" title="View a downstream (child) project that importants and refs public models from the upstream (parent) project."/>
+<Lightbox src="/img/docs/collaborate/dbt-explorer/cross-project-child.png" width="100%" height="100" title="View a downstream (child) project that imports and refs public models from the upstream (parent) project."/>
 
 ## Explore the project-level lineage graph
 

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

@@ -55,7 +55,7 @@ Microsoft made several changes related to connection encryption. Read more about
 ### Authentication methods
 
 This adapter is based on the adapter for Microsoft SQL Server.
-Therefor, the same authentication methods are supported.
+Therefore, the same authentication methods are supported.
 
 The configuration is the same except for 1 major difference:
 instead of specifying `type: sqlserver`, you specify `type: synapse`.

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

@@ -65,7 +65,7 @@ your_profile_name:
 | type            | The specific adapter to use                                                         | Required                                                           | `ibmdb2`                                       |
 | schema          | Specify the schema (database) to build models into                                  | Required                                                           | `analytics`                                    |
 | database        | Specify the database you want to connect to                                         | Required                                                           | `testdb`                                         |
-| host            | Hostname or IP-adress                                                               | Required                                                           | `localhost`                                    |
+| host            | Hostname or IP-address                                                              | Required                                                           | `localhost`                                    |
 | port            | The port to use                                                                     | Optional                                                           | `50000`                                        |
 | protocol        | Protocol to use                                                                     | Optional                                                           | `TCPIP`                                        |
 | username        | The username to use to connect to the server                                        | Required                                                           | `my-username`                                  |

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

@@ -83,7 +83,7 @@ _Parameters:_
 
 | Syntax    | Description                                                                                                                                                                                                                                 |
 | --------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `MODEL_TYPE`    | Type of the model your want to train. There are two options: <br/> - `classifier`: A model to predict classes/labels or categories such as spam detection<br/>- `regressor`: A model to predict continious outcomes such as CLV prediction. |
+| `MODEL_TYPE`    | Type of the model your want to train. There are two options: <br/> - `classifier`: A model to predict classes/labels or categories such as spam detection<br/>- `regressor`: A model to predict continuous outcomes such as CLV prediction. |
 | `FEATURES`    | Input column names as a list to train your AutoML model.                                                                                                                                                                                    |
 | `TARGET`    | Target column that you want to predict.                                                                                                                                                                                                     |
 

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

@@ -68,7 +68,7 @@ The `role` config controls the Postgres role that dbt assumes when opening new c
 
 #### sslmode
 
-The `sslmode` config controls how dbt connectes to Postgres databases using SSL. See [the Postgres docs](https://www.postgresql.org/docs/9.1/libpq-ssl.html) on `sslmode` for usage information. When unset, dbt will connect to databases using the Postgres default, `prefer`, as the `sslmode`.
+The `sslmode` config controls how dbt connects to Postgres databases using SSL. See [the Postgres docs](https://www.postgresql.org/docs/9.1/libpq-ssl.html) on `sslmode` for usage information. When unset, dbt will connect to databases using the Postgres default, `prefer`, as the `sslmode`.
 
 
 #### sslcert
@@ -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 archtecture. 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.
 
 <VersionBlock firstVersion="1.8">
 

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

@@ -25,7 +25,7 @@ import SetUpPages from '/snippets/_setup-pages-intro.md';
 <SetUpPages meta={frontMatter.meta} />
 
 
-If connecting to Databricks via ODBC driver, it requires `pyodbc`. Depending on your system, you can install it seperately or via pip. See the [`pyodbc` wiki](https://github.com/mkleehammer/pyodbc/wiki/Install) for OS-specific installation details.
+If connecting to Databricks via ODBC driver, it requires `pyodbc`. Depending on your system, you can install it separately or via pip. See the [`pyodbc` wiki](https://github.com/mkleehammer/pyodbc/wiki/Install) for OS-specific installation details.
 
 If connecting to a Spark cluster via the generic thrift or http methods, it requires `PyHive`.
 

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

@@ -10,7 +10,7 @@ meta:
   min_core_version: 'v1.5.0'
   cloud_support: Not Supported
   min_supported_version: 'n/a'
-  slack_channel_name: 'Upsolver Comunity'
+  slack_channel_name: 'Upsolver Community'
   slack_channel_link: 'https://join.slack.com/t/upsolvercommunity/shared_invite/zt-1zo1dbyys-hj28WfaZvMh4Z4Id3OkkhA'
   platform_name: 'Upsolver'
   config_page: '/reference/resource-configs/upsolver-configs'

website/docs/docs/dbt-cloud-apis/authentication.md

@@ -31,7 +31,7 @@ pagination_prev: null
 
 You should use service tokens broadly for any production workflow where you need a service account. You should use PATs only for developmental workflows _or_ dbt Cloud client workflows that require user context. The following examples show you when to use a personal access token (PAT) or a service token: 
 
-* **Connecting a partner integration to dbt Cloud** — Some examples include the [dbt Semantic Layer Google Sheets integration](/docs/cloud-integrations/avail-sl-integrations), Hightouch, Datafold, a custom app you’ve created, etc. These types of integrations should use a service token instead of a PAT because service tokens give you visibility, and you can scope them to only what the integration needs and ensure the least privilege. We highly recommend switching to a service token if you’re using a personal acess token for these integrations today. 
+* **Connecting a partner integration to dbt Cloud** — Some examples include the [dbt Semantic Layer Google Sheets integration](/docs/cloud-integrations/avail-sl-integrations), Hightouch, Datafold, a custom app you’ve created, etc. These types of integrations should use a service token instead of a PAT because service tokens give you visibility, and you can scope them to only what the integration needs and ensure the least privilege. We highly recommend switching to a service token if you’re using a personal access token for these integrations today.
 * **Production Terraform** — Use a service token since this is a production workflow and is acting as a service account and not a user account. 
 * **Cloud CLI** — Use a PAT since the dbt Cloud CLI works within the context of a user (the user is making the requests and has to operate within the context of their user account).
 * **Testing a custom script and staging Terraform or Postman** — We recommend using a PAT as this is a developmental workflow and is scoped to the user making the changes. When you push this script or Terraform into production, use a service token instead.

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

@@ -51,7 +51,7 @@ packages:
 </File>
 
 
-## Novemver 2022
+## November 2022
 
 ### The dbt Cloud + Databricks experience is getting even better
 
@@ -241,4 +241,4 @@ We started the new year with a gift! Multi-tenant Team and Enterprise accounts c
 
 #### Performance improvements and enhancements
 
-* We added client-side naming validation for file or folder creation.
+* We added client-side naming validation for file or folder creation.

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

@@ -35,7 +35,7 @@ Archived release notes for dbt Cloud from 2023
 
     To learn more, refer to [Extended attributes](/docs/dbt-cloud-environments#extended-attributes).
 
-    The **Extended Atrributes** text box is available from your environment's settings page: 
+    The **Extended Attributes** text box is available from your environment's settings page: 
 
     <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/extended-attributes.jpg" width="85%" title="Example of the Extended Attributes text box" />
 
@@ -183,7 +183,7 @@ Archived release notes for dbt Cloud from 2023
 
     Previously in dbt Cloud, you could only rerun an errored job from start but now you can also rerun it from its point of failure. 
 
-    You can view which job failed to complete successully, which command failed in the run step, and choose how to rerun it. To learn more, refer to [Retry jobs](/docs/deploy/retry-jobs).
+    You can view which job failed to complete successfully, which command failed in the run step, and choose how to rerun it. To learn more, refer to [Retry jobs](/docs/deploy/retry-jobs).
 
     <Lightbox src="/img/docs/deploy/native-retry.gif" width="70%" title="Example of the Rerun options in dbt Cloud"/>
 
@@ -812,7 +812,7 @@ Archived release notes for dbt Cloud from 2023
 
   </Expandable>
 
-- <Expandable alt_header='Scheduler optmization'>
+- <Expandable alt_header='Scheduler optimization'>
 
     The dbt Cloud Scheduler now prevents queue clog by canceling unnecessary runs of over-scheduled jobs.