Merge branch 'Clean-Up-Substitution-warning-3' into 'master'

Clean up substitution warning 3

See merge request gitlab-org/gitlab!71107

doc/install/docker.md

@@ -103,7 +103,7 @@ sudo docker run --detach \
 ```
 
 This will ensure that the Docker process has enough permissions to create the
-config files in the mounted volumes.
+configuration files in the mounted volumes.
 
 If you're using the [Kerberos integration](../integration/kerberos.md) **(PREMIUM ONLY)**,
 you must also publish your Kerberos port (for example, `--publish 8443:8443`).
@@ -573,7 +573,7 @@ sudo docker restart gitlab
 
 This error occurs when using Docker Toolbox with VirtualBox on Windows or Mac,
 and making use of Docker volumes. The `/c/Users` volume is mounted as a
-VirtualBox Shared Folder, and does not support the all POSIX filesystem features.
+VirtualBox Shared Folder, and does not support the all POSIX file system features.
 The directory ownership and permissions cannot be changed without remounting, and
 GitLab fails.
 

doc/install/next_steps.md

@@ -52,7 +52,7 @@ installation.
   Activate all GitLab Enterprise Edition functionality with a license.
 - [Pricing](https://about.gitlab.com/pricing/): Pricing for the different tiers.
 
-## Cross-repo Code Search
+## Cross-repository Code Search
 
 - [Advanced Search](../integration/elasticsearch.md): Leverage Elasticsearch for
   faster, more advanced code search across your entire GitLab instance.

doc/install/requirements.md

@@ -169,7 +169,7 @@ of GitLab Support or other GitLab engineers.
   operations to manage partitioned tables.
 
 - You should not modify the GitLab schema (for example, adding triggers or modifying tables).
-  Database migrations are tested against the schema definition in the GitLab code base. GitLab
+  Database migrations are tested against the schema definition in the GitLab codebase. GitLab
   version upgrades may fail if the schema is modified.
 
 ## Puma settings

doc/integration/jenkins.md

@@ -64,8 +64,8 @@ Grant a GitLab user access to the select GitLab projects.
 
 1. Grant the user permission to the GitLab projects.
 
-   If you're integrating Jenkins with many GitLab projects, consider granting the user global
-   Administrator permission. Otherwise, add the user to each project, and grant the Developer role.
+   If you're integrating Jenkins with many GitLab projects, consider granting the user the global
+   Administrator role. Otherwise, add the user to each project, and grant the Developer role.
 
 ## Configure GitLab API access
 

doc/operations/incident_management/oncall_schedules.md

@@ -31,7 +31,7 @@ To create an on-call schedule:
 1. On the top bar, select **Menu > Projects** and find your project.
 1. On the left sidebar, select **Monitor > On-call Schedules**.
 1. Select **Add a schedule**.
-1. Enter the schedule's name and description and select a timezone.
+1. Enter the schedule's name and description and select a time zone.
 1. Select **Add schedule**.
 
 You now have an empty schedule with no rotations. This renders as an empty state, prompting you to