feat: DRC-1868

- Fix Karen's comments

Signed-off-by: Jared Scott <[email protected]>

Author: gcko

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

@@ -1,8 +1,8 @@
 ---
-title: Getting Started
+title: CI/CD Getting Started
 ---
 
-# Getting Started
+# CI/CD Getting Started
 
 Automate data validation in your development workflow. Catch data issues before they reach production with continuous integration and delivery built specifically for dbt projects.
 
@@ -15,6 +15,9 @@ Set up automated workflows that:
 - **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.
+
 ## Understanding CI vs CD
 
 Recce uses both continuous integration and continuous delivery to automate data validation:
@@ -51,9 +54,6 @@ If your dbt project uses GitLab:
 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
 
-!!!note
-    CI/CD automation requires Recce Cloud Team plan. A free trial is available.
-
 ## Prerequisites
 
 Before setting up, ensure you have:

mkdocs.yml

@@ -76,7 +76,7 @@ nav:
           - 6-collaboration/share.md
       - CI/CD:
           # Brief intro explaining GitHub vs GitLab paths
-          - 7-cicd/getting-started.md
+          - 7-cicd/ci-cd-getting-started.md
 
           # GitHub CI/CD
           - Using GitHub: