Clean up warnings detected by the Vale Admin rule

Changes "admin" to "administration", "administrator", "administer", or "Admin Area" depending on the context to enforce standards.

Clean up warnings detected by the Vale Admin rule
Changes "admin" to "administration", "administrator", "administer", or "Admin Area" depending on the context to enforce standards.
ad555ae5 · Jonston Chan · Marcel Amirault · 68fa8cc6 · ad555ae5 · ad555ae5
--- a/doc/user/project/import/github.md
+++ b/doc/user/project/import/github.md
@@ -157,7 +157,7 @@ of the above are automatically configured. **(PREMIUM)**
 ## Improving the speed of imports on self-managed instances

 NOTE:
-Admin access to the GitLab server is required.
+Administrator access to the GitLab server is required.

 For large projects it may take a while to import all data. To reduce the time necessary, you can increase the number of
 Sidekiq workers that process the following queues:

--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -61,7 +61,7 @@ Docker pulls and pushes and re-run any CI pipelines to retrieve any build artifa

 ## Migrating from GitLab.com to self-managed GitLab

-The process is essentially the same as for [migrating from self-managed GitLab to GitLab.com](#migrating-from-self-managed-gitlab-to-gitlabcom). The main difference is that users can be created on the self-managed GitLab instance by an admin through the UI or the [users API](../../../api/users.md#user-creation).
+The process is essentially the same as for [migrating from self-managed GitLab to GitLab.com](#migrating-from-self-managed-gitlab-to-gitlabcom). The main difference is that users can be created on the self-managed GitLab instance by an administrator through the UI or the [users API](../../../api/users.md#user-creation).

 ## Migrating between two self-managed GitLab instances

@@ -73,4 +73,4 @@ then restore it on the new server.
 In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped),
 refer to the instructions in [Migrating from self-managed GitLab to GitLab.com](#migrating-from-self-managed-gitlab-to-gitlabcom).

-Additionally, you can migrate users using the [Users API](../../../api/users.md) with an admin user.
+Additionally, you can migrate users using the [Users API](../../../api/users.md) with an administrator user.
--- a/doc/user/project/import/perforce.md
+++ b/doc/user/project/import/perforce.md
@@ -35,7 +35,7 @@ Git:

 ## Why migrate

-Perforce Helix can be difficult to manage both from a user and an admin
+Perforce Helix can be difficult to manage both from a user and an administrator
 perspective. Migrating to Git/GitLab there is:

 - **No licensing costs**, Git is GPL while Perforce Helix is proprietary.

--- a/doc/user/project/integrations/hipchat.md
+++ b/doc/user/project/integrations/hipchat.md
@@ -19,7 +19,7 @@ HipChat v1 API (legacy) supports "API Auth Tokens" in the Group API menu. A v1
 token is allowed to send messages to *any* room.

 HipChat v2 API has tokens that are can be created using the Integrations tab
-in the Group or Room admin page. By design, these are lightweight tokens that
+in the Group or Room administration page. By design, these are lightweight tokens that
 allow GitLab to send messages only to *one* room.

 ### Complete these steps in HipChat

--- a/doc/user/project/integrations/mattermost.md
+++ b/doc/user/project/integrations/mattermost.md
@@ -19,7 +19,7 @@ To enable Mattermost integration you must create an incoming webhook integration
 1. Choose a display name, description and channel, those can be overridden on GitLab.
 1. Save it and copy the **Webhook URL** because we need this later for GitLab.

-Incoming Webhooks might be blocked on your Mattermost instance. Ask your Mattermost admin
+Incoming Webhooks might be blocked on your Mattermost instance. Ask your Mattermost administrator
 to enable it on:

 - **Mattermost System Console > Integrations > Integration Management** in Mattermost
@@ -27,7 +27,7 @@ to enable it on:
 - **Mattermost System Console > Integrations > Custom Integrations** in Mattermost
  versions 5.11 and earlier.

-Display name override is not enabled by default, you need to ask your admin to enable it on that same section.
+Display name override is not enabled by default, you need to ask your administrator to enable it on that same section.

 ## On GitLab


--- a/doc/user/project/integrations/mattermost_slash_commands.md
+++ b/doc/user/project/integrations/mattermost_slash_commands.md
@@ -43,7 +43,7 @@ preconfigured with the right settings.
 The first thing to do in Mattermost is to enable custom slash commands from
 the administrator console.

-1. Log in with an account that has admin privileges and navigate to the system
+1. Log in with an account that has administrator privileges and navigate to the system
   console.

   ![Mattermost go to console](img/mattermost_goto_console.png)

--- a/doc/user/project/issues/design_management.md
+++ b/doc/user/project/issues/design_management.md
@@ -37,7 +37,7 @@ to be enabled:

 Design Management also requires that projects are using
 [hashed storage](../../../administration/raketasks/storage.md#migrate-to-hashed-storage). Since
- GitLab 10.0, newly created projects use hashed storage by default. A GitLab admin can verify the storage type of a
+ GitLab 10.0, newly created projects use hashed storage by default. A GitLab administrator can verify the storage type of a
 project by navigating to **Admin Area > Projects** and then selecting the project in question.
 A project can be identified as hashed-stored if its *Gitaly relative path* contains `@hashed`.


--- a/doc/user/project/issues/managing_issues.md
+++ b/doc/user/project/issues/managing_issues.md
@@ -160,7 +160,7 @@ The "Move issue" button is at the bottom of the right-sidebar when viewing the i
 If you have advanced technical skills you can also bulk move all the issues from one project to another in the rails console. The below script will move all the issues from one project to another that are not in status **closed**.

 To access rails console run `sudo gitlab-rails console` on the GitLab server and run the below
-script. Please be sure to change **project**, **admin_user** and **target_project** to your values.
+script. Please be sure to change `project`, `admin_user`, and `target_project` to your values.
 We do also recommend [creating a backup](../../../raketasks/backup_restore.md#back-up-gitlab) before
 attempting any changes in the console.


--- a/doc/user/project/members/share_project_with_groups.md
+++ b/doc/user/project/members/share_project_with_groups.md
@@ -44,7 +44,7 @@ Note that you can only share a project with:
 - groups for which you have an explicitly defined membership
 - groups that contain a nested subgroup or project for which you have an explicitly defined role

-Admins are able to share projects with any group in the system.
+Administrators are able to share projects with any group in the system.

 ## Maximum access level


--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md
@@ -23,7 +23,7 @@ GitLab Pages site.

 Note that **how to** add DNS records depends on which server your domain
 is hosted on. Every control panel has its own place to do it. If you are
-not an admin of your domain, and don't have access to your registrar,
+not an administrator of your domain, and don't have access to your registrar,
 you'll need to ask for the technical support of your hosting service
 to do it for you.


--- a/doc/user/project/pages/index.md
+++ b/doc/user/project/pages/index.md
@@ -85,7 +85,7 @@ scripts that GitLab CI/CD runs to accomplish this task is created from a file na

 You can either use GitLab's [default domain for GitLab Pages websites](getting_started_part_one.md#gitlab-pages-default-domain-names),
 `*.gitlab.io`, or your own domain (`example.com`). In that case, you'll
-need admin access to your domain's registrar (or control panel) to set it up with Pages.
+need administrator access to your domain's registrar (or control panel) to set it up with Pages.

 The following diagrams show the workflows you might follow to get started with Pages.

@@ -103,7 +103,7 @@ To restrict access to your website, enable [GitLab Pages Access Control](pages_a

 If you're using a self-managed instance (Core, Starter, Premium, or Ultimate),
 your websites will be published on your own server, according to the
-[Pages admin settings](../../../administration/pages/index.md) chosen by your sysadmin,
+[Pages settings](../../../administration/pages/index.md) chosen by your sysadmin,
 who can make them public or internal.

 ## Pages examples

--- a/doc/user/project/protected_branches.md
+++ b/doc/user/project/protected_branches.md
@@ -22,7 +22,7 @@ By default, a protected branch does four simple things:
 - It prevents **anyone** from deleting the branch.

 NOTE:
-A GitLab admin is allowed to push to the protected branches.
+A GitLab administrator is allowed to push to the protected branches.

 See the [Changelog](#changelog) section for changes over time.


--- a/doc/user/project/repository/index.md
+++ b/doc/user/project/repository/index.md
@@ -189,7 +189,7 @@ updated every 15 minutes at most, so may not reflect recent activity. The displa

 The project size may differ slightly from one instance to another due to compression, housekeeping, and other factors.

-[Repository size limit](../../admin_area/settings/account_and_limit_settings.md) may be set by admins.
+[Repository size limit](../../admin_area/settings/account_and_limit_settings.md) may be set by administrators.
 GitLab.com's repository size limit [is set by GitLab](../../gitlab_com/index.md#account-and-limit-settings).

 ## Contributors

--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -42,7 +42,7 @@ Note the following:
 - Exports are stored in a temporary [shared directory](../../../development/shared_files.md)
  and are deleted every 24 hours by a specific worker.
 - Group members are exported as project members, as long as the user has
-  maintainer or admin access to the group where the exported project lives.
+  maintainer or administrator access to the group where the exported project lives.
 - Project members with owner access will be imported as maintainers.
 - Imported users can be mapped by their primary email on self-managed instances, if an administrative user (not an owner) does the import.
  Otherwise, a supplementary comment is left to mention that the original author and
@@ -180,7 +180,7 @@ all imported projects are given the visibility of `Private`.

 NOTE:
 The maximum import file size can be set by the Administrator, default is 50MB.
-As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](../../../api/settings.md#change-application-settings) or the [Admin UI](../../admin_area/settings/account_and_limit_settings.md).
+As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](../../../api/settings.md#change-application-settings) or the [Admin Area UI](../../admin_area/settings/account_and_limit_settings.md).

 ### Project import status


--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -262,8 +262,8 @@ quickly share your project with others.

 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/268288) in GitLab 12.9, third-party assets and libraries required for Live Preview are hosted at `https://sandbox-prod.gitlab-static.net` when it is enabled. However, some libraries are still served from other third-party services which may or may not be desirable in your environment.

-The Live Preview feature needs to be enabled in the GitLab instances
-admin settings. Live Preview is enabled for all projects on
+The Live Preview feature needs to be enabled in the GitLab instance's
+Admin Area. Live Preview is enabled for all projects on
 GitLab.com

 ![Administrator Live Preview setting](img/admin_live_preview_v13_0.png)