updating file with edits

Author: doriwilson

docs/7-cicd/ci-cd-getting-started.md

@@ -10,82 +10,78 @@ Automate data validation in your development workflow. Catch data issues before
 
 Set up automated workflows that:
 
-- **Maintain current baselines** - Auto-update comparison baselines on every merge to main
-- **Validate every PR/MR** - Run data validation checks automatically when changes are proposed
+- **Save time on reviews** - Eliminate manual validation steps for every change
+- **Run data validations on every pull request/merge request** - Run data validation checks automatically when changes are proposed
 - **Prevent regressions** - Catch data quality issues before they reach production
-- **Save team time** - Eliminate manual validation steps for every change
 
 !!!note
-    CI/CD automation requires Recce Cloud Team plan. A free trial is available.
+    CI/CD automation requires a Cloud Plan. Get started for free [here](https://cloud.reccehq.com/).
 
-## Understanding CI vs CD
+## What is CI/CD? 
 
-Recce uses both continuous integration and continuous delivery to automate data validation:
+Recce uses both continuous integration (CI) and continuous delivery (CD) to automate data validation:
 
 **Continuous Integration (CI)**
 
-- **When**: Runs on every PR/MR update
-- **Purpose**: Validates proposed changes against baseline
+- **When**: Runs when you open a new or update a Pull Request/Merge Request 
+- **Purpose**: Validates proposed changes against baseline (typically this mean production)
 - **Benefit**: Catches issues before merge, with results in your PR/MR
 
 **Continuous Delivery (CD)**
 
 - **When**: Runs after merge to main branch
-- **Purpose**: Updates your baseline Recce session with latest production state
+- **Purpose**: Updates baseline artifacts Recce uses to with latest production state
 - **Benefit**: Ensures future comparisons use current baseline
 
-## Choose your platform
+## What does look like with Recce?
 
-Recce integrates with both GitHub Actions and GitLab CI/CD.
-
-Select your Git platform to get started:
+Both CI and CD workflows follow the same pattern:
 
-### GitHub
-If your dbt project uses GitHub:
+1. **Trigger event** (merge to main, or PR/MR opened/updated)
+2. **Generate dbt artifacts** (`dbt docs generate` or external source)
+3. **Upload to Recce Cloud** (automatic via workflow action)
+4. **Validation results** appear in Recce dashboard and PR/MR
 
-1. [Setup CI](./github/setup-ci.md) - Auto-validate changes in every PR
-2. [Setup CD](./github/setup-cd.md) - Auto-update baseline on merge to main
+<figure markdown>
+  ![Recce CI/CD architecture](../assets/images/7-cicd/ci-cd.png){: .shadow}
+  <figcaption>Automated validation workflow for pull requests</figcaption>
+</figure>
 
-### GitLab
-If your dbt project uses GitLab:
+## Getting Started with your CI/CD
 
-2. [Setup CI](./gitlab/setup-ci.md) - Auto-validate changes in every MR
-1. [Setup CD](./gitlab/setup-cd.md) - Auto-update baseline on merge to main
-3. [GitLab Personal Access Token Guide](./gitlab/gitlab-pat-guide.md) - Required for GitLab integration
+Recce currently integrates with both GitHub Actions and GitLab CI/CD. If you use another CI/CD product and interested in Recce, [let us know](https://cal.com/team/recce/chat).
 
 ## Prerequisites
 
 Before setting up, ensure you have:
 
-- **Recce Cloud account** with Team plan or free trial
+- **Recce Cloud account** You can signup and start your free trial [here](https://cloud.reccehq.com/)
 - **Repository connected** to Recce Cloud ([setup guide](../2-getting-started/start-free-with-cloud.md#git-integration))
-- **dbt artifacts** (`manifest.json` and `catalog.json`) from your project
+- **dbt artifacts generated** (`manifest.json` and `catalog.json`) from your project
 
-## Architecture overview
+### GitHub
+If your dbt project uses GitHub:
 
-Both CI and CD workflows follow the same pattern:
+1. [Setup CD](./github/setup-cd.md) - Auto-update baseline on merge to main
+2. [Setup CI](./github/setup-ci.md) - Auto-validate changes in every PR
 
-1. **Trigger event** (merge to main, or PR/MR opened/updated)
-2. **Generate dbt artifacts** (`dbt docs generate` or external source)
-3. **Upload to Recce Cloud** (automatic via workflow action)
-4. **Validation results** appear in Recce dashboard and PR/MR
+### GitLab
+If your dbt project uses GitLab:
 
-<figure markdown>
-  ![Recce CI/CD architecture](../assets/images/7-cicd/ci-cd.png){: .shadow}
-  <figcaption>Automated validation workflow for pull requests</figcaption>
-</figure>
+1. [Setup CD](./gitlab/setup-cd.md) - Auto-update baseline on merge to main
+2. [Setup CI](./gitlab/setup-ci.md) - Auto-validate changes in every MR
+3. [GitLab Personal Access Token Guide](./gitlab/gitlab-pat-guide.md) - Required for GitLab integration
 
 ## Next steps
 
-1. Choose your platform (GitHub or GitLab)
-2. Start with CD setup to establish baseline updates
-3. Add CI setup to enable PR/MR validation
-4. Review [best practices](./best-practices-prep-env.md) for environment preparation
+1. Start with relevant CD setup ([Gitlab](./gitlab/setup-cd.md) or [Github](./github/setup-cd.md)) to establish automatic baseline (production artifacts) updates.
+2. Configure CI setup ([Gitlab](./gitlab/setup-ci.md) or [Github](./github/setup-ci.md)) to enable PR/MR validation
+3. Review [best practices](./best-practices-prep-env.md) for environment preparation
 
 ## Related workflows
 
 After setting up CI/CD automation, explore these workflow guides:
 
-- [Development workflow](./scenario-dev.md) - Validate changes during development
-- [PR/MR review workflow](./scenario-pr-review.md) - Collaborate on validation results
-- [Preset checks](./preset-checks.md) - Configure automatic validation checks
+- [Development workflow](./scenario-dev.md) - How to validate data impact during development (pre-PR/MR)
+- [PR/MR review workflow](./scenario-pr-review.md) - How to collaborate with teammates using Recce in PRs/MRs
+- [Preset checks](./preset-checks.md) - How to configure automatic validation checks