1 files changed, 21 insertions, 7 deletions
diff --git a/doc/user/project/repository/branches/index.md b/doc/user/project/repository/branches/index.md
index 4d0cf28593d..d049b2108ee 100644
--- a/doc/user/project/repository/branches/index.md
+++ b/doc/user/project/repository/branches/index.md
@@ -64,7 +64,7 @@ against accidental deletion and forced pushes.
 
 By default, when you create a new project in GitLab, the initial branch is called `master`.
 For self-managed instances, a GitLab administrator can customize the initial branch name to something
-else. This way, every new project created from then on will start from the custom branch name rather than `master`. To do so:
+else. This way, every new project created from then on starts from the custom branch name rather than `master`. To do so:
 
 1. Go to the **Admin Area > Settings > Repository** and expand **Default initial
    branch name**.
@@ -96,10 +96,11 @@ To compare branches in a repository:
 
 1. Navigate to your project's repository.
 1. Select **Repository > Compare** in the sidebar.
-1. Select branches to compare using the [branch filter search box](#branch-filter-search-box)
+1. Select the target repository to compare with the [repository filter search box](#repository-filter-search-box).
+1. Select branches to compare using the [branch filter search box](#branch-filter-search-box).
 1. Click **Compare** to view the changes inline:
 
-![compare branches](img/compare_branches.png)
+   ![compare branches](img/compare_branches_v13_10.png)
 
 ## Delete merged branches
 
@@ -108,17 +109,30 @@ To compare branches in a repository:
 ![Delete merged branches](img/delete_merged_branches.png)
 
 This feature allows merged branches to be deleted in bulk. Only branches that
-have been merged and [are not protected](../../protected_branches.md) will be deleted as part of
+have been merged and [are not protected](../../protected_branches.md) are deleted as part of
 this operation.
 
 It's particularly useful to clean up old branches that were not deleted
 automatically when a merge request was merged.
 
+## Repository filter search box
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52967) in GitLab 13.10.
+
+This feature allows you to search and select a repository quickly when [comparing branches](#compare).
+
+![Repository filter search box](img/repository_filter_search_box_v13_10.png)
+
+Search results appear in the following order:
+
+- Repositories with names exactly matching the search terms.
+- Other repositories with names that include search terms, sorted alphabetically.
+
 ## Branch filter search box
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22166) in GitLab 11.5.
 
-![Branch filter search box](img/branch_filter_search_box.png)
+![Branch filter search box](img/branch_filter_search_box_v13_10.png)
 
 This feature allows you to search and select branches quickly. Search results appear in the following order:
 
@@ -127,8 +141,8 @@ This feature allows you to search and select branches quickly. Search results ap
 
 Sometimes when you have hundreds of branches you may want a more flexible matching pattern. In such cases you can use the following:
 
-- `^feature` will only match branch names that begin with 'feature'.
-- `feature$` will only match branch names that end with 'feature'.
+- `^feature` matches only branch names that begin with 'feature'.
+- `feature$` matches only branch names that end with 'feature'.
 
 <!-- ## Troubleshooting