Skip to content

Commit e264503

Browse files
authored
Fix typo on Branch Review page (#6272)
Fix "These might might represent different builds of the application [...]"
1 parent ac1d304 commit e264503

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/cloud/features/branch-review.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Compare which tests are failing, flaky, pending, added, or modified between the
2424
UI Coverage or Cypress Accessibility changes between runs will also appear here.
2525

2626
Branch Review is useful even if you do not have a Pull Request workflow, because it allows you to compare any two runs of your choice.
27-
These might might represent different builds of the application, changes in test code, or results from nightly runs. This page will use
27+
These might represent different builds of the application, changes in test code, or results from nightly runs. This page will use
2828
the example of a Pull Request made using the GitHub integration, but this integration is not required in order to use Branch Review.
2929

3030
A common scenario throughout the software development lifecycle (SDLC) is an engineer's **feature** branch that will be merged into the

0 commit comments

Comments
 (0)