diff --git a/docs/guides/cloud/branch-review.mdx b/docs/guides/cloud/branch-review.mdx
index ae425abac5..bc83d3d6e1 100644
--- a/docs/guides/cloud/branch-review.mdx
+++ b/docs/guides/cloud/branch-review.mdx
@@ -72,7 +72,7 @@ If you do not see PR # tags associated with a branch, you may need to [pass PR n
 
 #### Latest Runs
 
-If the selected branch has a PR associated and a PR # passed via CI, there is an additional callout on the top of the overview tab of the **Latest runs** page directs to the Branch Review.
+If the selected branch has a PR associated and a PR # passed via CI, there is an additional callout on the top of the overview tab of the **Latest runs** page which directs to the Branch Review.
 
 <DocsImage
   src="/img/guides/cloud/branch-review/branch-review-available.jpg"
@@ -107,7 +107,7 @@ Clicking the branch label will link you directly to the appropriate [run overvie
 
 ### Review Test Status
 
-When on the review screen, you will see tabs Failures, Flaky, Pending, Added, and Modified. Each tab will show you the specs that fall into that category. You can click on a test to view the test details.
+When on the review screen, you will see the Failures, Flaky, Pending, Added, and Modified tabs. Each tab will show you the specs that fall into that category. You can click on a test to view the test details.
 
 <DocsImage
   src="/img/guides/cloud/branch-review/branch-review-details.jpg"
@@ -128,7 +128,7 @@ When on the review screen, you will see tabs Failures, Flaky, Pending, Added, an
 4. The test state (failed, flaky, pending) is also indicated at the spec level
    - _new_ = the state was <u>not</u> previously captured, but now <u>is</u> captured<br />(newly pending tests can imply an `it.skip()` was not removed)
    - _existing_ = the state <u>was</u> previously captured and now <u>is still</u> captured
-   - _resolved_ = the state <u>was</u> previously captured but now is <u>no longer</u>
+   - _resolved_ = the state <u>was</u> previously captured but now is <u>no longer</u> captured
 
 :::