Fix up the docs warning detected by the vale Admin rule

doc/integration/elasticsearch.md

@@ -155,7 +155,7 @@ may need to set the `production -> elasticsearch -> indexer_path` setting in you
 For GitLab instances with more than 50GB repository data you can follow the instructions for [Indexing large
 instances](#indexing-large-instances) below.
 
-To enable Advanced Search, you must have admin access to GitLab:
+To enable Advanced Search, you must have administrator access to GitLab:
 
 1. On the top bar, select **Menu > Admin**.
 1. On the left sidebar, select **Settings > Advanced Search**.

doc/operations/metrics/embed_grafana.md

@@ -51,7 +51,7 @@ To set up the Grafana API in Grafana:
    section.
 1. To enable the integration, check the **Active** checkbox.
 1. For **Grafana URL**, enter the base URL of the Grafana instance.
-1. For **API Token**, enter the Admin API token you just generated.
+1. For **API Token**, enter the Administrator API token you just generated.
 1. Click **Save Changes**.
 
 ### Generate a link to a panel

doc/public_access/public_access.md

@@ -81,7 +81,7 @@ Prerequisite:
 
 You can restrict the use of visibility levels for users when they create a project or a snippet.
 This is useful to prevent users from publicly exposing their repositories by accident. The
-restricted visibility settings do not apply to admin users.
+restricted visibility settings do not apply to administrators.
 
 For details, see [Restricted visibility levels](../user/admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels).
 

doc/raketasks/user_management.md

@@ -32,7 +32,7 @@ sudo gitlab-rake gitlab:import:all_users_to_all_projects
 bundle exec rake gitlab:import:all_users_to_all_projects RAILS_ENV=production
 ```
 
-Admin users are added as maintainers.
+Administrators are added as maintainers.
 
 ## Add user as a developer to all groups
 

doc/security/information_exclusivity.md

@@ -24,7 +24,7 @@ limitation.
 You can take steps to prevent unintentional sharing and information
 destruction. This limitation is the reason why only certain people are allowed
 to [add users to a project](../user/project/members/index.md)
-and why only a GitLab admin can [force push a protected
+and why only a GitLab administrator can [force push a protected
 branch](../user/project/protected_branches.md).
 
 <!-- ## Troubleshooting

doc/security/reset_user_password.md

@@ -32,7 +32,7 @@ sudo gitlab-rake "gitlab:password:reset[johndoe]"
 
 NOTE:
 To reset the default admin password, run this Rake task with the username
-`root`, which is the default username of that admin account.
+`root`, which is the default username of that administrator account.
 
 ## Rails console
 
@@ -110,7 +110,7 @@ password.
 
 If the username was changed to something else and has been forgotten, one
 possible way is to reset the password using Rails console with user ID `1` (in
-almost all the cases, the first user is the default admin account).
+almost all the cases, the first user is the default administrator account).
 
 <!-- ## Troubleshooting