Update docs/cloud/features/branch-review.mdx

Co-authored-by: Tyler Biethman <[email protected]>

Author: marktnoonan

docs/cloud/features/branch-review.mdx

@@ -35,7 +35,7 @@ repo's **develop** or **main** branch. Here's how this scenario appears in Branc
   alt="Cypress Branch Review"
 />
 
-Without Branch Review pinpointing changes in your test suite's results requires a manual side-by-side comparison between your newly-introduced branch's test runs and your base branch's test runs. This sub-optimal workflow often fails to answer the fundamental questions, _what changed_ and _why?_ You might be left wondering if the same tests are flaky between branches, when new failures were introduced, or if you added sufficient test coverage to your new branch.
+Without Branch Review, pinpointing changes in your test suite's results requires a manual side-by-side comparison between your newly-introduced branch's test runs and your base branch's test runs. This sub-optimal workflow often fails to answer the fundamental questions, _what changed_ and _why?_ You might be left wondering if the same tests are flaky between branches, when new failures were introduced, or if you added sufficient test coverage to your new branch.
 
 ## Getting Started