Merge branch 'current' into feature/clarify-tagging-inheritance-example

website/docs/reference/node-selection/state-comparison-caveats.md

@@ -60,8 +60,8 @@ State comparison works by identifying discrepancies between two manifests. Thos
 1. Changes made to a project in development
 2. Env-aware logic that causes different behavior based on the `target`, env vars, etc.
 
-dbt will do its best to capture *only* changes that are the result of modifications made in development. In projects with intricate env-aware logic, dbt will err on the side of running too many models (i.e. false positives). Over the next several versions of dbt, We're working on:
-- iterative improvements to dbt's built-in dectective abilities
+dbt will do its best to capture *only* changes that are the result of modifications made in development. In projects with intricate env-aware logic, dbt will err on the side of running too many models (i.e. false positives). Over the next several versions of dbt, we're working on:
+- iterative improvements to dbt's built-in detective abilities
 - better options for more complex projects, in the form of more-specific subselectors (see [this issue](https:/dbt-labs/dbt-core/issues/2704))
 
 <Changelog>

website/docs/reference/resource-configs/strategy.md

@@ -136,7 +136,7 @@ Behind the scenes, snapshot strategies are implemented as macros, named `snapsho
 
 It's possible to implement your own snapshot strategy by adding a macro with the same naming pattern to your project. For example, you might choose to create a strategy which records hard deletes, named `timestamp_with_deletes`.
 
-1. Create a macro named `snapshot_timestamp_with_deletes_strategy`. Use the existing code a guide and adjust as needed.
+1. Create a macro named `snapshot_timestamp_with_deletes_strategy`. Use the existing code as a guide and adjust as needed.
 2. Use this strategy via the `strategy` configuration:
 
 <File name='snapshots/<filename>.sql'>