clarify deployment vs main

Author: ethanpalm

editor.mdx

@@ -114,7 +114,7 @@ Markdown mode provides direct access to the underlying MDX code of your document
 
 The **Publish** button works differently depending on your branch:
 
-* **Main branch**: Updates your live site immediately.
+* **Deployment branch**: Updates your live site immediately.
 * **Other branches**: Creates a pull request for review.
 
 <Frame>
@@ -132,7 +132,7 @@ The **Publish** button works differently depending on your branch:
 
 ## Branches
 
-Branches allow you to work on documentation changes without updating the main version until you're ready for your changes to go live.
+Branches allow you to safely work on changes without affecting your live documentation. When your changes are ready, you can merge them into your deployment branch and make them live.
 
 <Tip>
   Use branches for significant updates, new sections, or when multiple team members are working on different parts of the documentation simultaneously.
@@ -158,7 +158,7 @@ When you are working on a branch, your changes are not automatically saved.
 
 ## Pull Requests
 
-Pull requests (or PRs) let you and other people review changes that you've made on a branch and then merge those changes into your main documentation.
+Pull requests (or PRs) let you and other people review changes that you've made on a branch and then merge those changes into your documentation.
 
 ### Creating a Pull Request on a Branch 
 
@@ -186,7 +186,7 @@ You can review pull requests in your Git platform (GitHub, GitLab).
 
 After you create a pull request, you can see a preview deployment of the changes.
 
-After a reviewer approves a pull request, you can merge the pull request into your main branch and the changes will be deployed to your live documentation site.
+After a reviewer approves a pull request, you can merge it to deploy the changes to your live documentation site.
 
 ## Git Synchronization
 
@@ -196,11 +196,11 @@ The web editor integrates with your Git repository, ensuring that all changes ar
 
 * **Authentication**: The web editor connects to your Git repository through our [GitHub App](/settings/github) or [GitLab integration](/settings/gitlab).
 
-* **Automatic fetching**: When you open the editor, it automatically fetches the latest content from your repository's main branch.
+* **Automatic fetching**: When you open the editor, it automatically fetches the latest content from your repository's deployment branch.
 
 * **Change tracking**: As you make edits, the web editor tracks changes and can commit them to your repository.
 
-* **Branching**: You can make changes directly to your main branch or to a separate branch, depending on your workflow preferences.
+* **Branching**: You can make changes directly to your deployment branch or to a separate branch, depending on your workflow preferences.
 
 * **Pull requests**: For collaborative workflows, you can create pull requests from the web editor.
 
@@ -224,7 +224,7 @@ A commit is a snapshot of changes to your documentation at a specific point in t
 
 <Accordion title="Branch">
 
-A branch is a parallel version of your documentation that allows you to work on changes without affecting the main version. The web editor allows you to create and switch between branches.
+A branch is a parallel version of your documentation that allows you to work on changes without affecting the live version. The web editor allows you to create and switch between branches.
 
 </Accordion>