Clean up vale substitution warnings MR1

doc/administration/auth/ldap/ldap-troubleshooting.md

@@ -387,7 +387,7 @@ the following are true:
 - The configured `admin_group` in the `gitlab.rb` is a CN, rather than a DN or an array.
 - This CN falls under the scope of the configured `group_base`.
 - The members of the `admin_group` have already signed into GitLab with their LDAP
-  credentials. GitLab only grants this administrator access to the users whose
+  credentials. GitLab only grants the Administrator role to the users whose
   accounts are already connected to LDAP.
 
 If all the above are true and the users are still not getting access, [run a manual

doc/administration/clusters/kas.md

@@ -104,7 +104,7 @@ In Omnibus GitLab, find the logs in `/var/log/gitlab/gitlab-kas/`.
 See also the [user documentation](../../user/clusters/agent/index.md#troubleshooting)
 for troubleshooting problems with individual agents.
 
-### KAS logs - GitOps: failed to get project info
+### KAS logs - GitOps: failed to get project information
 
 If you get the following error message:
 

doc/administration/gitaly/troubleshooting.md

@@ -393,7 +393,7 @@ $ sudo /opt/gitlab/embedded/bin/praefect -config /var/opt/gitlab/praefect/config
 praefect sql-migrate: OK (applied 21 migrations)
 ```
 
-### Requests fail with 'repo scoped: invalid Repository' errors
+### Requests fail with 'repository scoped: invalid Repository' errors
 
 This indicates that the virtual storage name used in the
 [Praefect configuration](praefect.md#praefect) does not match the storage name used in

doc/administration/instance_review.md

@@ -12,7 +12,7 @@ If you run a medium-sized self-managed instance (50+ users) of a free version of
 [either Community Edition or unlicensed Enterprise Edition](https://about.gitlab.com/install/ce-or-ee/),
 you qualify for a free Instance Review.
 
-1. Sign in as a user with administrator [permissions](../user/permissions.md).
+1. Sign in as a user with Administrator [role](../user/permissions.md).
 1. In the top menu, click your user icon, and select
    **Get a free instance review**:
 

doc/administration/reference_architectures/10k_users.md

@@ -1509,7 +1509,7 @@ the details of each Gitaly node that makes up the cluster. Each storage is also
 and this name is used in several areas of the configuration. In this guide, the name of the storage will be
 `default`. Also, this guide is geared towards new installs, if upgrading an existing environment
 to use Gitaly Cluster, you may need to use a different name.
-Refer to the [Praefect documentation](../gitaly/praefect.md#praefect) for more info.
+Refer to the [Praefect documentation](../gitaly/praefect.md#praefect) for more information.
 
 The following IPs will be used as an example:
 

doc/administration/reference_architectures/25k_users.md

@@ -1527,7 +1527,7 @@ the details of each Gitaly node that makes up the cluster. Each storage is also
 and this name is used in several areas of the configuration. In this guide, the name of the storage will be
 `default`. Also, this guide is geared towards new installs, if upgrading an existing environment
 to use Gitaly Cluster, you may need to use a different name.
-Refer to the [Praefect documentation](../gitaly/praefect.md#praefect) for more info.
+Refer to the [Praefect documentation](../gitaly/praefect.md#praefect) for more information.
 
 The following IPs will be used as an example: