Vale substitution fixes in docs

doc/user/packages/container_registry/index.md

@@ -914,7 +914,7 @@ these steps:
 ### Troubleshoot as a GitLab server admin
 
 Troubleshooting the GitLab Container Registry, most of the times, requires 
-administrator access to the GitLab server.
+you to log in to GitLab server with the Administrator role.
 
 [Read how to troubleshoot the Container Registry](../../../administration/packages/container_registry.md#troubleshooting).
 

doc/user/packages/debian_repository/index.md

@@ -138,7 +138,7 @@ To install a package:
 
 1. Configure the repository:
 
-    If you are using a private project, add your [credentials](#authenticate-to-the-package-registry) to your apt config:
+    If you are using a private project, add your [credentials](#authenticate-to-the-package-registry) to your apt configuration:
 
     ```shell
     echo 'machine gitlab.example.com login <username> password <your_access_token>' \

doc/user/packages/helm_repository/index.md

@@ -105,7 +105,7 @@ helm install my-release project-1/mychart
 - `<project_id>`: the project ID (like `42`).
 - `<channel>`: the name of the channel (like `stable`).
 
-If the repo has previously been added, you may need to run:
+If the repository has previously been added, you may need to run:
 
 ```shell
 helm repo update

doc/user/project/import/index.md

@@ -47,7 +47,7 @@ information, see [the import notes](../settings/import_export.md#important-notes
 NOTE:
 When migrating to GitLab.com, you must create users manually unless [SCIM](../../../user/group/saml_sso/scim_setup.md)
 will be used. Creating users with the API is limited to self-managed instances as it requires
-administrator access.
+the Administrator role.
 
 To migrate all data from self-managed to GitLab.com, you can leverage the [API](../../../api/index.md).
 Migrate the assets in this order:

doc/user/project/issues/due_dates.md

@@ -15,7 +15,7 @@ the issue can view the due date.
 
 When creating an issue, select the **Due date** field to make a calendar
 appear for choosing the date. To remove the date, select the date
-text and delete it. The date is related to the server's timezone, not the timezone of
+text and delete it. The date is related to the server's time zone, not the time zone of
 the user setting the due date.
 
 ![Create a due date](img/due_dates_create.png)
@@ -45,7 +45,7 @@ Due dates also appear in your [to-do list](../../todos.md).
 
 The day before an open issue is due, an email is sent to all participants
 of the issue. Like the due date, the "day before the due date" is determined by the
-server's timezone.
+server's time zone.
 
 Issues with due dates can also be exported as an iCalendar feed. The URL of the
 feed can be added to calendar applications. The feed is accessible by selecting

doc/user/project/pages/index.md

@@ -87,7 +87,7 @@ GitLab Pages website.
 
 You can either use the GitLab [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
-need administrator access to your domain's registrar (or control panel) to set it up with Pages.
+must have the Administrator role in 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.
 

doc/user/project/releases/index.md

@@ -218,7 +218,7 @@ To set a deploy freeze window in the UI, complete these steps:
 1. Scroll to **Deploy freezes**.
 1. Click **Expand** to see the deploy freeze table.
 1. Click **Add deploy freeze** to open the deploy freeze modal.
-1. Enter the start time, end time, and timezone of the desired deploy freeze period.
+1. Enter the start time, end time, and time zone of the desired deploy freeze period.
 1. Click **Add deploy freeze** in the modal.
 1. After the deploy freeze is saved, you can edit it by selecting the edit button (**{pencil}**) and remove it by selecting the delete button (**{remove}**).
    ![Deploy freeze modal for setting a deploy freeze period](img/deploy_freeze_v14_3.png)