Add latest changes from gitlab-org/gitlab@master

64 files changed, 376 insertions, 182 deletions

diff --git a/doc/.vale/gitlab/spelling-exceptions.txt b/doc/.vale/gitlab/spelling-exceptions.txt
index 9e7fdef62c3..c3dc596acb7 100644
--- a/doc/.vale/gitlab/spelling-exceptions.txt
+++ b/doc/.vale/gitlab/spelling-exceptions.txt
@@ -1,3 +1,5 @@
+accessor
+accessors
 Akismet
 Alertmanager
 Algolia
@@ -75,6 +77,7 @@ burndown
 burnup
 burstable
 cacheable
+Caddy
 callstack
 callstacks
 Camo
@@ -291,6 +294,7 @@ Leiningen
 libFuzzer
 Libravatar
 liveness
+Lodash
 Lograge
 logrotate
 Logrus
@@ -582,11 +586,14 @@ swimlane
 swimlanes
 syncable
 Sysbench
+syscall
+syscalls
 syslog
 tanuki
 tcpdump
 templated
 Thanos
+Thoughtbot
 throughputs
 Tiller
 timebox
@@ -605,6 +612,7 @@ toolkits
 tooltip
 tooltips
 transpile
+transpiled
 transpiles
 transpiling
 Trello
@@ -636,6 +644,7 @@ unchecks
 uncomment
 uncommented
 uncommenting
+uncordon
 unencode
 unencoded
 unencoder
@@ -742,6 +751,7 @@ Worldline
 Xcode
 Xeon
 YouTrack
+Yubico
 Zeitwerk
 Zendesk
 zsh
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md
index 460f8470092..2b7a7300ad8 100644
--- a/doc/administration/pages/index.md
+++ b/doc/administration/pages/index.md
@@ -971,3 +971,21 @@ If the wildcard DNS [prerequisite](#prerequisites) can't be met, you can still u
 1. [Move](../../user/project/settings/index.md#transferring-an-existing-project-into-another-namespace)
    all projects you need to use Pages with into a single group namespace, for example `pages`.
 1. Configure a [DNS entry](#dns-configuration) without the `*.`-wildcard, for example `pages.example.io`.
+
+### Pages daemon fails with permission denied errors
+
+If `/tmp` is mounted with `noexec`, the Pages daemon fails to start with an error like:
+
+```plaintext
+{"error":"fork/exec /gitlab-pages: permission denied","level":"fatal","msg":"could not create pages daemon","time":"2021-02-02T21:54:34Z"}
+```
+
+In this case, change `TMPDIR` to a location that is not mounted with `noexec`. Add the following to
+`/etc/gitlab/gitlab.rb`:
+
+```ruby
+gitlab_pages['env'] = {'TMPDIR' => '<new_tmp_path>'}
+```
+
+Once added, reconfigure with `sudo gitlab-ctl reconfigure` and restart GitLab with
+`sudo gitlab-ctl restart`.
diff --git a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
index 26e44a49aec..7b8828dc14e 100644
--- a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
+++ b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
@@ -88,7 +88,7 @@ and they will assist you with any issues you are having.
 
 - Minimal configuration that can be used to [test a Kubernetes Helm chart](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/620).
 
-- Tailing logs of a separate pod. An example for a Webservice pod:
+- Tailing logs of a separate pod. An example for a `webservice` pod:
 
   ```shell
   kubectl logs gitlab-webservice-54fbf6698b-hpckq -c webservice
diff --git a/doc/api/graphql/reference/gitlab_schema.graphql b/doc/api/graphql/reference/gitlab_schema.graphql
index 36f19032154..3f716767748 100644
--- a/doc/api/graphql/reference/gitlab_schema.graphql
+++ b/doc/api/graphql/reference/gitlab_schema.graphql
@@ -350,7 +350,7 @@ type AlertManagementAlert implements Noteable {
   title: String
 
   """
-  To-dos of the current user for the alert.
+  To-do items of the current user for the alert.
   """
   todos(
     """
@@ -1017,7 +1017,7 @@ type AlertSetAssigneesPayload {
   issue: Issue
 
   """
-  The todo after mutation.
+  The to-do item after mutation.
   """
   todo: Todo
 }
@@ -1067,7 +1067,7 @@ type AlertTodoCreatePayload {
   issue: Issue
 
   """
-  The todo after mutation.
+  The to-do item after mutation.
   """
   todo: Todo
 }
@@ -1734,7 +1734,7 @@ type BoardEpic implements CurrentUserTodos & Noteable {
   createdAt: Time
 
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -1758,7 +1758,7 @@ type BoardEpic implements CurrentUserTodos & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -4515,7 +4515,7 @@ type CreateAlertIssuePayload {
   issue: Issue
 
   """
-  The todo after mutation.
+  The to-do item after mutation.
   """
   todo: Todo
 }
@@ -5480,7 +5480,7 @@ type CreateTestCasePayload {
 
 interface CurrentUserTodos {
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -5504,7 +5504,7 @@ interface CurrentUserTodos {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -6622,7 +6622,7 @@ A single design
 """
 type Design implements CurrentUserTodos & DesignFields & Noteable {
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -6646,7 +6646,7 @@ type Design implements CurrentUserTodos & DesignFields & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -8580,7 +8580,7 @@ type Epic implements CurrentUserTodos & Noteable {
   createdAt: Time
 
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -8604,7 +8604,7 @@ type Epic implements CurrentUserTodos & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -9260,7 +9260,7 @@ type EpicIssue implements CurrentUserTodos & Noteable {
   createdAt: Time!
 
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -9284,7 +9284,7 @@ type EpicIssue implements CurrentUserTodos & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -12471,7 +12471,7 @@ type Issue implements CurrentUserTodos & Noteable {
   createdAt: Time!
 
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -12495,7 +12495,7 @@ type Issue implements CurrentUserTodos & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -14554,7 +14554,7 @@ type MergeRequest implements CurrentUserTodos & Noteable {
   createdAt: Time!
 
   """
-  Todos for the current user.
+  To-do items for the current user.
   """
   currentUserTodos(
     """
@@ -14578,7 +14578,7 @@ type MergeRequest implements CurrentUserTodos & Noteable {
     last: Int
 
     """
-    State of the todos.
+    State of the to-do items.
     """
     state: TodoStateEnum
   ): TodoConnection!
@@ -24925,47 +24925,47 @@ Representing a to-do entry
 """
 type Todo {
   """
-  Action of the to-do
+  Action of the to-do item
   """
   action: TodoActionEnum!
 
   """
-  The author of this to-do
+  The author of this to-do item
   """
   author: User!
 
   """
-  Body of the to-do
+  Body of the to-do item
   """
   body: String!
 
   """
-  Timestamp this to-do was created
+  Timestamp this to-do item was created
   """
   createdAt: Time!
 
   """
-  Group this to-do is associated with
+  Group this to-do item is associated with
   """
   group: Group
 
   """
-  ID of the to-do
+  ID of the to-do item
   """
   id: ID!
 
   """
-  The project this to-do is associated with
+  The project this to-do item is associated with
   """
   project: Project
 
   """
-  State of the to-do
+  State of the to-do item
   """
   state: TodoStateEnum!
 
   """
-  Target type of the to-do
+  Target type of the to-do item
   """
   targetType: TodoTargetEnum!
 }
@@ -25030,7 +25030,7 @@ type TodoCreatePayload {
   errors: [String!]!
 
   """
-  The to-do created.
+  The to-do item created.
   """
   todo: Todo
 }
@@ -25065,7 +25065,7 @@ input TodoMarkDoneInput {
   clientMutationId: String
 
   """
-  The global ID of the to-do to mark as done.
+  The global ID of the to-do item to mark as done.
   """
   id: TodoID!
 }
@@ -25085,7 +25085,7 @@ type TodoMarkDonePayload {
   errors: [String!]!
 
   """
-  The requested to-do.
+  The requested to-do item.
   """
   todo: Todo!
 }
@@ -25100,7 +25100,7 @@ input TodoRestoreInput {
   clientMutationId: String
 
   """
-  The global ID of the to-do to restore.
+  The global ID of the to-do item to restore.
   """
   id: TodoID!
 }
@@ -25115,7 +25115,7 @@ input TodoRestoreManyInput {
   clientMutationId: String
 
   """
-  The global IDs of the to-dos to restore (a maximum of 50 is supported at once).
+  The global IDs of the to-do items to restore (a maximum of 50 is supported at once).
   """
   ids: [TodoID!]!
 }
@@ -25135,14 +25135,14 @@ type TodoRestoreManyPayload {
   errors: [String!]!
 
   """
-  Updated to-dos.
+  Updated to-do items.
   """
   todos: [Todo!]!
 
   """
-  The IDs of the updated to-do items. Deprecated in 13.2: Use todos.
+  The IDs of the updated to-do items. Deprecated in 13.2: Use to-do items.
   """
-  updatedIds: [TodoID!]! @deprecated(reason: "Use todos. Deprecated in 13.2.")
+  updatedIds: [TodoID!]! @deprecated(reason: "Use to-do items. Deprecated in 13.2.")
 }
 
 """
@@ -25160,7 +25160,7 @@ type TodoRestorePayload {
   errors: [String!]!
 
   """
-  The requested to-do.
+  The requested to-do item.
   """
   todo: Todo!
 }
@@ -25232,14 +25232,14 @@ type TodosMarkAllDonePayload {
   errors: [String!]!
 
   """
-  Updated todos.
+  Updated to-do items.
   """
   todos: [Todo!]!
 
   """
-  Ids of the updated todos. Deprecated in 13.2: Use todos.
+  IDs of the updated to-do items. Deprecated in 13.2: Use to-do items.
   """
-  updatedIds: [TodoID!]! @deprecated(reason: "Use todos. Deprecated in 13.2.")
+  updatedIds: [TodoID!]! @deprecated(reason: "Use to-do items. Deprecated in 13.2.")
 }
 
 """
@@ -25509,7 +25509,7 @@ type UpdateAlertStatusPayload {
   issue: Issue
 
   """
-  The todo after mutation.
+  The to-do item after mutation.
   """
   todo: Todo
 }
@@ -26839,7 +26839,7 @@ type User {
   status: UserStatus
 
   """
-  Todos of the user
+  To-do items of the user
   """
   todos(
     """
diff --git a/doc/api/graphql/reference/gitlab_schema.json b/doc/api/graphql/reference/gitlab_schema.json
index be73d02f0f1..215ae78d5ff 100644
--- a/doc/api/graphql/reference/gitlab_schema.json
+++ b/doc/api/graphql/reference/gitlab_schema.json
@@ -953,7 +953,7 @@
             },
             {
               "name": "todos",
-              "description": "To-dos of the current user for the alert.",
+              "description": "To-do items of the current user for the alert.",
               "args": [
                 {
                   "name": "action",
@@ -2504,7 +2504,7 @@
             },
             {
               "name": "todo",
-              "description": "The todo after mutation.",
+              "description": "The to-do item after mutation.",
               "args": [
 
               ],
@@ -2648,7 +2648,7 @@
             },
             {
               "name": "todo",
-              "description": "The todo after mutation.",
+              "description": "The to-do item after mutation.",
               "args": [
 
               ],
@@ -4482,7 +4482,7 @@
             },
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -4526,7 +4526,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -12313,7 +12313,7 @@
             },
             {
               "name": "todo",
-              "description": "The todo after mutation.",
+              "description": "The to-do item after mutation.",
               "args": [
 
               ],
@@ -14902,7 +14902,7 @@
           "fields": [
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -14946,7 +14946,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -17991,7 +17991,7 @@
           "fields": [
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -18035,7 +18035,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -23713,7 +23713,7 @@
             },
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -23757,7 +23757,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -25584,7 +25584,7 @@
             },
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -25628,7 +25628,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -34062,7 +34062,7 @@
             },
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -34106,7 +34106,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -39886,7 +39886,7 @@
             },
             {
               "name": "currentUserTodos",
-              "description": "Todos for the current user.",
+              "description": "To-do items for the current user.",
               "args": [
                 {
                   "name": "after",
@@ -39930,7 +39930,7 @@
                 },
                 {
                   "name": "state",
-                  "description": "State of the todos.",
+                  "description": "State of the to-do items.",
                   "type": {
                     "kind": "ENUM",
                     "name": "TodoStateEnum",
@@ -72418,7 +72418,7 @@
           "fields": [
             {
               "name": "action",
-              "description": "Action of the to-do",
+              "description": "Action of the to-do item",
               "args": [
 
               ],
@@ -72436,7 +72436,7 @@
             },
             {
               "name": "author",
-              "description": "The author of this to-do",
+              "description": "The author of this to-do item",
               "args": [
 
               ],
@@ -72454,7 +72454,7 @@
             },
             {
               "name": "body",
-              "description": "Body of the to-do",
+              "description": "Body of the to-do item",
               "args": [
 
               ],
@@ -72472,7 +72472,7 @@
             },
             {
               "name": "createdAt",
-              "description": "Timestamp this to-do was created",
+              "description": "Timestamp this to-do item was created",
               "args": [
 
               ],
@@ -72490,7 +72490,7 @@
             },
             {
               "name": "group",
-              "description": "Group this to-do is associated with",
+              "description": "Group this to-do item is associated with",
               "args": [
 
               ],
@@ -72504,7 +72504,7 @@
             },
             {
               "name": "id",
-              "description": "ID of the to-do",
+              "description": "ID of the to-do item",
               "args": [
 
               ],
@@ -72522,7 +72522,7 @@
             },
             {
               "name": "project",
-              "description": "The project this to-do is associated with",
+              "description": "The project this to-do item is associated with",
               "args": [
 
               ],
@@ -72536,7 +72536,7 @@
             },
             {
               "name": "state",
-              "description": "State of the to-do",
+              "description": "State of the to-do item",
               "args": [
 
               ],
@@ -72554,7 +72554,7 @@
             },
             {
               "name": "targetType",
-              "description": "Target type of the to-do",
+              "description": "Target type of the to-do item",
               "args": [
 
               ],
@@ -72780,7 +72780,7 @@
             },
             {
               "name": "todo",
-              "description": "The to-do created.",
+              "description": "The to-do item created.",
               "args": [
 
               ],
@@ -72863,7 +72863,7 @@
           "inputFields": [
             {
               "name": "id",
-              "description": "The global ID of the to-do to mark as done.",
+              "description": "The global ID of the to-do item to mark as done.",
               "type": {
                 "kind": "NON_NULL",
                 "name": null,
@@ -72937,7 +72937,7 @@
             },
             {
               "name": "todo",
-              "description": "The requested to-do.",
+              "description": "The requested to-do item.",
               "args": [
 
               ],
@@ -72969,7 +72969,7 @@
           "inputFields": [
             {
               "name": "id",
-              "description": "The global ID of the to-do to restore.",
+              "description": "The global ID of the to-do item to restore.",
               "type": {
                 "kind": "NON_NULL",
                 "name": null,
@@ -73004,7 +73004,7 @@
           "inputFields": [
             {
               "name": "ids",
-              "description": "The global IDs of the to-dos to restore (a maximum of 50 is supported at once).",
+              "description": "The global IDs of the to-do items to restore (a maximum of 50 is supported at once).",
               "type": {
                 "kind": "NON_NULL",
                 "name": null,
@@ -73086,7 +73086,7 @@
             },
             {
               "name": "todos",
-              "description": "Updated to-dos.",
+              "description": "Updated to-do items.",
               "args": [
 
               ],
@@ -73112,7 +73112,7 @@
             },
             {
               "name": "updatedIds",
-              "description": "The IDs of the updated to-do items. Deprecated in 13.2: Use todos.",
+              "description": "The IDs of the updated to-do items. Deprecated in 13.2: Use to-do items.",
               "args": [
 
               ],
@@ -73134,7 +73134,7 @@
                 }
               },
               "isDeprecated": true,
-              "deprecationReason": "Use todos. Deprecated in 13.2."
+              "deprecationReason": "Use to-do items. Deprecated in 13.2."
             }
           ],
           "inputFields": null,
@@ -73191,7 +73191,7 @@
             },
             {
               "name": "todo",
-              "description": "The requested to-do.",
+              "description": "The requested to-do item.",
               "args": [
 
               ],
@@ -73363,7 +73363,7 @@
             },
             {
               "name": "todos",
-              "description": "Updated todos.",
+              "description": "Updated to-do items.",
               "args": [
 
               ],
@@ -73389,7 +73389,7 @@
             },
             {
               "name": "updatedIds",
-              "description": "Ids of the updated todos. Deprecated in 13.2: Use todos.",
+              "description": "IDs of the updated to-do items. Deprecated in 13.2: Use to-do items.",
               "args": [
 
               ],
@@ -73411,7 +73411,7 @@
                 }
               },
               "isDeprecated": true,
-              "deprecationReason": "Use todos. Deprecated in 13.2."
+              "deprecationReason": "Use to-do items. Deprecated in 13.2."
             }
           ],
           "inputFields": null,
@@ -74189,7 +74189,7 @@
             },
             {
               "name": "todo",
-              "description": "The todo after mutation.",
+              "description": "The to-do item after mutation.",
               "args": [
 
               ],
@@ -77580,7 +77580,7 @@
             },
             {
               "name": "todos",
-              "description": "Todos of the user",
+              "description": "To-do items of the user",
               "args": [
                 {
                   "name": "action",
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index 8d0b25a2093..bb0baa2eeee 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -102,7 +102,7 @@ Describes an alert from the project's Alert Management.
 | `startedAt` | Time | Timestamp the alert was raised. |
 | `status` | AlertManagementStatus | Status of the alert. |
 | `title` | String | Title of the alert. |
-| `todos` | TodoConnection | To-dos of the current user for the alert. |
+| `todos` | TodoConnection | To-do items of the current user for the alert. |
 | `updatedAt` | Time | Timestamp the alert was last updated. |
 
 ### AlertManagementAlertStatusCountsType
@@ -166,7 +166,7 @@ Autogenerated return type of AlertSetAssignees.
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
 | `issue` | Issue | The issue created after mutation. |
-| `todo` | Todo | The todo after mutation. |
+| `todo` | Todo | The to-do item after mutation. |
 
 ### AlertTodoCreatePayload
 
@@ -178,7 +178,7 @@ Autogenerated return type of AlertTodoCreate.
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
 | `issue` | Issue | The issue created after mutation. |
-| `todo` | Todo | The todo after mutation. |
+| `todo` | Todo | The to-do item after mutation. |
 
 ### AwardEmoji
 
@@ -278,7 +278,7 @@ Represents an epic on an issue board.
 | `closedAt` | Time | Timestamp of when the epic was closed. |
 | `confidential` | Boolean | Indicates if the epic is confidential. |
 | `createdAt` | Time | Timestamp of when the epic was created. |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `descendantCounts` | EpicDescendantCount | Number of open and closed descendant epics and issues. |
 | `descendantWeightSum` | EpicDescendantWeights | Total weight of open and closed issues in the epic and its descendants. |
 | `description` | String | Description of the epic. |
@@ -705,7 +705,7 @@ Autogenerated return type of CreateAlertIssue.
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
 | `issue` | Issue | The issue created after mutation. |
-| `todo` | Todo | The todo after mutation. |
+| `todo` | Todo | The to-do item after mutation. |
 
 ### CreateAnnotationPayload
 
@@ -1078,7 +1078,7 @@ A single design.
 
 | Field | Type | Description |
 | ----- | ---- | ----------- |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `diffRefs` | DiffRefs! | The diff refs for this design. |
 | `discussions` | DiscussionConnection! | All discussions on this noteable |
 | `event` | DesignVersionEvent! | How this design was changed in the current version. |
@@ -1400,7 +1400,7 @@ Represents an epic.
 | `closedAt` | Time | Timestamp of when the epic was closed. |
 | `confidential` | Boolean | Indicates if the epic is confidential. |
 | `createdAt` | Time | Timestamp of when the epic was created. |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `descendantCounts` | EpicDescendantCount | Number of open and closed descendant epics and issues. |
 | `descendantWeightSum` | EpicDescendantWeights | Total weight of open and closed issues in the epic and its descendants. |
 | `description` | String | Description of the epic. |
@@ -1516,7 +1516,7 @@ Relationship between an epic and an issue.
 | `confidential` | Boolean! | Indicates the issue is confidential |
 | `createNoteEmail` | String | User specific email address for the issue |
 | `createdAt` | Time! | Timestamp of when the issue was created |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `description` | String | Description of the issue |
 | `descriptionHtml` | String | The GitLab Flavored Markdown rendering of `description` |
 | `designCollection` | DesignCollection | Collection of design images associated with this issue |
@@ -1891,7 +1891,7 @@ Represents a recorded measurement (object count) for the Admins.
 | `confidential` | Boolean! | Indicates the issue is confidential |
 | `createNoteEmail` | String | User specific email address for the issue |
 | `createdAt` | Time! | Timestamp of when the issue was created |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `description` | String | Description of the issue |
 | `descriptionHtml` | String | The GitLab Flavored Markdown rendering of `description` |
 | `designCollection` | DesignCollection | Collection of design images associated with this issue |
@@ -2202,7 +2202,7 @@ Autogenerated return type of MarkAsSpamSnippet.
 | `commitsWithoutMergeCommits` | CommitConnection | Merge request commits excluding merge commits |
 | `conflicts` | Boolean! | Indicates if the merge request has conflicts |
 | `createdAt` | Time! | Timestamp of when the merge request was created |
-| `currentUserTodos` | TodoConnection! | Todos for the current user. |
+| `currentUserTodos` | TodoConnection! | To-do items for the current user. |
 | `defaultMergeCommitMessage` | String | Default merge commit message of the merge request |
 | `defaultMergeCommitMessageWithDescription` | String | Default merge commit message of the merge request with description |
 | `defaultSquashCommitMessage` | String | Default squash commit message of the merge request |
@@ -3703,15 +3703,15 @@ Representing a to-do entry.
 
 | Field | Type | Description |
 | ----- | ---- | ----------- |
-| `action` | TodoActionEnum! | Action of the to-do |
-| `author` | User! | The author of this to-do |
-| `body` | String! | Body of the to-do |
-| `createdAt` | Time! | Timestamp this to-do was created |
-| `group` | Group | Group this to-do is associated with |
-| `id` | ID! | ID of the to-do |
-| `project` | Project | The project this to-do is associated with |
-| `state` | TodoStateEnum! | State of the to-do |
-| `targetType` | TodoTargetEnum! | Target type of the to-do |
+| `action` | TodoActionEnum! | Action of the to-do item |
+| `author` | User! | The author of this to-do item |
+| `body` | String! | Body of the to-do item |
+| `createdAt` | Time! | Timestamp this to-do item was created |
+| `group` | Group | Group this to-do item is associated with |
+| `id` | ID! | ID of the to-do item |
+| `project` | Project | The project this to-do item is associated with |
+| `state` | TodoStateEnum! | State of the to-do item |
+| `targetType` | TodoTargetEnum! | Target type of the to-do item |
 
 ### TodoCreatePayload
 
@@ -3721,7 +3721,7 @@ Autogenerated return type of TodoCreate.
 | ----- | ---- | ----------- |
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
-| `todo` | Todo | The to-do created. |
+| `todo` | Todo | The to-do item created. |
 
 ### TodoMarkDonePayload
 
@@ -3731,7 +3731,7 @@ Autogenerated return type of TodoMarkDone.
 | ----- | ---- | ----------- |
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
-| `todo` | Todo! | The requested to-do. |
+| `todo` | Todo! | The requested to-do item. |
 
 ### TodoRestoreManyPayload
 
@@ -3741,8 +3741,8 @@ Autogenerated return type of TodoRestoreMany.
 | ----- | ---- | ----------- |
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
-| `todos` | Todo! => Array | Updated to-dos. |
-| `updatedIds` **{warning-solid}** | TodoID! => Array | **Deprecated:** Use todos. Deprecated in 13.2. |
+| `todos` | Todo! => Array | Updated to-do items. |
+| `updatedIds` **{warning-solid}** | TodoID! => Array | **Deprecated:** Use to-do items. Deprecated in 13.2. |
 
 ### TodoRestorePayload
 
@@ -3752,7 +3752,7 @@ Autogenerated return type of TodoRestore.
 | ----- | ---- | ----------- |
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
-| `todo` | Todo! | The requested to-do. |
+| `todo` | Todo! | The requested to-do item. |
 
 ### TodosMarkAllDonePayload
 
@@ -3762,8 +3762,8 @@ Autogenerated return type of TodosMarkAllDone.
 | ----- | ---- | ----------- |
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
-| `todos` | Todo! => Array | Updated todos. |
-| `updatedIds` **{warning-solid}** | TodoID! => Array | **Deprecated:** Use todos. Deprecated in 13.2. |
+| `todos` | Todo! => Array | Updated to-do items. |
+| `updatedIds` **{warning-solid}** | TodoID! => Array | **Deprecated:** Use to-do items. Deprecated in 13.2. |
 
 ### ToggleAwardEmojiPayload
 
@@ -3810,7 +3810,7 @@ Autogenerated return type of UpdateAlertStatus.
 | `clientMutationId` | String | A unique identifier for the client performing the mutation. |
 | `errors` | String! => Array | Errors encountered during execution of the mutation. |
 | `issue` | Issue | The issue created after mutation. |
-| `todo` | Todo | The todo after mutation. |
+| `todo` | Todo | The to-do item after mutation. |
 
 ### UpdateBoardEpicUserPreferencesPayload
 
@@ -3976,7 +3976,7 @@ Autogenerated return type of UpdateSnippet.
 | `starredProjects` | ProjectConnection | Projects starred by the user |
 | `state` | UserState! | State of the user |
 | `status` | UserStatus | User status |
-| `todos` | TodoConnection! | Todos of the user |
+| `todos` | TodoConnection! | To-do items of the user |
 | `userPermissions` | UserPermissions! | Permissions for the current user on the resource |
 | `username` | String! | Username of the user. Unique within this instance of GitLab |
 | `webPath` | String! | Web path of the user |
diff --git a/doc/api/groups.md b/doc/api/groups.md
index 25571af9874..0aba679655b 100644
--- a/doc/api/groups.md
+++ b/doc/api/groups.md
@@ -1010,7 +1010,7 @@ GET /groups?search=foobar
 ]
 ```
 
-## Hooks
+## Hooks **(PREMIUM)**
 
 Also called Group Hooks and Webhooks.
 These are different from [System Hooks](system_hooks.md) that are system wide and [Project Hooks](projects.md#hooks) that are limited to one project.
@@ -1057,6 +1057,7 @@ GET /groups/:id/hooks/:hook_id
   "wiki_page_events": true,
   "deployment_events": true,
   "releases_events": true,
+  "subgroup_events": true,
   "enable_ssl_verification": true,
   "created_at": "2012-10-12T17:04:47Z"
 }
@@ -1086,6 +1087,7 @@ POST /groups/:id/hooks
 | `wiki_page_events`           | boolean        | no       | Trigger hook on wiki events |
 | `deployment_events`          | boolean        | no       | Trigger hook on deployment events |
 | `releases_events`            | boolean        | no       | Trigger hook on release events |
+| `subgroup_events`            | boolean        | no       | Trigger hook on subgroup events |
 | `enable_ssl_verification`    | boolean        | no       | Do SSL verification when triggering the hook |
 | `token`                      | string         | no       | Secret token to validate received payloads; not returned in the response |
 
@@ -1114,6 +1116,7 @@ PUT /groups/:id/hooks/:hook_id
 | `wiki_events`                | boolean        | no       | Trigger hook on wiki events |
 | `deployment_events`          | boolean        | no       | Trigger hook on deployment events |
 | `releases_events`            | boolean        | no       | Trigger hook on release events |
+| `subgroup_events`            | boolean        | no       | Trigger hook on subgroup events |
 | `enable_ssl_verification`    | boolean        | no       | Do SSL verification when triggering the hook |
 | `token`                      | string         | no       | Secret token to validate received payloads; not returned in the response |
 
diff --git a/doc/api/settings.md b/doc/api/settings.md
index 6c035dea1ef..6c996caed7b 100644
--- a/doc/api/settings.md
+++ b/doc/api/settings.md
@@ -302,7 +302,7 @@ listed in the descriptions of the relevant settings.
 | `housekeeping_incremental_repack_period` | integer          | required by: `housekeeping_enabled`  | Number of Git pushes after which an incremental `git repack` is run. |
 | `html_emails_enabled`                    | boolean          | no                                   | Enable HTML emails. |
 | `import_sources`                         | array of strings | no                                   | Sources to allow project import from, possible values: `github`, `bitbucket`, `bitbucket_server`, `gitlab`, `fogbugz`, `git`, `gitlab_project`, `gitea`, `manifest`, and `phabricator`. |
-| `invisible_captcha_enabled`              | boolean          | no                                   | Enable Invisible Captcha spam detection during sign-up. Disabled by default. |
+| `invisible_captcha_enabled`              | boolean          | no                                   | <!-- vale gitlab.Spelling = NO --> Enable Invisible Captcha <!-- vale gitlab.Spelling = YES --> spam detection during sign-up. Disabled by default. |
 | `issues_create_limit`                    | integer          | no                                   | Max number of issue creation requests per minute per user. Disabled by default.|
 | `local_markdown_version`                 | integer          | no                                   | Increase this value when any cached Markdown should be invalidated. |
 | `maintenance_mode_message`               | string           | no                                   | **(PREMIUM)** Message displayed when instance is in maintenance mode |
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index 09ca3bb18ea..750ecd91085 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -6,7 +6,9 @@ type: reference
 ---
 
 <!-- markdownlint-disable MD044 -->
+<!-- vale gitlab.Spelling = NO -->
 # Keyword reference for the .gitlab-ci.yml file
+<!-- vale gitlab.Spelling = YES -->
 <!-- markdownlint-enable MD044 -->
 
 This document lists the configuration options for your GitLab `.gitlab-ci.yml` file.
@@ -1403,7 +1405,7 @@ job:
         - spec/**.rb
 ```
 
-Glob patterns are interpreted with Ruby [File.fnmatch](https://docs.ruby-lang.org/en/2.7.0/File.html#method-c-fnmatch)
+Glob patterns are interpreted with Ruby [`File.fnmatch`](https://docs.ruby-lang.org/en/2.7.0/File.html#method-c-fnmatch)
 with the flags `File::FNM_PATHNAME | File::FNM_DOTMATCH | File::FNM_EXTGLOB`.
 
 For performance reasons, GitLab matches a maximum of 10,000 `exists` patterns. After the 10,000th check, rules with patterned globs always match.
diff --git a/doc/development/cicd/index.md b/doc/development/cicd/index.md
index 196b6461f72..d79d681263d 100644
--- a/doc/development/cicd/index.md
+++ b/doc/development/cicd/index.md
@@ -146,7 +146,7 @@ As we increase the number of runners in the pool we also increase the chances of
 
 ## The definition of "Job" in GitLab CI/CD
 
-"Job" in GitLab CI context refers a task to drive Continuous Integartion, Delivery and Deployment.
+"Job" in GitLab CI context refers a task to drive Continuous Integration, Delivery and Deployment.
 Typically, a pipeline contains multiple stages, and a stage contains multiple jobs.
 
 In Active Record modeling, Job is defined as `CommitStatus` class.
@@ -164,4 +164,4 @@ we should use "Job" in general, instead of "Build".
 
 We have a few inconsistencies in our codebase that should be refactored.
 For example, `CommitStatus` should be `Ci::Job` and `Ci::JobArtifact` should be `Ci::BuildArtifact`.
-Please read [this isse](https://gitlab.com/gitlab-org/gitlab/-/issues/16111) for the full refactoring plan.
+See [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/16111) for the full refactoring plan.
diff --git a/doc/development/database/strings_and_the_text_data_type.md b/doc/development/database/strings_and_the_text_data_type.md
index 703118b23d2..f338520c6ca 100644
--- a/doc/development/database/strings_and_the_text_data_type.md
+++ b/doc/development/database/strings_and_the_text_data_type.md
@@ -36,7 +36,7 @@ validations and index creation while it allows reads and writes).
 
 ### Exceptions
 
-Text columns used by `attr_encrypted` are not required to have a limit, becuase the length of the
+Text columns used by `attr_encrypted` are not required to have a limit, because the length of the
 text after encryption may be longer than the text itself. Instead, you can use an Active Record
 length validation on the attribute.
 
diff --git a/doc/development/ee_features.md b/doc/development/ee_features.md
index c1d77abf08e..81014b7624c 100644
--- a/doc/development/ee_features.md
+++ b/doc/development/ee_features.md
@@ -166,9 +166,9 @@ still having access the class's implementation with `super`.
 There are a few gotchas with it:
 
 - you should always [`extend ::Gitlab::Utils::Override`](utilities.md#override) and use `override` to
-  guard the "overrider" method to ensure that if the method gets renamed in
+  guard the `overrider` method to ensure that if the method gets renamed in
   CE, the EE override isn't silently forgotten.
-- when the "overrider" would add a line in the middle of the CE
+- when the `overrider` would add a line in the middle of the CE
   implementation, you should refactor the CE method and split it in
   smaller methods. Or create a "hook" method that is empty in CE,
   and with the EE-specific implementation in EE.
@@ -971,7 +971,7 @@ information on managing page-specific JavaScript within EE.
 
 #### Child Component only used in EE
 
-To separate Vue template differences we should [async import the components](https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components).
+To separate Vue template differences we should [import the components asynchronously](https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components).
 
 Doing this allows for us to load the correct component in EE while in CE
 we can load a empty component that renders nothing. This code **should**
@@ -1068,7 +1068,7 @@ export default {
 **For EE components that need different results for the same computed values, we can pass in props to the CE wrapper as seen in the example.**
 
 - **EE Child components**
-  - Since we are using the async loading to check which component to load, we'd still use the component's name, check [this example](#child-component-only-used-in-ee).
+  - Since we are using the asynchronous loading to check which component to load, we'd still use the component's name, check [this example](#child-component-only-used-in-ee).
 
 - **EE extra HTML**
   - For the templates that have extra HTML in EE we should move it into a new component and use the `ee_else_ce` dynamic import
diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md
index e5d0bd7ee10..10fa331e1dd 100644
--- a/doc/development/elasticsearch.md
+++ b/doc/development/elasticsearch.md
@@ -210,7 +210,7 @@ class MigrationName < Elastic::Migration
 end
 ```
 
-Applied migrations are stored in `gitlab-#{RAILS_ENV}-migrations` index. All unexecuted migrations
+Applied migrations are stored in `gitlab-#{RAILS_ENV}-migrations` index. All migrations not executed
 are applied by the [`Elastic::MigrationWorker`](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/app/workers/elastic/migration_worker.rb)
 cron worker sequentially.
 
diff --git a/doc/development/experiment_guide/index.md b/doc/development/experiment_guide/index.md
index 2b0fd3ccc54..5d77c0ca0e9 100644
--- a/doc/development/experiment_guide/index.md
+++ b/doc/development/experiment_guide/index.md
@@ -44,7 +44,7 @@ addressed.
 > - It is not yet intended for use in GitLab self-managed instances.
 
 [GitLab Experiment](https://gitlab.com/gitlab-org/gitlab-experiment/) is a gem included
-in GitLab that can be used for running experiments. 
+in GitLab that can be used for running experiments.
 
 ## How to create an A/B test using `experimentation.rb`
 
@@ -368,7 +368,7 @@ Use a comma to list more than one experiment to be forced:
 document.cookie = "force_experiment=<EXPERIMENT_KEY>,<ANOTHER_EXPERIMENT_KEY>; path=/";
 ```
 
-Clear the experiments by unsetting the `force_experiment` cookie:
+To clear the experiments, unset the `force_experiment` cookie:
 
 ```javascript
 document.cookie = "force_experiment=; path=/";
diff --git a/doc/development/fe_guide/graphql.md b/doc/development/fe_guide/graphql.md
index 40ed5b383b6..a53d9fee029 100644
--- a/doc/development/fe_guide/graphql.md
+++ b/doc/development/fe_guide/graphql.md
@@ -18,6 +18,8 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo
 
 **GraphQL at GitLab**:
 
+<!-- vale gitlab.Spelling = NO -->
+
 - <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> [GitLab Unfiltered GraphQL playlist](https://www.youtube.com/watch?v=wHPKZBDMfxE&list=PL05JrBw4t0KpcjeHjaRMB7IGB2oDWyJzv)
 - <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> [GraphQL at GitLab: Deep Dive](../api_graphql_styleguide.md#deep-dive) (video) by Nick Thomas
   - An overview of the history of GraphQL at GitLab (not frontend-specific)
@@ -29,6 +31,8 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo
 - [🛠 Vuex -> Apollo Migration: a proof-of-concept project](https://gitlab.com/ntepluhina/vuex-to-apollo/blob/master/README.md)
   - A collection of examples that show the possible approaches for state management with Vue+GraphQL+(Vuex or Apollo) apps
 
+<!-- vale gitlab.Spelling = YES -->
+
 ### Libraries
 
 We use [Apollo](https://www.apollographql.com/) (specifically [Apollo Client](https://www.apollographql.com/docs/react/)) and [Vue Apollo](https://github.com/vuejs/vue-apollo)
@@ -39,13 +43,21 @@ can help you learn how to integrate Vue Apollo.
 
 For other use cases, check out the [Usage outside of Vue](#usage-outside-of-vue) section.
 
+<!-- vale gitlab.Spelling = NO -->
+
 We use [Immer](https://immerjs.github.io/immer/docs/introduction) for immutable cache updates;
 see [Immutability and cache updates](#immutability-and-cache-updates) for more information.
 
+<!-- vale gitlab.Spelling = YES -->
+
 ### Tooling
 
+<!-- vale gitlab.Spelling = NO -->
+
 - [Apollo Client Devtools](https://github.com/apollographql/apollo-client-devtools)
 
+<!-- vale gitlab.Spelling = YES -->
+
 #### [Apollo GraphQL VS Code extension](https://marketplace.visualstudio.com/items?itemName=apollographql.vscode-apollo)
 
 If you use VS Code, the Apollo GraphQL extension supports autocompletion in `.graphql` files. To set up
@@ -160,9 +172,14 @@ const primaryKeyId = getIdFromGraphQLId(data.id);
 From Apollo version 3.0.0 all the cache updates need to be immutable. It needs to be replaced entirely
 with a **new and updated** object.
 
-To facilitate the process of updating the cache and returning the new object we use the library [Immer](https://immerjs.github.io/immer/docs/introduction).
+<!-- vale gitlab.Spelling = NO -->
+
+To facilitate the process of updating the cache and returning the new object we
+use the library [Immer](https://immerjs.github.io/immer/docs/introduction).
 When possible, follow these conventions:
 
+<!-- vale gitlab.Spelling = YES -->
+
 - The updated cache is named `data`.
 - The original cache data is named `sourceData`.
 
@@ -753,9 +770,13 @@ export default {
 
 #### Mocking response as component data
 
-With [Vue test utils](https://vue-test-utils.vuejs.org/) one can quickly test components that
+<!-- vale gitlab.Spelling = NO -->
+
+With [Vue Test Utils](https://vue-test-utils.vuejs.org/) one can quickly test components that
 fetch GraphQL queries. The simplest way is to use `shallowMount` and then set
-the data on the component
+the data on the component:
+
+<!-- vale gitlab.Spelling = YES -->
 
 ```javascript
 it('tests apollo component', () => {
diff --git a/doc/development/fe_guide/icons.md b/doc/development/fe_guide/icons.md
index 852de1f98b8..821334e3008 100644
--- a/doc/development/fe_guide/icons.md
+++ b/doc/development/fe_guide/icons.md
@@ -26,12 +26,16 @@ To use a sprite Icon in HAML or Rails we use a specific helper function:
 sprite_icon(icon_name, size: nil, css_class: '')
 ```
 
+<!-- vale gitlab.Spelling = NO -->
+
 - **icon_name**: Use the icon_name for the SVG sprite in the list of
   ([GitLab SVGs](https://gitlab-org.gitlab.io/gitlab-svgs)).
 - **size (optional)**: Use one of the following sizes : 16, 24, 32, 48, 72 (this
   is translated into a `s16` class)
 - **css_class (optional)**: If you want to add additional CSS classes.
 
+<!-- vale gitlab.Spelling = YES -->
+
 **Example**
 
 ```haml
diff --git a/doc/development/fe_guide/performance.md b/doc/development/fe_guide/performance.md
index 7d249c65ebd..2a1c3daa6b8 100644
--- a/doc/development/fe_guide/performance.md
+++ b/doc/development/fe_guide/performance.md
@@ -202,15 +202,15 @@ help identify marks and measures coming from the different apps on the same page
 
 ## Best Practices
 
-### Realtime Components
+### Real-time Components
 
-When writing code for realtime features we have to keep a couple of things in mind:
+When writing code for real-time features we have to keep a couple of things in mind:
 
 1. Do not overload the server with requests.
-1. It should feel realtime.
+1. It should feel real-time.
 
-Thus, we must strike a balance between sending requests and the feeling of realtime.
-Use the following rules when creating realtime solutions.
+Thus, we must strike a balance between sending requests and the feeling of real-time.
+Use the following rules when creating real-time solutions.
 
 1. The server tells you how much to poll by sending `Poll-Interval` in the header.
    Use that as your polling interval. This enables system administrators to change the
@@ -221,7 +221,7 @@ Use the following rules when creating realtime solutions.
 1. Poll on active tabs only. Please use [Visibility](https://github.com/ai/visibilityjs).
 1. Use regular polling intervals, do not use backoff polling, or jitter, as the interval is
    controlled by the server.
-1. The backend code is likely to be using etags. You do not and should not check for status
+1. The backend code is likely to be using ETags. You do not and should not check for status
    `304 Not Modified`. The browser transforms it for you.
 
 ### Lazy Loading Images
@@ -333,7 +333,7 @@ browser's developer console from any page in GitLab.
       action();
     ```
 
-  For example, see how we use this in [app/assets/javascripts/pages/projects/graphs/charts/index.js](https://gitlab.com/gitlab-org/gitlab/-/commit/5e90885d6afd4497002df55bf015b338efcfc3c5#02e81de37f5b1716a3ef3222fa7f7edf22c40969_9_8):
+  For example, see how we use this in [`app/assets/javascripts/pages/projects/graphs/charts/index.js`](https://gitlab.com/gitlab-org/gitlab/-/commit/5e90885d6afd4497002df55bf015b338efcfc3c5#02e81de37f5b1716a3ef3222fa7f7edf22c40969_9_8):
 
   ```javascript
   waitForCSSLoaded(() => {
diff --git a/doc/development/fe_guide/troubleshooting.md b/doc/development/fe_guide/troubleshooting.md
index 641bbdcbd8d..abaf9cd68c7 100644
--- a/doc/development/fe_guide/troubleshooting.md
+++ b/doc/development/fe_guide/troubleshooting.md
@@ -12,7 +12,7 @@ Running into a problem? Maybe this will help ¯\＿(ツ)＿/¯.
 
 ### This guide doesn't contain the issue I ran into
 
-If you run into a Frontend development issue that is not in this guide, please consider updating this guide with your issue and possible remedies. This way future adventurers can face these dragons with more success, being armed with your experience and knowedge.
+If you run into a Frontend development issue that is not in this guide, please consider updating this guide with your issue and possible remedies. This way future adventurers can face these dragons with more success, being armed with your experience and knowledge.
 
 ## Testing issues
 
diff --git a/doc/development/polling.md b/doc/development/polling.md
index 18f9fb954dd..f854891a528 100644
--- a/doc/development/polling.md
+++ b/doc/development/polling.md
@@ -60,6 +60,6 @@ route matching easier.
 
 For more information see:
 
-- [`Poll-Interval` header](fe_guide/performance.md#realtime-components)
+- [`Poll-Interval` header](fe_guide/performance.md#real-time-components)
 - [RFC 7232](https://tools.ietf.org/html/rfc7232)
 - [ETag proposal](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26926)
diff --git a/doc/development/reactive_caching.md b/doc/development/reactive_caching.md
index 1b8a3f91086..0223f5d91d6 100644
--- a/doc/development/reactive_caching.md
+++ b/doc/development/reactive_caching.md
@@ -103,7 +103,7 @@ not wait until the background worker completes.
 - An API that calls a model or service method that uses `ReactiveCaching` should return
   `202 accepted` when the cache is being calculated (when `#with_reactive_cache` returns `nil`).
 - It should also
-  [set the polling interval header](fe_guide/performance.md#realtime-components) with
+  [set the polling interval header](fe_guide/performance.md#real-time-components) with
   `Gitlab::PollingInterval.set_header`.
 - The consumer of the API is expected to poll the API.
 - You can also consider implementing [ETag caching](polling.md) to reduce the server
diff --git a/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md b/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
index 50dabfaaec4..8a929737ebe 100644
--- a/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
+++ b/doc/development/testing_guide/end_to_end/rspec_metadata_tests.md
@@ -41,5 +41,5 @@ This is a partial list of the [RSpec metadata](https://relishapp.com/rspec/rspec
 | `:skip_signup_disabled` | The test uses UI to sign up a new user and is skipped in any environment that does not allow new user registration via the UI. |
 | `:smoke`          | The test belongs to the test suite which verifies basic functionality of a GitLab instance.|
 | `:smtp`           | The test requires a GitLab instance to be configured to use an SMTP server. Tests SMTP notification email delivery from GitLab by using MailHog. |
-| `:testcase`       | The link to the test case issue in the [Quality Testcases project](https://gitlab.com/gitlab-org/quality/testcases/). |
+| `:testcase`       | The link to the test case issue in the [Quality Test Cases project](https://gitlab.com/gitlab-org/quality/testcases/). |
 | `:transient`      | The test tests transient bugs. It is excluded by default. |
diff --git a/doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md b/doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md
index 4dd19a524a9..3c319e221fb 100644
--- a/doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md
+++ b/doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md
@@ -78,7 +78,7 @@ CONTAINER ID   ...     PORTS                                    NAMES
 d15d3386a0a8   ...     22/tcp, 443/tcp, 0.0.0.0:32772->80/tcp   gitlab-gitaly-ha
 ```
 
-That shows that the GitLab instance running in the `gitlab-gitaly-ha` container can be reached via `http://localhost:32772`. However, Git operations like cloning and pushing are performed against the URL revealed via the UI as the clone URL. It uses the hostname configured for the GitLab instance, which in this case matches the Docker container name and network, `gitlab-gitaly-ha.test`. Before you can run the tests you need to configure your computer to access the container via that address. One option is to [use caddyserver as described for running tests against GDK](https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/docs/run_qa_against_gdk.md#workarounds).
+That shows that the GitLab instance running in the `gitlab-gitaly-ha` container can be reached via `http://localhost:32772`. However, Git operations like cloning and pushing are performed against the URL revealed via the UI as the clone URL. It uses the hostname configured for the GitLab instance, which in this case matches the Docker container name and network, `gitlab-gitaly-ha.test`. Before you can run the tests you need to configure your computer to access the container via that address. One option is to [use Caddy server as described for running tests against GDK](https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/docs/run_qa_against_gdk.md#workarounds).
 
 Another option is to use NGINX.
 
diff --git a/doc/development/testing_guide/frontend_testing.md b/doc/development/testing_guide/frontend_testing.md
index 81b4689c521..7e7f62e41dd 100644
--- a/doc/development/testing_guide/frontend_testing.md
+++ b/doc/development/testing_guide/frontend_testing.md
@@ -258,7 +258,7 @@ it('exists', () => {
 ### Naming unit tests
 
 When writing describe test blocks to test specific functions/methods,
-please use the method name as the describe block name.
+use the method name as the describe block name.
 
 **Bad**:
 
@@ -439,7 +439,7 @@ it('waits for an Ajax call', done => {
 });
 ```
 
-If you are not able to register handlers to the `Promise`, for example because it is executed in a synchronous Vue life cycle hook, please take a look at the [waitFor](#wait-until-axios-requests-finish) helpers or you can flush all pending `Promise`s:
+If you are not able to register handlers to the `Promise`, for example because it is executed in a synchronous Vue life cycle hook, take a look at the [waitFor](#wait-until-axios-requests-finish) helpers or you can flush all pending `Promise`s:
 
 **in Jest:**
 
@@ -702,10 +702,10 @@ unit testing by mocking out modules which cannot be easily consumed in our test
 Jest supports [manual module mocks](https://jestjs.io/docs/en/manual-mocks) by placing a mock in a `__mocks__/` directory next to the source module
 (e.g. `app/assets/javascripts/ide/__mocks__`). **Don't do this.** We want to keep all of our test-related code in one place (the `spec/` folder).
 
-If a manual mock is needed for a `node_modules` package, please use the `spec/frontend/__mocks__` folder. Here's an example of
+If a manual mock is needed for a `node_modules` package, use the `spec/frontend/__mocks__` folder. Here's an example of
 a [Jest mock for the package `monaco-editor`](https://gitlab.com/gitlab-org/gitlab/blob/b7f914cddec9fc5971238cdf12766e79fa1629d7/spec/frontend/__mocks__/monaco-editor/index.js#L1).
 
-If a manual mock is needed for a CE module, please place it in `spec/frontend/mocks/ce`.
+If a manual mock is needed for a CE module, place it in `spec/frontend/mocks/ce`.
 
 - Files in `spec/frontend/mocks/ce` mocks the corresponding CE module from `app/assets/javascripts`, mirroring the source module's path.
   - Example: `spec/frontend/mocks/ce/lib/utils/axios_utils` mocks the module `~/lib/utils/axios_utils`.
@@ -728,11 +728,11 @@ If a manual mock is needed for a CE module, please place it in `spec/frontend/mo
 Global mocks introduce magic and technically can reduce test coverage. When mocking is deemed profitable:
 
 - Keep the mock short and focused.
-- Please leave a top-level comment in the mock on why it is necessary.
+- Leave a top-level comment in the mock on why it is necessary.
 
 ### Additional mocking techniques
 
-Please consult the [official Jest docs](https://jestjs.io/docs/en/jest-object#mock-modules) for a full overview of the available mocking features.
+Consult the [official Jest docs](https://jestjs.io/docs/en/jest-object#mock-modules) for a full overview of the available mocking features.
 
 ## Running Frontend Tests
 
@@ -865,7 +865,7 @@ end
 This will create a new fixture located at
 `tmp/tests/frontend/fixtures-ee/graphql/releases/queries/all_releases.query.graphql.json`.
 
-Note that you will need to provide the paths to all fragments used by the query.
+You will need to provide the paths to all fragments used by the query.
 `get_graphql_query_as_string` reads all of the provided file paths and returns
 the result as a single, concatenated string.
 
@@ -929,7 +929,8 @@ it.each([
 );
 ```
 
-**Note**: only use template literal block if pretty print is **not** needed for spec output. For example, empty strings, nested objects etc.
+NOTE:
+Only use template literal block if pretty print is not needed for spec output. For example, empty strings, nested objects etc.
 
 For example, when testing the difference between an empty search string and a non-empty search string, the use of the array block syntax with the pretty print option would be preferred. That way the differences between an empty string e.g. `''` and a non-empty string e.g. `'search string'` would be visible in the spec output. Whereas with a template literal block, the empty string would be shown as a space, which could lead to a confusing developer experience
 
@@ -1038,7 +1039,8 @@ import Subject from '~/feature/the_subject.vue';
 import _Thing from '~/feature/path/to/thing.vue';
 ```
 
-**PLEASE NOTE:** Do not simply disregard test timeouts. This could be a sign that there's
+NOTE:
+Do not disregard test timeouts. This could be a sign that there's
 actually a production problem. Use this opportunity to analyze the production webpack bundles and
 chunks and confirm that there is not a production issue with the async imports.
 
@@ -1063,7 +1065,7 @@ See also [Notes on testing Vue components](../fe_guide/vue.md#testing-vue-compon
 ## Test helpers
 
 Test helpers can be found in [`spec/frontend/__helpers__`](https://gitlab.com/gitlab-org/gitlab/blob/master/spec/frontend/__helpers__).
-If you introduce new helpers, please place them in that directory.  
+If you introduce new helpers, place them in that directory.
 
 ### Vuex Helper: `testAction`
 
diff --git a/doc/development/testing_guide/index.md b/doc/development/testing_guide/index.md
index 68326879dd0..c22a4e0b3ad 100644
--- a/doc/development/testing_guide/index.md
+++ b/doc/development/testing_guide/index.md
@@ -9,9 +9,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 This document describes various guidelines and best practices for automated
 testing of the GitLab project.
 
-It is meant to be an _extension_ of the [thoughtbot testing
+It is meant to be an _extension_ of the [Thoughtbot testing
 style guide](https://github.com/thoughtbot/guides/tree/master/testing-rspec). If
-this guide defines a rule that contradicts the thoughtbot guide, this guide
+this guide defines a rule that contradicts the Thoughtbot guide, this guide
 takes precedence. Some guidelines may be repeated verbatim to stress their
 importance.
 
diff --git a/doc/development/testing_guide/review_apps.md b/doc/development/testing_guide/review_apps.md
index 6e37b947767..f1c74f990cb 100644
--- a/doc/development/testing_guide/review_apps.md
+++ b/doc/development/testing_guide/review_apps.md
@@ -357,7 +357,7 @@ using `v232`.
 
 For the record, the debugging steps to find out this issue were:
 
-1. Switch kubectl context to review-apps-ce (we recommend using [kubectx](https://github.com/ahmetb/kubectx/))
+1. Switch kubectl context to `review-apps-ce` (we recommend using [`kubectx`](https://github.com/ahmetb/kubectx/))
 1. `kubectl get pods | grep dns`
 1. `kubectl describe pod <pod name>` & confirm exact error message
 1. Web search for exact error message, following rabbit hole to [a relevant Kubernetes bug report](https://github.com/kubernetes/kubernetes/issues/57345)
diff --git a/doc/development/testing_guide/testing_migrations_guide.md b/doc/development/testing_guide/testing_migrations_guide.md
index 31054d0ffb2..d54ca0d3c64 100644
--- a/doc/development/testing_guide/testing_migrations_guide.md
+++ b/doc/development/testing_guide/testing_migrations_guide.md
@@ -32,7 +32,7 @@ migrate the database **down** to the previous migration version.
 
 With this approach you can test a migration against a database schema.
 
-An `after` hook migrates the database **up** and reinstitutes the latest
+An `after` hook migrates the database **up** and restores the latest
 schema version, so that the process does not affect subsequent specs and
 ensures proper isolation.
 
diff --git a/doc/development/windows.md b/doc/development/windows.md
index 08ff29a4e58..07f8a80e95f 100644
--- a/doc/development/windows.md
+++ b/doc/development/windows.md
@@ -63,7 +63,7 @@ Build a Google Cloud image with the above shared runners repository by doing the
 
 ## How to use a Windows image in GCP
 
-1. In a web browser, go to <https://console.cloud.google.com/compute/images>.
+1. In a web browser, go to the [Google Cloud Platform console](https://console.cloud.google.com/compute/images).
 1. Filter images by the name you used when creating image, `windows` is likely all you need to filter by.
 1. Click the image's name.
 1. Click the **CREATE INSTANCE** link.
@@ -81,7 +81,7 @@ Build a Google Cloud image with the above shared runners repository by doing the
 1. Click **Continue** to accept the certificate.
 1. Enter the password and click **Next**.
 
-You should now be remoted into a Windows machine with a command prompt.
+You should now be connected into a Windows machine with a command prompt.
 
 ### Optional: Use GCP VM Instance as a runner
 
diff --git a/doc/integration/security_partners/index.md b/doc/integration/security_partners/index.md
index 87307ec15ea..1053c612782 100644
--- a/doc/integration/security_partners/index.md
+++ b/doc/integration/security_partners/index.md
@@ -10,4 +10,8 @@ type: index
 You can integrate GitLab with its security partners. This page has information on how do this with
 each security partner:
 
+<!-- vale gitlab.Spelling = NO -->
+
 - [Anchore](https://docs.anchore.com/current/docs/using/integration/ci_cd/gitlab/)
+
+<!-- vale gitlab.Spelling = YES -->
diff --git a/doc/operations/metrics/dashboards/yaml.md b/doc/operations/metrics/dashboards/yaml.md
index 536757f5fe0..138d9b28c76 100644
--- a/doc/operations/metrics/dashboards/yaml.md
+++ b/doc/operations/metrics/dashboards/yaml.md
@@ -133,7 +133,7 @@ metrics:
     unit: 'count'
 ```
 
-This works by lowercasing the value of `label` and, if there are more words separated by spaces, replacing those spaces with an underscore (`_`). The transformed value is then checked against the labels of the time series returned by the Prometheus query. If a time series label is found that is equal to the transformed value, then the label value renders in the legend like this:
+This works by converting the value of `label` to lower-case and, if there are more words separated by spaces, replacing those spaces with an underscore (`_`). The transformed value is then checked against the labels of the time series returned by the Prometheus query. If a time series label is found that is equal to the transformed value, then the label value renders in the legend like this:
 
 ![legend with label shorthand variable](img/prometheus_dashboard_label_variable_shorthand.png)
 
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md
index 0b8a1b961ea..24b1c7a6978 100644
--- a/doc/raketasks/backup_restore.md
+++ b/doc/raketasks/backup_restore.md
@@ -240,7 +240,7 @@ The resulting file is named `dump_gitlab_backup.tar`. This is useful for
 systems that make use of rsync and incremental backups, and results in
 considerably faster transfer speeds.
 
-#### Rsyncable
+#### Confirm archive can be transferred
 
 To ensure the generated archive is transferable by rsync, you can set the `GZIP_RSYNCABLE=yes`
 option. This sets the `--rsyncable` option to `gzip`, which is useful only in
@@ -1204,9 +1204,9 @@ and the jobs begin running again.
 
 Use the information in the following sections at your own risk.
 
-#### Check for undecryptable values
+#### Verify that all values can be decrypted
 
-You can determine if you have undecryptable values in the database by using the
+You can determine if your database contains values that can't be decrypted by using the
 [Secrets Doctor Rake task](../administration/raketasks/doctor.md).
 
 #### Take a backup
diff --git a/doc/security/password_storage.md b/doc/security/password_storage.md
index ca39defe6b9..af4b57e342a 100644
--- a/doc/security/password_storage.md
+++ b/doc/security/password_storage.md
@@ -11,6 +11,6 @@ GitLab stores user passwords in a hashed format, to prevent passwords from being
 
 GitLab uses the [Devise](https://github.com/heartcombo/devise) authentication library, which handles the hashing of user passwords. Password hashes are created with the following attributes:
 
-- **Hashing**: the [bcrypt](https://en.wikipedia.org/wiki/Bcrypt) hashing function is used to generate the hash of the provided password. This is a strong, industry-standard cryptographic hashing function.
+- **Hashing**: the [`bcrypt`](https://en.wikipedia.org/wiki/Bcrypt) hashing function is used to generate the hash of the provided password. This is a strong, industry-standard cryptographic hashing function.
 - **Stretching**: Password hashes are [stretched](https://en.wikipedia.org/wiki/Key_stretching) to harden against brute-force attacks. GitLab uses a stretching factor of 10 by default.
 - **Salting**: A [cryptographic salt](https://en.wikipedia.org/wiki/Salt_(cryptography)) is added to each password to harden against pre-computed hash and dictionary attacks. Each salt is randomly generated for each password, so that no two passwords share a salt, to further increase security.
diff --git a/doc/ssh/README.md b/doc/ssh/README.md
index f34e38fb7ca..f3fa7dd6033 100644
--- a/doc/ssh/README.md
+++ b/doc/ssh/README.md
@@ -201,7 +201,7 @@ Now you can copy the SSH key you created to your GitLab account. To do so, follo
    pbcopy < ~/.ssh/id_ed25519.pub
    ```
 
-   **Linux (requires the xclip package):**
+   **Linux (requires the `xclip` package):**
 
    ```shell
    xclip -sel clip < ~/.ssh/id_ed25519.pub
diff --git a/doc/topics/authentication/index.md b/doc/topics/authentication/index.md
index fd477a8a475..1988e3e2890 100644
--- a/doc/topics/authentication/index.md
+++ b/doc/topics/authentication/index.md
@@ -48,6 +48,10 @@ This page gathers all the resources for the topic **Authentication** within GitL
 
 ## Third-party resources
 
+<!-- vale gitlab.Spelling = NO -->
+
 - [Kanboard Plugin GitLab Authentication](https://github.com/kanboard/plugin-gitlab-auth)
 - [Jenkins GitLab OAuth Plugin](https://wiki.jenkins.io/display/JENKINS/GitLab+OAuth+Plugin)
 - [OKD - Configuring Authentication and User Agent](https://docs.okd.io/3.11/install_config/configuring_authentication.html#GitLab)
+
+<!-- vale gitlab.Spelling = YES -->
\ No newline at end of file
diff --git a/doc/user/project/integrations/img/mattermost_configuration.png b/doc/user/project/integrations/img/mattermost_configuration.png
deleted file mode 100644
index 18c0036846d..00000000000
--- a/doc/user/project/integrations/img/mattermost_configuration.png
+++ /dev/null
diff --git a/doc/user/project/integrations/img/mattermost_configuration_v2.png b/doc/user/project/integrations/img/mattermost_configuration_v2.png
new file mode 100644
index 00000000000..e05b34fd77a
--- /dev/null
+++ b/doc/user/project/integrations/img/mattermost_configuration_v2.png
diff --git a/doc/user/project/integrations/mattermost.md b/doc/user/project/integrations/mattermost.md
index 74dcce70cae..db190f47b01 100644
--- a/doc/user/project/integrations/mattermost.md
+++ b/doc/user/project/integrations/mattermost.md
@@ -59,5 +59,6 @@ At the end, fill in your Mattermost details:
 | **Username** | Optional username which can be on messages sent to Mattermost. Fill this in if you want to change the username of the bot. |
 | **Notify only broken pipelines** | If you choose to enable the **Pipeline** event and you want to be only notified about failed pipelines. |
 | **Branches to be notified** | Select which types of branches to send notifications for. |
+| **Labels to be notified** | Optional labels that the issue or merge request must have in order to trigger a notification. Leave blank to get all notifications. |
 
-![Mattermost configuration](img/mattermost_configuration.png)
+![Mattermost configuration](img/mattermost_configuration_v2.png)
diff --git a/doc/user/project/integrations/slack.md b/doc/user/project/integrations/slack.md
index 9e9f5b8297f..ab798675278 100644
--- a/doc/user/project/integrations/slack.md
+++ b/doc/user/project/integrations/slack.md
@@ -45,6 +45,7 @@ separately configured [Slack slash commands](slack_slash_commands.md).
 1. Select the **Notify only broken pipelines** check box to only notify on failures.
 1. In the **Branches to be notified** select box, choose which types of branches
    to send notifications for.
+1. Leave the **Labels to be notified** field blank to get all notifications or add labels that the issue or merge request must have in order to trigger a notification.
 1. Click **Test settings and save changes**.
 
 Your Slack team now starts receiving GitLab event notifications as configured.
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index bcc43c162af..27c2cb08d10 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -1221,7 +1221,7 @@ X-Gitlab-Event: Pipeline Hook
             "id": 380987,
             "description": "shared-runners-manager-6.gitlab.com",
             "active": true,
-            "is_shared": true, 
+            "is_shared": true,
             "tags": [
               "linux",
               "docker"
@@ -1485,6 +1485,74 @@ X-Gitlab-Event: Member Hook
 }
 ```
 
+### Subgroup events **(PREMIUM)**
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/260419) in GitLab 13.9.
+
+Subgroup events are triggered when:
+
+- A [subgroup is created in a group](#subgroup-created-in-a-group)
+- A [subgroup is removed from a group](#subgroup-removed-from-a-group)
+
+#### Subgroup created in a group
+
+**Request Header**:
+
+```plaintext
+X-Gitlab-Event: Subgroup Hook
+```
+
+**Request Body**:
+
+```json
+{
+
+  "created_at": "2021-01-20T09:40:12Z",
+  "updated_at": "2021-01-20T09:40:12Z",
+  "event_name": "subgroup_create",
+  "name": "subgroup1",
+  "path": "subgroup1",
+  "full_path": "group1/subgroup1",
+  "group_id": 10,
+  "parent_group_id": 7,
+  "parent_name": "group1",
+  "parent_path": "group1",
+  "parent_full_path": "group1"
+
+}
+```
+
+#### Subgroup removed from a group
+
+**Request Header**:
+
+```plaintext
+X-Gitlab-Event: Subgroup Hook
+```
+
+**Request Body**:
+
+```json
+{
+
+  "created_at": "2021-01-20T09:40:12Z",
+  "updated_at": "2021-01-20T09:40:12Z",
+  "event_name": "subgroup_destroy",
+  "name": "subgroup1",
+  "path": "subgroup1",
+  "full_path": "group1/subgroup1",
+  "group_id": 10,
+  "parent_group_id": 7,
+  "parent_name": "group1",
+  "parent_path": "group1",
+  "parent_full_path": "group1"
+
+}
+```
+
+NOTE:
+Webhooks for when a [subgroup is removed from a group](#subgroup-removed-from-a-group) are not triggered when a [subgroup is transferred to a new parent group](../../group/index.md#transferring-groups)
+
 ### Feature Flag events
 
 Triggered when a feature flag is turned on or off.
diff --git a/doc/user/project/members/img/access_requests_management_13_8.png b/doc/user/project/members/img/access_requests_management_13_8.png
deleted file mode 100644
index 950ef4dec01..00000000000
--- a/doc/user/project/members/img/access_requests_management_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/access_requests_management_v13_9.png b/doc/user/project/members/img/access_requests_management_v13_9.png
new file mode 100644
index 00000000000..b7883e9d134
--- /dev/null
+++ b/doc/user/project/members/img/access_requests_management_v13_9.png
diff --git a/doc/user/project/members/img/add_user_email_accept_13_8.png b/doc/user/project/members/img/add_user_email_accept_13_8.png
deleted file mode 100644
index ed980036af5..00000000000
--- a/doc/user/project/members/img/add_user_email_accept_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/add_user_email_accept_v13_9.png b/doc/user/project/members/img/add_user_email_accept_v13_9.png
new file mode 100644
index 00000000000..a6b303e05ca
--- /dev/null
+++ b/doc/user/project/members/img/add_user_email_accept_v13_9.png
diff --git a/doc/user/project/members/img/add_user_email_ready_13_8.png b/doc/user/project/members/img/add_user_email_ready_v13_8.png
index a610b46a176..a610b46a176 100644
--- a/doc/user/project/members/img/add_user_email_ready_13_8.png
+++ b/doc/user/project/members/img/add_user_email_ready_v13_8.png
diff --git a/doc/user/project/members/img/add_user_email_search_13_8.png b/doc/user/project/members/img/add_user_email_search_v13_8.png
index 934cf19bd3d..934cf19bd3d 100644
--- a/doc/user/project/members/img/add_user_email_search_13_8.png
+++ b/doc/user/project/members/img/add_user_email_search_v13_8.png
diff --git a/doc/user/project/members/img/add_user_give_permissions_13_8.png b/doc/user/project/members/img/add_user_give_permissions_v13_8.png
index 1916d056a52..1916d056a52 100644
--- a/doc/user/project/members/img/add_user_give_permissions_13_8.png
+++ b/doc/user/project/members/img/add_user_give_permissions_v13_8.png
diff --git a/doc/user/project/members/img/add_user_import_members_from_another_project_13_8.png b/doc/user/project/members/img/add_user_import_members_from_another_project_v13_8.png
index a6dddec3fb7..a6dddec3fb7 100644
--- a/doc/user/project/members/img/add_user_import_members_from_another_project_13_8.png
+++ b/doc/user/project/members/img/add_user_import_members_from_another_project_v13_8.png
diff --git a/doc/user/project/members/img/add_user_imported_members_13_8.png b/doc/user/project/members/img/add_user_imported_members_13_8.png
deleted file mode 100644
index 725e447604f..00000000000
--- a/doc/user/project/members/img/add_user_imported_members_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/add_user_imported_members_v13_9.png b/doc/user/project/members/img/add_user_imported_members_v13_9.png
new file mode 100644
index 00000000000..e40240df2b2
--- /dev/null
+++ b/doc/user/project/members/img/add_user_imported_members_v13_9.png
diff --git a/doc/user/project/members/img/add_user_list_members_13_8.png b/doc/user/project/members/img/add_user_list_members_13_8.png
deleted file mode 100644
index b8c0160c6d8..00000000000
--- a/doc/user/project/members/img/add_user_list_members_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/add_user_list_members_v13_9.png b/doc/user/project/members/img/add_user_list_members_v13_9.png
new file mode 100644
index 00000000000..7a07ea01d14
--- /dev/null
+++ b/doc/user/project/members/img/add_user_list_members_v13_9.png
diff --git a/doc/user/project/members/img/add_user_search_people_13_8.png b/doc/user/project/members/img/add_user_search_people_v13_8.png
index e9aa58512ab..e9aa58512ab 100644
--- a/doc/user/project/members/img/add_user_search_people_13_8.png
+++ b/doc/user/project/members/img/add_user_search_people_v13_8.png
diff --git a/doc/user/project/members/img/project_groups_tab_13_8.png b/doc/user/project/members/img/project_groups_tab_13_8.png
deleted file mode 100644
index 5d7948f0761..00000000000
--- a/doc/user/project/members/img/project_groups_tab_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/project_groups_tab_v13_9.png b/doc/user/project/members/img/project_groups_tab_v13_9.png
new file mode 100644
index 00000000000..d1b6a640341
--- /dev/null
+++ b/doc/user/project/members/img/project_groups_tab_v13_9.png
diff --git a/doc/user/project/members/img/project_members_13_8.png b/doc/user/project/members/img/project_members_13_8.png
deleted file mode 100644
index 9120d471b3b..00000000000
--- a/doc/user/project/members/img/project_members_13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/project_members_filter_direct_v13_9.png b/doc/user/project/members/img/project_members_filter_direct_v13_9.png
new file mode 100644
index 00000000000..50115ee4052
--- /dev/null
+++ b/doc/user/project/members/img/project_members_filter_direct_v13_9.png
diff --git a/doc/user/project/members/img/project_members_filter_inherited_v13_9.png b/doc/user/project/members/img/project_members_filter_inherited_v13_9.png
new file mode 100644
index 00000000000..433003fe58b
--- /dev/null
+++ b/doc/user/project/members/img/project_members_filter_inherited_v13_9.png
diff --git a/doc/user/project/members/img/project_members_search_v13_9.png b/doc/user/project/members/img/project_members_search_v13_9.png
new file mode 100644
index 00000000000..67280d11dca
--- /dev/null
+++ b/doc/user/project/members/img/project_members_search_v13_9.png
diff --git a/doc/user/project/members/img/project_members_sort_v13_9.png b/doc/user/project/members/img/project_members_sort_v13_9.png
new file mode 100644
index 00000000000..47abe18ba49
--- /dev/null
+++ b/doc/user/project/members/img/project_members_sort_v13_9.png
diff --git a/doc/user/project/members/img/project_members_v13_9.png b/doc/user/project/members/img/project_members_v13_9.png
new file mode 100644
index 00000000000..3b48c752c6a
--- /dev/null
+++ b/doc/user/project/members/img/project_members_v13_9.png
diff --git a/doc/user/project/members/img/share_project_with_groups_tab_v13_8.png b/doc/user/project/members/img/share_project_with_groups_tab_v13_8.png
deleted file mode 100644
index 6cbbb386396..00000000000
--- a/doc/user/project/members/img/share_project_with_groups_tab_v13_8.png
+++ /dev/null
diff --git a/doc/user/project/members/img/share_project_with_groups_tab_v13_9.png b/doc/user/project/members/img/share_project_with_groups_tab_v13_9.png
new file mode 100644
index 00000000000..99be996c03e
--- /dev/null
+++ b/doc/user/project/members/img/share_project_with_groups_tab_v13_9.png
diff --git a/doc/user/project/members/index.md b/doc/user/project/members/index.md
index cccb998fc31..00474098487 100644
--- a/doc/user/project/members/index.md
+++ b/doc/user/project/members/index.md
@@ -21,42 +21,74 @@ project's **Members**.
 When your project belongs to the group, group members inherit the membership and permission
 level for the project from the group.
 
-![Project members page](img/project_members_13_8.png)
+![Project members page](img/project_members_v13_9.png)
 
 From the image above, we can deduce the following things:
 
 - There are 3 members that have access to the project.
 - User0 is a Reporter and has inherited their permissions from group `demo`
   which contains current project.
-- For User1 there is no indication of a group, therefore they belong directly
+- User1 is shown as a **Direct member** in the **Source** column, therefore they belong directly
   to the project we're inspecting.
 - Administrator is the Owner and member of **all** groups and for that reason,
   there is an indication of an ancestor group and inherited Owner permissions.
 
-[From GitLab 12.6](https://gitlab.com/gitlab-org/gitlab/-/issues/21727), you can filter this list
-using the dropdown on the right side:
+## Filter and sort members
 
-![Project members filter](img/project_members_filter_v12_6.png)
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/21727) in GitLab 12.6.
+> - [Improved](https://gitlab.com/groups/gitlab-org/-/epics/4901) in GitLab 13.9.
+> - Improvements are [deployed behind a feature flag](../../feature_flags.md), enabled by default.
+> - Improvements are enabled on GitLab.com.
+> - Improvements are recommended for production use.
+> - For GitLab self-managed instances, GitLab administrators can opt to [disable improvements](#enable-or-disable-improvements-to-project-member-management). **(FREE SELF)**
 
-- **Show only direct members** displays only User1.
-- **Show only inherited members** displays User0 and Administrator.
+The following sections illustrate how you can filter and sort members in a project. To view these options,
+navigate to your desired project, go to **Members**, and include the noted search terms.
+
+### Membership filter
+
+By default, inherited and direct members are displayed. The membership filter can be used to display only inherited or only direct members.
+
+#### Display inherited members
+
+To display inherited members, include `Membership` `=` `Inherited` in the search text box.
+
+![Project members filter inherited](img/project_members_filter_inherited_v13_9.png)
+
+#### Display direct members
+
+To display direct members, include `Membership` `=` `Direct` in the search text box.
+
+![Project members filter direct](img/project_members_filter_direct_v13_9.png)
+
+### Search
+
+You can search for members by name, username, or email.
+
+![Project members search](img/project_members_search_v13_9.png)
+
+### Sort
+
+You can sort members by **Account**, **Access granted**, **Max role**, or **Last sign-in** in ascending or descending order.
+
+![Project members sort](img/project_members_sort_v13_9.png)
 
 ## Add a user
 
 Right next to **People**, start typing the name or username of the user you
 want to add.
 
-![Search for people](img/add_user_search_people_13_8.png)
+![Search for people](img/add_user_search_people_v13_8.png)
 
 Select the user and the [permission level](../../permissions.md)
 that you'd like to give the user. Note that you can select more than one user.
 
-![Give user permissions](img/add_user_give_permissions_13_8.png)
+![Give user permissions](img/add_user_give_permissions_v13_8.png)
 
 Once done, select **Add users to project** and they are immediately added to
 your project with the permissions you gave them above.
 
-![List members](img/add_user_list_members_13_8.png)
+![List members](img/add_user_list_members_v13_9.png)
 
 From there on, you can either remove an existing user or change their access
 level to the project.
@@ -68,14 +100,14 @@ You can import another project's users in your own project by hitting the
 
 In the dropdown menu, you can see only the projects you are Maintainer on.
 
-![Import members from another project](img/add_user_import_members_from_another_project_13_8.png)
+![Import members from another project](img/add_user_import_members_from_another_project_v13_8.png)
 
 Select the one you want and hit **Import project members**. A flash message
 displays, notifying you that the import was successful, and the new members
 are now in the project's members list. Notice that the permissions that they
 had on the project you imported from are retained.
 
-![Members list of new members](img/add_user_imported_members_13_8.png)
+![Members list of new members](img/add_user_imported_members_v13_9.png)
 
 ## Invite people using their e-mail address
 
@@ -83,18 +115,18 @@ If a user you want to give access to doesn't have an account on your GitLab
 instance, you can invite them just by typing their e-mail address in the
 user search field.
 
-![Invite user by mail](img/add_user_email_search_13_8.png)
+![Invite user by mail](img/add_user_email_search_v13_8.png)
 
 As you can imagine, you can mix inviting multiple people and adding existing
 GitLab users to the project.
 
-![Invite user by mail ready to submit](img/add_user_email_ready_13_8.png)
+![Invite user by mail ready to submit](img/add_user_email_ready_v13_8.png)
 
 Once done, hit **Add users to project** and watch that there is a new member
 with the e-mail address we used above. From there on, you can resend the
 invitation, change their access level, or even delete them.
 
-![Invite user members list](img/add_user_email_accept_13_8.png)
+![Invite user members list](img/add_user_email_accept_v13_9.png)
 
 While unaccepted, the system automatically sends reminder emails on the second, fifth,
 and tenth day after the invitation was initially sent.
@@ -130,7 +162,7 @@ NOTE:
 If a project does not have any maintainers, the notification is sent to the
 most recently active owners of the project's group.
 
-![Manage access requests](img/access_requests_management_13_8.png)
+![Manage access requests](img/access_requests_management_v13_9.png)
 
 If you change your mind before your request is approved, just click the
 **Withdraw Access Request** button.
@@ -167,3 +199,27 @@ To remove a member from a project:
    A **Remove member** modal appears.
 1. (Optional) Select the **Also unassign this user from related issues and merge requests** checkbox.
 1. Click **Remove member**.
+
+## Enable or disable improvements to project member management **(FREE SELF)**
+
+Project member management improvements are deployed behind a feature flag that is **enabled by default**.
+[GitLab administrators with access to the GitLab Rails console](../../../administration/feature_flags.md)
+can opt to disable the improvements.
+
+To disable them:
+
+```ruby
+# For the instance
+Feature.disable(:vue_project_members_list)
+# For a single project
+Feature.disable(:vue_project_members_list, Project.find(<project id>))
+```
+
+To enable them:
+
+```ruby
+# For the instance
+Feature.enable(:vue_project_members_list)
+# For a single project
+Feature.enable(:vue_project_members_list, Project.find(<project id>))
+```
diff --git a/doc/user/project/members/share_project_with_groups.md b/doc/user/project/members/share_project_with_groups.md
index d17717fb29c..7000988d9bf 100644
--- a/doc/user/project/members/share_project_with_groups.md
+++ b/doc/user/project/members/share_project_with_groups.md
@@ -26,7 +26,7 @@ To share 'Project Acme' with the 'Engineering' group:
 
 1. For 'Project Acme' use the left navigation menu to go to **Members**.
 
-   ![share project with groups](img/share_project_with_groups_tab_v13_8.png)
+   ![share project with groups](img/share_project_with_groups_tab_v13_9.png)
 
 1. Select the **Invite group** tab.
 1. Add the 'Engineering' group with the maximum access level of your choice.
@@ -35,7 +35,7 @@ To share 'Project Acme' with the 'Engineering' group:
 1. After sharing 'Project Acme' with 'Engineering':
    - The group is listed in the **Groups** tab.
 
-     !['Engineering' group is listed in Groups tab](img/project_groups_tab_13_8.png)
+     !['Engineering' group is listed in Groups tab](img/project_groups_tab_v13_9.png)
 
    - The project is listed on the group dashboard.
 
diff --git a/doc/user/shortcuts.md b/doc/user/shortcuts.md
index a8435424d62..014555cffed 100644
--- a/doc/user/shortcuts.md
+++ b/doc/user/shortcuts.md
@@ -35,7 +35,7 @@ These shortcuts are available in most areas of GitLab
 | <kbd>Shift</kbd> + <kbd>m</kbd> | Go to your Merge requests page.|
 | <kbd>Shift</kbd> + <kbd>t</kbd> | Go to your To-Do List page. |
 | <kbd>p</kbd> + <kbd>b</kbd>     | Show/hide the Performance Bar. |
-| <kbd>g</kbd> + <kbd>x</kbd>     | Toggle between [GitLab](https://gitlab.com/) and [GitLab Next](https://next.gitlab.com/). |
+| <kbd>g</kbd> + <kbd>x</kbd>     | Toggle between [GitLab](https://gitlab.com/) and [GitLab Next](https://next.gitlab.com/) (GitLab SaaS only). |
 
 Additionally, the following shortcuts are available when editing text in text fields,
 for example comments, replies, issue descriptions, and merge request descriptions: