Merge branch 'fix/doc-user-admin-area-not-owned' into 'master'

Doc Consistency: user/admin_area - not owned

See merge request gitlab-org/gitlab!72062

doc/user/admin_area/appearance.md

@@ -39,7 +39,7 @@ of the page to activate it in the GitLab instance.
 
 ## System header and footer messages
 
-> - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/55057) to GitLab Free in 11.9.
+> - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/55057) from GitLab Premium to GitLab Free in 11.9.
 
 You can add a small header message, a small footer message, or both, to the interface
 of your GitLab instance. These messages appear on all projects and pages of the

doc/user/admin_area/settings/external_authorization.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # External authorization control **(FREE SELF)**
 
-> - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27056) to GitLab Free in 11.10.
+> - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27056) from GitLab Premium to GitLab Free in 11.10.
 
 In highly controlled environments, it may be necessary for access policy to be
 controlled by an external service that permits access based on project

doc/user/admin_area/settings/floc.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Federated Learning of Cohorts (FLoC) **(FREE SELF)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60933) in GitLab Free 13.12.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60933) in GitLab 13.12.
 
 Federated Learning of Cohorts (FLoC) is a new feature of the Chrome browser.
 It works by categorizing users into different cohorts, so that

doc/user/admin_area/settings/protected_paths.md

@@ -41,7 +41,7 @@ try again.
 
 ## Configure using GitLab UI
 
-> Introduced in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31246).
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31246) in GitLab 12.4.
 
 Throttling of protected paths is enabled by default and can be disabled or
 customized on **Admin > Network > Protected Paths**, along with these options:

doc/user/admin_area/settings/sidekiq_job_limits.md

@@ -13,7 +13,6 @@ type: reference
 Redis. To avoid excessive memory for Redis, we:
 
 - Compress job arguments before storing them in Redis.
-arguments before storing them in Redis, and rejecting jobs that exceed
 - Reject jobs that exceed the specified threshold limit after compression.
 
 To access Sidekiq job size limits:
@@ -30,7 +29,6 @@ To access Sidekiq job size limits:
 |-------------------------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Limiting mode                             | Compress         | This mode compresses the jobs at the specified threshold and rejects them if they exceed the specified limit after compression.                                               |
 | Sidekiq job compression threshold (bytes) | 100 000 (100 KB) | When the size of arguments exceeds this threshold, they are compressed before being stored in Redis.                                                                          |
-| Sidekiq job size limit (bytes)            | 0                | The jobs exceeding this size after compression are rejected. This avoids excessive memory usage in Redis leading to instability. Setting it to 0 prevents rejecting jobs. |
+| Sidekiq job size limit (bytes)            | 0                | The jobs exceeding this size after compression are rejected. This avoids excessive memory usage in Redis leading to instability. Setting it to 0 prevents rejecting jobs.     |
 
-After changing these values, [restart
-Sidekiq](../../../administration/restart_gitlab.md).
+After changing these values, [restart Sidekiq](../../../administration/restart_gitlab.md).

doc/user/admin_area/settings/sign_up_restrictions.md

@@ -62,7 +62,7 @@ To enforce confirmation of the email address used for new sign ups:
 1. On the left sidebar, select **Settings > General**, and expand **Sign-up restrictions**.
 1. Select the **Enable email restrictions for sign ups** checkbox, then select **Save changes**.
 
-## User cap **(FREE SELF)**
+## User cap
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4315) in GitLab 13.7.
 > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/292600) in GitLab 13.9.

doc/user/admin_area/settings/third_party_offers.md

@@ -7,7 +7,7 @@ type: reference
 
 # Third-party offers **(FREE SELF)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20379) in GitLab Free 11.1.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20379) in GitLab 11.1.
 
 Within GitLab, we inform users of available third-party offers they might find valuable in order
 to enhance the development of their projects. An example is the Google Cloud Platform free credit

doc/user/admin_area/settings/usage_statistics.md

@@ -12,7 +12,7 @@ to perform various actions.
 
 All usage statistics are [opt-out](#enable-or-disable-usage-statistics).
 
-## Service Ping **(FREE SELF)**
+## Service Ping
 
 Service Ping is a process that collects and sends a weekly payload to GitLab Inc.
 For more information, see the [Service Ping guide](../../../development/service_ping/index.md).
@@ -23,7 +23,7 @@ When Service Ping is enabled, GitLab gathers data from other instances and
 enables certain [instance-level analytics features](../analytics/index.md)
 that are dependent on Service Ping.
 
-## Version check **(FREE SELF)**
+## Version check
 
 If enabled, version check informs you if a new version is available and the
 importance of it through a status. The status displays on the help pages (`/help`)

doc/user/admin_area/user_cohorts.md

@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Cohorts **(FREE)**
+# Cohorts **(FREE SELF)**
 
 You can analyze your users' GitLab activities over time.