concsion

Author: ethanpalm

editor/branches.mdx

@@ -3,13 +3,9 @@ title: "Working with branches"
 description: "Use branches to make and review changes without affecting your live documentation"
 ---
 
-Branches are a version control feature that let you create separate instances of your documentation, then merge into your main branch if you want to publish your changes. Think of a branch as a copy of your documentation where you can experiment, make edits, and test changes before they go live.
+Branches let you create separate instances of your documentation to make changes, get reviews, and try new approaches before publishing. Your team can work on branches to update different parts of your documentation at the same time without affecting what users see on your live site until you publish any changes.
 
-A benefit of branches is that your team can work simultaneously on seprate branches without getting in each other's way. Even if two different branches make changes to the same file, you will be required to resolve any conflicts before merging branches and publishing your docs updates.
-
-If you decide that you don't want to publish changes from a branch, you can delete the branch with no consequences. This makes branch a safe place to experiment and try new approaches to your content.
-
-We recommend that you always work from branches when you're updating your documentation. This ensures that your live site stays stable and enables review workflows for any updates.
+We recommend always working from branches when updating documentation to keep your live site stable and enable review workflows.
 
 ## Creating a branch