update header

website/docs/docs/deploy/ci-jobs.md

@@ -41,7 +41,7 @@ To make CI job creation easier, many options on the **CI job** page are set to d
       To review the comparison report, navigate to the [Compare tab](/docs/deploy/run-visibility#compare-tab) in the job run's details. A summary of the report is also available from the pull request in your Git provider (see the [CI report example](#example-ci-report)). 
 
       :::info Optimization tip 
-      When you enable the **Run compare changes** checkbox, you can customize the comparison command to optimize your CI job. For example, if you have large models that take a long time to compare, you can exclude them to speed up the process using the `--exclude` flag. Use [custom dbt syntaxes](/docs/deploy/job-commands#advanced-ci-compare-changes) for the list of syntaxes to modify the selection criteria.
+      When you enable the **Run compare changes** checkbox, you can customize the comparison command to optimize your CI job. For example, if you have large models that take a long time to compare, you can exclude them to speed up the process using the `--exclude` flag. Use [custom commands](/docs/deploy/job-commands#advanced-ci-compare-changes) to modify the selection criteria.
       :::
 
     - **Compare changes against an environment (Deferral)** — By default, it’s set to the **Production** environment if you created one. This option allows dbt Cloud to check the state of the code in the PR against the code running in the deferred environment, so as to only check the modified code, instead of building the full table or the entire DAG.
@@ -53,7 +53,7 @@ To make CI job creation easier, many options on the **CI job** page are set to d
     - **Run timeout** — Cancel the CI job if the run time exceeds the timeout value. You can use this option to help ensure that a CI check doesn't consume too much of your warehouse resources. If you enable the **Run compare changes** option, the timeout value defaults to `3600` (one hour) to prevent long-running comparisons. 
 
 
-1. (optional) Options in the **Advanced settings** section: 
+2. (optional) Options in the **Advanced settings** section: 
     - **Environment variables** — Define [environment variables](/docs/build/environment-variables) to customize the behavior of your project when this CI job runs. You can specify that a CI job is running in a _Staging_ or _CI_ environment by setting an environment variable and modifying your project code to behave differently, depending on the context. It's common for teams to process only a subset of data for CI runs, using environment variables to branch logic in their dbt project code.
     - **Target name** — Define the [target name](/docs/build/custom-target-names). Similar to **Environment Variables**, this option lets you customize the behavior of the project. You can use this option to specify that a CI job is running in a _Staging_ or _CI_ environment by setting the target name and modifying your project code to behave differently, depending on the context. 
     - **dbt version** — By default, it’s set to inherit the [dbt version](/docs/dbt-versions/core) from the environment. dbt Labs strongly recommends that you don't change the default setting. This option to change the version at the job level is useful only when you upgrade a project to the next dbt version; otherwise, mismatched versions between the environment and job can lead to confusing behavior.

website/docs/docs/deploy/job-commands.md

@@ -48,7 +48,7 @@ Use [selectors](/reference/node-selection/syntax) as a powerful way to select an
 
 :::
 
-#### Advanced CI compare changes
+#### Compare changes custom commands
 For users that have Advanced CI's [compare changes](/docs/deploy/advanced-ci#compare-changes) feature enabled, you can use a custom dbt syntax to exclude specific large models (or groups of models with tags) to optimize running the comparison. Running comparisons on large models can significantly increase the time it takes for CI jobs to complete. 
 
 Here are some examples of how you can customize the comparison command: