adding in grammatical or rephrasing changes to sections 3-8

Author: doriwilson

docs/3-visualized-change/column-level-lineage.md

@@ -4,7 +4,7 @@ title: Column-Level Lineage
 
 Column-Level Lineage provides visibility into the upstream and downstream relationships of a column.
 
-Common use-cases for column-level lineage are
+Common use-cases for column-level lineage are:
 
 1. **Source Exploration**: During development, column-level lineage helps you understand how a column is derived.
 2. **Impact Analysis**: When modifying the logic of a column, column-level lineage enables you to assess the potential impact across the entire DAG.
@@ -33,7 +33,7 @@ The transformation type is also displayed for each column, which will help you u
 | Pass-through  |The column is directly selected from the upstream table. |
 | Renamed | The column is selected from the upstream table but with a different name. |
 | Derived | The column is created through transformations applied to upstream columns, such as calculations, conditions, functions, or aggregations. |
-| Source | The column is not derived from any upstream data. It may originate from a seed/source node, literal value, or data generation function. |
-| Unknown | We have no information about the transformation type. This could be due to a parse error, or other unknown reason. |
+| Source | The column is not derived from any upstream data. It may originate from a seed/source node, literal value or data generation function. |
+| Unknown | We have no information about the transformation type. This could be due to a parse error or other unknown reason. |
 
 

docs/3-visualized-change/multi-models.md

@@ -20,9 +20,9 @@ To select multiple models individually, click the checkbox on the models you wis
 
 To select a node and all of its parents or children:
 
-1. Click the checkbox on the node.
-2. Right-click the node.
-3. Click to select either parent or child models.
+1. Click the checkbox on the node
+2. Right-click the node
+3. Click to select either parent or child models
 
 <figure markdown>
   ![Select a node and its parents or children](../assets/images/3-visualized-change/select-node-children.gif){: .shadow}
@@ -88,7 +88,7 @@ Since Recce uses dbt's built-in node selector, it supports most of the selecting
 
 ### Use `state` method
 
-In dbt, you need to specify the `--state` option in the CLI. In Recce, we use the base environment as the state, allowing you to use the selector on the fly.
+In dbt, you need to specify the `--state` option in the CLI. In Recce we use the base environment as the state, allowing you to use the selector on the fly.
 
 
 ### Removed models
@@ -97,7 +97,7 @@ Another difference is that in dbt, you cannot select removed models. However, in
 
 ## Supported Diff
 
-In addition to lineage diff, other types of diff also support node selection. You can find these features in the **...** button in the top right corner. Currently supported diffs include:
+In addition to lineage diff, other types of diff also support node selection. You can find these features in the **...** button in the top right corner. Currently supported node-based diffs include:
 
 - Lineage diff
 - Row count diff

docs/4-downstream-impacts/impact-radius.md

@@ -134,8 +134,8 @@ Two core features power the impact radius analysis:
 With the insights from the two features above, Recce determines the impact radius:
 
 1. If a model has a **breaking change**, include all downstream models in the impact radius.
-1. If a model has a **non-breaking change**, include only the downstream columns and models of newly added columns.
-1. If a model has a **partial breaking change**, include the downstream columns and models of added, removed, or modified columns.
+2. If a model has a **non-breaking change**, include only the downstream columns and models of newly added columns.
+3. If a model has a **partial breaking change**, include the downstream columns and models of added, removed, or modified columns.
 
 
 

docs/5-data-diffing/query.md

@@ -53,11 +53,11 @@ In the current version, Recce provides two ways to compare the query result betw
 
 **Query diff occurs in the client side:**
 
-Without providing primary key(s) upfront, AdHoc query compare in the client side. That is, Recce fetches the first 2,000 rows and compare in the client side. The advantage is it has more flexibility to query sql for no PK, especially when column structures differ or no clear primary key exists.
+Without primary keys provided upfront, adhoc queries will compare results on the client side. That is, Recce fetches the first 2,000 rows and compare in the client side. The advantage is it has more flexibility to query sql for no PK, especially when column structures differ or no clear primary key exists.
 However, the limitation is that we cannot find the mismatched rows in a big query result.
 
 **Query diff occurs in the warehouse:**
 
-With primary key(s) given, it can perform a query diff in the warehouse. It only displays changed, added, or removed rows. Therefore, if only one record is different among a million, that specific record will be visible. Hence, it also reduces the amount of data transferred.
+When primary keys are given, it can perform a query diff in the warehouse. It will only display changed, added, or removed rows. Meaning, if only one record is different among a million, that specific record will be visible. Thus reducing the amount of data transferred.
 
 Another similar feature is [Value Diff](lineage.md#value-diff). Value diff is based on a chosen model, so you don’t need to write SQL to operate it, though it naturally offers less flexibility. Additionally, value diff can show a summary or actual diff records, whereas query diff only shows the actual diff records.

docs/5-data-diffing/value-diff.md

@@ -5,7 +5,7 @@ title: Value Diff
 
 Value Diff shows the matched count and percentage for each column in the table. It uses the primary key(s) to uniquely identify the records between the model in both environments.
 
-The primary key is automatically inferred by the first column with the [unique](https://docs.getdbt.com/reference/resource-properties/data-tests#unique) test. If no primary key is detected at least one column is required to be specified as the primary key.
+The primary key (PK) is automatically inferred by the first column with the [unique](https://docs.getdbt.com/reference/resource-properties/data-tests#unique) test. If no primary key is detected at least one column is required to be specified as the primary key.
 
 <figure markdown>
   ![Recce Value Diff](../assets/images/5-data-diffing/value-diff.png)

docs/6-collaboration/checklist.md

@@ -34,9 +34,9 @@ An example performing a Top-K diff and adding the results to the Checklist:
 
 The Recce Checklist provides a way to record the results of a data check during change exploration. The purpose of adding Checks to the Checklist is to enable you to:
 
-- Save Checks with notes of your interpretation of the data.
-- Re-run checks following further data modeling changes.
-- Share Checks as part of PR or stakeholder review.
+- Save Checks with notes of your interpretation of the data
+- Re-run checks following further data modeling changes
+- Share Checks as part of PR or stakeholder review
 
 ## Preset Check
 

docs/7-cicd/best-practices-prep-env.md

@@ -6,12 +6,12 @@ Recce is designed to compare two environments in your data project. To use it ef
 
 However, there are many challenges in preparing environments.
 
-1. Your **source data** might be continuously updating.
-2. Your transformations might be **time-consuming**.
-3. The base branch may have **other PRs merged** at any time.
-4. The generated environment will leave data in the warehouse, which also needs to be properly managed.
+1. Your **source data** might be continuously updating
+2. Your transformations might be **time-consuming**
+3. The base branch may have **other PRs merged** at any time
+4. The generated environment will leave data in the warehouse, which also needs to be properly managed
 
-This article will not focus on how to use Recce but rather on how to effectively prepare environments for Recce use.
+This article will not focus on how to use Recce, but rather on how to effectively prepare environments for Recce use.
 
 
 ## Best Practices
@@ -88,9 +88,9 @@ Using the production environment as the base environment is a straightforward ch
 
 This staging environment can have the following characteristics:
 
-1. Ensure that the transformed results reflect the **latest commit** of the base branch.
-2. Use the **same source data** as the PR environment.
-3. Use the **same transformation logic** as the PR environment.
+1. Ensure that the transformed results reflect the **latest commit** of the base branch
+2. Use the **same source data** as the PR environment
+3. Use the **same transformation logic** as the PR environment
 
 The basic principle is that the staging environment's configuration should be **as close as possible to the PR environments**, except for using a different git commit.
 
@@ -168,9 +168,9 @@ Recce relies on the base and current environment artifacts to find the correspon
 
 Here are a few methods you can choose:
 
-1. In CI, upload the generated artifact to the cloud storage (e.g., AWS S3).
-2. For dbt Cloud users, you can [download artifacts](https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Retrieve%20Run%20Artifact) for the latest run of a given job.
-3. For GitHub Actions users, you can use the GitHub CLI (gh) to [download artifacts](https://cli.github.com/manual/gh_run_download) for the latest run of a given workflow.
+1. In CI, upload the generated artifact to the cloud storage (e.g., AWS S3)
+2. For dbt Cloud users, you can [download artifacts](https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Retrieve%20Run%20Artifact) for the latest run of a given job
+3. For GitHub Actions users, you can use the GitHub CLI (gh) to [download artifacts](https://cli.github.com/manual/gh_run_download) for the latest run of a given workflow
 
 If the methods mentioned above are too complex, a stateless approach is to directly check out the base branch and run **`dbt docs generate`** to generate the artifacts.
 
@@ -205,8 +205,8 @@ dbt run-operation clear_schema --args "{'schema_name': 'pr_123'}"
 | PR           | `pr_<number>` | On Push            | # of opened PR      | 1 month, excluding this week     |
 
 
-- Automate environment generation using GitHub Actions.
-- PR Environment will only be generated automatically when the PR is up-to-date.
-- Artifacts will be stored under the workflow’s artifacts.
-- PR environments are removed on PR closed.
-- Use staging environment as the base environment for Recce.
+- Automate environment generation using GitHub Actions
+- PR Environment will only be generated automatically when the PR is up-to-date
+- Artifacts will be stored under the workflow’s artifacts
+- PR environments are removed on PR closed
+- Use staging environment as the base environment for Recce

docs/7-cicd/index.md

@@ -4,7 +4,7 @@ icon: material/hand-wave-outline
 ---
 
 ## What is Recce Cloud?
-Recce Cloud is a data collaboration platform for teams doing data validation, impact analysis, and pull requests reviews. It helps data teams catch issues early, understand downstream impacts, and communicate changes clearly—all in one shared workspace. Instead of working alone in a local dev environment, teams can explore lineage, run custom queries, and validate metrics together, speeding up reviews and building trust across stakeholders.
+Recce Cloud is a data collaboration platform for teams doing data validation, impact analysis, and pull requests reviews. It helps data teams catch issues early, understand downstream impacts, and communicate changes clearly in one shared workspace. Instead of working in an isolated local environment, teams can explore lineage, run custom queries, and validate metrics together in a cloud-hosted environment.
 
 - [Learn more about different plans](https://reccehq.com/pricing)
 - Follow the [Getting Started](/get-started/) guide
@@ -14,9 +14,9 @@ Recce Cloud integrates with GitHub to support validation in your PR workflow. Th
 
 ### Prerequisite
 1. Sign in [Recce cloud](https://cloud.reccehq.com/)
-2. Click **Install** button to install Recce Cloud GitHub app to your personal or organization account.
-3. Authorize the repositories to the GitHub app.
-4. Prepare the GitHub personal access token with the `repo` permission. Please see the [GitHub document](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). And set it to your environment variable.
+2. Click **Install** button to install Recce Cloud GitHub app to your personal or organization account
+3. Authorize the repositories to the GitHub app
+4. Prepare the GitHub personal access token with the `repo` permission. Please see the [GitHub document](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). And set it to your environment variable
    ```
    export GITHUB_TOKEN=<token>
    ```
@@ -36,8 +36,8 @@ Recce Cloud integrates with GitHub to support validation in your PR workflow. Th
    git checkout -b <my-awesome-feature>
    ```
 1. Develop your features and prepare the dbt artifacts for the base (`target-base/`) and current (`target/`) environments.
-1. Create a pull request for this branch. Recce Cloud requires an open pull request in your GitHub repository. It also stores the latest Recce state for each pull request.
-1. Launch the Recce instance in the cloud mode. It will use the dbt artifacts in the local `target` and `target-base` and initiate a new review state if necessary.
+2. Create a pull request for this branch. Recce Cloud requires an open pull request in your GitHub repository. It also stores the latest Recce state for each pull request.
+3. Launch the Recce instance in the cloud mode. It will use the dbt artifacts in the local `target` and `target-base` and initiate a new review state if necessary.
    ```
    recce server --cloud
    ```
@@ -51,7 +51,7 @@ Recce Cloud integrates with GitHub to support validation in your PR workflow. Th
 If the review state is already available for this PR, you can open the Recce instance to review.
 
 1. Checkout the branch for the reviewed PR.
-1. Launch the Recce instance to review this PR
+2. Launch the Recce instance to review this PR
     ```
     recce server --review --cloud
     ```
@@ -105,14 +105,14 @@ recce summary --cloud > summary.md
 
 ### Recce cloud
 
-The cloud subcommand in recce provides functionality for managing state files in cloud storage.
+The cloud subcommand in Recce provides functionality for managing state files in cloud storage.
 
 #### purge
 
 You can purge the state from your current PR. It is useful when
 
 1. You forgot the password
-1. You would like to reset the state of this PR.
+1. You would like to reset the state of this PR
 
 ```shell
 git checkout <pr-branch>
@@ -139,6 +139,6 @@ recce cloud download
 
 ## GitHub Pull Request Status Check
 
-Recce Cloud integrate with the [GitHub Pull Request Status Check](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks). If there is recce review state synced to a PR, the PR would have a recce cloud check status. Once all checks in recce are approved, the check status would change to passed and ready to be merged.
+Recce Cloud integrate with the [GitHub Pull Request Status Check](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks). If there is Recce review state synced to a PR, the PR would have a Recce cloud check status. Once all checks in Recce are approved, the check status would change to passed and ready to be merged.
 
 ![alt text](../assets/images/recce-cloud/pr-checks-all-approved.png){: .shadow}

docs/7-cicd/preset-checks.md

@@ -13,7 +13,7 @@ To configure the preset checks, add the settings to the [recce config file](../8
 
 1. Add a check to your checklist
     ![alt text](../assets/images/7-cicd/preset-checks-prep.png){: .shadow}
-2. Open the menu for the check and select **Get Preset Check Template**.
+2. Open the menu for the check and select **Get Preset Check Template**
 3. Copy the yaml config from the dialog
     ![alt text](../assets/images/7-cicd/preset-checks-template.png){: .shadow}
 
@@ -40,9 +40,9 @@ To configure the preset checks, add the settings to the [recce config file](../8
 
 ### Recce Server
 
-1. When a new Recce instance is launched, all preset checks are automatically set up, but these checks are not executed at this time.
+1. When a new Recce instance is launched, all preset checks are automatically set up, but these checks are not executed at this time
     ![alt text](../assets/images/7-cicd/preset-checks.png){: .shadow}
-2. When the **Run Query** button is pressed, the check will be executed.
+2. When the **Run Query** button is pressed, the check will be executed
 
 ### Recce Run
 
@@ -69,7 +69,7 @@ To configure the preset checks, add the settings to the [recce config file](../8
     ```shell
     recce server recce_state.json
     ```
-3. You can show the summary of the state by the [recce summary](./recce-summary.md) command
+3. You can show the summary of the state by the [recce summary](./recce-summary.md) command.
     ```shell
     recce summary recce_state.json
     ```

docs/7-cicd/recce-summary.md

@@ -2,7 +2,7 @@
 title: Summary
 ---
 
-Recce `Summary` command is used to generate a summary based on the input state file. In the previous section, the `Run` command was used to generate a state file based on the two environments. It provides a way to integrate Recce into your CI/CD pipeline. The `Summary` command is used to generate a summary based on the output of `Run` command. You can also integrate the `Summary` command into your CI/CD pipeline to generate a summary based on the state file generated by the `Run` command. Therefor, the generated summary can be posted to your repository hosting platform, such as GitHub, GitLab, or Bitbucket.
+Recce `Summary` command is used to generate a summary based on the input state file. In the previous section, the `Run` command was used to generate a state file based on the two environments. It provides a way to integrate Recce into your CI/CD pipeline. The `Summary` command is used to generate a summary based on the output of `Run` command. You can also integrate the `Summary` command into your CI/CD pipeline to generate a summary based on the state file generated by the `Run` command. Thus allowing the generated summary can be posted to your repository hosting platform, such as GitHub, GitLab, or Bitbucket.
 
 ## Usage
 
@@ -18,7 +18,7 @@ recce summary recce-state.json
 
 ## Output
 
-The output of the `summary` command will be Markdown format. The markdown output will contain the following sections:
+The output of the `summary` command will be in markdown format. The markdown output will contain the following sections:
 
 - Lineage Graph - A graph that shows the lineage of the models that are impacted by the modified models.
 - Checks Summary - A summary of the checks that are detected mismatch between `base` and `current` environments.