Change per copilot review

Signed-off-by: popcorny <[email protected]>

Author: popcornylu

docs/features/breaking-change-analysis.md

@@ -13,7 +13,7 @@ It's generally assumed that any modification to a model’s SQL will affect all
 
 
 ## Usage
-Use the [impact radius](./impact-radius.md#usage) to analyze changed and see the impacted downstream.
+Use the [impact radius](./impact-radius.md#usage) view to analyze changed and see the impacted downstream.
 
 ## Categories of change
 ### Non-breaking change

docs/features/impact-radius.md

@@ -56,7 +56,7 @@ Two core features power the impact radius analysis:
 **[Breaking Change Analysis](./breaking-change-analysis.md)** classifies modified models into three categories:
 
 - **Breaking changes**: All downstream nodes are impacted
-- **Non-breaking changes**: No downstream nodes are not impacted
+- **Non-breaking changes**: No downstream nodes are impacted
 - **Partial breaking changes**: Only downstream columns that depend on modified columns are impacted.
 
 **[Column-level lineage](./column-level-lineage.md)** analyzes your model's SQL to identify column-level dependencies:

mkdocs.yml

@@ -56,7 +56,7 @@ nav:
           - features/state-file.md
           - features/preset-checks.md
           - features/node-selection.md
-          - features/impact-radius.md          
+          - features/impact-radius.md
           - features/breaking-change-analysis.md
           - features/column-level-lineage.md
           - reference/configuration.md