Remove old GitLab versions from Proj Mgmt pages

Remove old GitLab versions from Proj Mgmt pages

doc/user/award_emojis.md

@@ -6,11 +6,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Award emoji **(FREE)**
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/1825) in GitLab 8.2.
-> - GitLab 9.0 [introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9570) the usage of native emoji if the platform
->   supports them and falls back to images or CSS sprites. This change greatly
->   improved award emoji performance overall.
-
 When you're collaborating online, you get fewer opportunities for high-fives
 and thumbs-ups. Emoji can be awarded to [issues](project/issues/index.md), [merge requests](project/merge_requests/index.md),
 [snippets](snippets.md), and anywhere you can have a thread.
@@ -24,8 +19,6 @@ For information on the relevant API, see [Award Emoji API](../api/award_emoji.md
 
 ## Sort issues and merge requests on vote count
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/2781) in GitLab 8.5.
-
 You can quickly sort issues and merge requests by the number of votes they
 have received. The sort options can be found in the dropdown menu as "Most
 popular" and "Least popular".
@@ -38,8 +31,6 @@ downvotes.
 
 ## Award emoji for comments
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/4291) in GitLab 8.9.
-
 Award emoji can also be applied to individual comments when you want to
 celebrate an accomplishment or agree with an opinion.
 

doc/user/project/labels.md

@@ -156,8 +156,6 @@ to the project:
 
 ## Scoped labels **(PREMIUM)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9175) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.10.
-
 Scoped labels allow teams to use the label feature to annotate issues, merge requests
 and epics with mutually exclusive labels. This can enable more complicated workflows
 by preventing certain labels from being used together.
@@ -241,14 +239,14 @@ to label notifications for the project only, or the whole group.
 
 ## Label priority
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/14189) in GitLab 8.9.
-> - Priority sorting is based on the highest priority label only. [This discussion](https://gitlab.com/gitlab-org/gitlab/-/issues/14523) considers changing this.
-
 Labels can have relative priorities, which are used in the **Label priority** and
 **Priority** sort orders of issues and merge request list pages. Prioritization
 for both group and project labels happens at the project level, and cannot be done
 from the group label list.
 
+NOTE:
+Priority sorting is based on the highest priority label only. [This discussion](https://gitlab.com/gitlab-org/gitlab/-/issues/14523) considers changing this.
+
 From the project label list page, star a label to indicate that it has a priority.
 
 ![Labels prioritized](img/labels_prioritized_v13_5.png)

doc/user/todos.md

@@ -7,8 +7,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # To-Do List **(FREE)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/2817) in GitLab 8.5.
-
 Your *To-Do List* is a chronological list of items waiting for your input.
 The items are known as *to-do items*.
 
@@ -67,8 +65,6 @@ You can manually add an item to your To-Do List.
 
 ## Create a to-do item by directly addressing someone
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7926) in GitLab 9.0.
-
 You can create a to-do item by directly addressing someone at the start of a line.
 For example, in the following comment: