Update merge jobs language (#6548)

## What are you changing in this pull request and why?

CD generally stands for Continuous Delivery or Continuous Deployment
(see https://en.wikipedia.org/wiki/Continuous_delivery). It also appears
we are using this language elsewhere.

## Checklist

- [x] I have reviewed the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.

<!-- vercel-deployment-preview -->
---
🚀 Deployment available! Here are the direct links to the updated files:


-
https://docs-getdbt-com-git-continuous-delivery-dbt-labs.vercel.app/docs/deploy/merge-jobs

<!-- end-vercel-deployment-preview -->

---------

Co-authored-by: Matt Shaver <[email protected]>

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

@@ -5,7 +5,7 @@ description: "Learn how to trigger a dbt job run when a Git pull request merges.
 ---
 
 
-You can set up a merge job to implement a continuous development (CD) workflow in dbt Cloud. The merge job triggers a dbt job to run when someone merges Git pull requests into production. This workflow creates a seamless development experience where changes made in code will automatically update production data. Also, you can use this workflow for running `dbt compile` to update your environment's manifest so subsequent CI job runs are more performant.
+You can set up a merge job to implement a continuous deployment (CD) workflow in dbt Cloud. The merge job triggers a dbt job to run when someone merges Git pull requests into production. This workflow creates a seamless development experience where changes made in code will automatically update production data. Also, you can use this workflow for running `dbt compile` to update your environment's manifest so subsequent CI job runs are more performant.
 
 By using CD in dbt Cloud, you can take advantage of deferral to build only the edited model and any downstream changes. With merge jobs, state will be updated almost instantly, always giving the most up-to-date state information in [dbt Explorer](/docs/collaborate/explore-projects).
 
@@ -62,4 +62,4 @@ The following is an example of creating a new **Code pushed** trigger in Azure D
 
 <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/example-azuredevops-new-event.png" title="Example of creating a new trigger to push events in Azure Devops"/>
 
-</Expandable>
+</Expandable>