Rearrange the second paragraph of overview

doc/user/project/labels.md

@@ -2,18 +2,18 @@
 
 ## Overview
 
-As your count of issues, MRs and Epics grow within GitLab it becomes more and more challenging
+As your count of issues, merge requests, and epics grows in GitLab, it's more and more challenging
 to keep track of those items. Especially as your organization grows from just a few people to
 hundreds or thousands. This is where labels come in. They help you organize and tag your work
-so you can easily track and find the work items you're interested in.
+so you can track and find the work items you're interested in.
 
-Labels allow you to categorize epics, issues, and merge requests using descriptive titles like
-`bug`, `feature request`, or `docs`, as well as customizable colors. They allow you to quickly
-and dynamically filter and manage epics, issues, and merge requests, and are a key
-part of [issue boards](issue_board.md).
+Labels are a key part of [issue boards](issue_board.md). With labels you can:
 
-You can use labels to help [search](../search/index.md#issues-and-merge-requests) in
-lists of issues, merge requests, and epics, as well as [search in issue boards](../search/index.md#issue-boards).
+- Categorize epics, issues, and merge requests using colors and descriptive titles like
+`bug`, `feature request`, or `docs`.
+- Dynamically filter and manage epics, issues, and merge requests.
+- [Search lists of issues, merge requests, and epics](../search/index.md#issues-and-merge-requests),
+  as well as [issue boards](../search/index.md#issue-boards).
 
 ## Project labels and group labels