Merge branch 'Clean-Up-Substitution-warning-(administration)-2' into 'master'

Clean up docs warnings detected by the Vale Substitution Warnings rule

See merge request gitlab-org/gitlab!71028

doc/administration/geo/replication/troubleshooting.md

@@ -430,7 +430,7 @@ their resync may take a long time and cause significant load on your Geo nodes,
 storage and network systems.
 
 If you get the error `Synchronization failed - Error syncing repository` along with the following log messages, this indicates that the expected `geo` remote is not present in the `.git/config` file
-of a repository on the secondary Geo node's filesystem:
+of a repository on the secondary Geo node's file system:
 
 ```json
 {
@@ -803,7 +803,7 @@ get_ctl_options': invalid option: --skip-preflight-checks (OptionParser::Invalid
 get_ctl_options': invalid option: --force (OptionParser::InvalidOption)
 ```
 
-This can happen with XFS or filesystems that list files in lexical order, because the
+This can happen with XFS or file systems that list files in lexical order, because the
 load order of the Omnibus command files can be different than expected, and a global function would get redefined.
 More details can be found in [the related issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6076).
 

doc/administration/package_information/defaults.md

@@ -59,7 +59,7 @@ Legend:
 - `Alternative` - If it is possible to configure the component to use different type of communication. The type is listed with default port used in that case.
 - `Connection port` - Port on which the component communicates.
 
-GitLab also expects a filesystem to be ready for the storage of Git repositories
+GitLab also expects a file system to be ready for the storage of Git repositories
 and various other files.
 
 Note that if you are using NFS (Network File System), files will be carried

doc/administration/package_information/index.md

@@ -39,7 +39,7 @@ libraries are located in `/opt/gitlab/version-manifest.txt`.
 
 If you don't have the package installed, you can always check the Omnibus GitLab
 [source repository](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master), specifically the
-[config directory](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/config).
+[configuration directory](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/config).
 
 For example, if you examine the `8-6-stable` branch, you can conclude that
 8.6 packages were running [Ruby 2.1.8](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/8-6-stable/config/projects/gitlab.rb#L48).

doc/administration/reference_architectures/3k_users.md

@@ -1230,7 +1230,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/50k_users.md

@@ -1531,7 +1531,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/5k_users.md

@@ -1222,7 +1222,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/timezone.md

@@ -14,22 +14,22 @@ The global time zone configuration parameter can be changed in `config/gitlab.ym
 
 Uncomment and customize if you want to change the default time zone of the GitLab application.
 
-## Viewing available timezones
+## Viewing available time zones
 
 To see all available time zones, run `bundle exec rake time:zones:all`.
 
 For Omnibus installations, run `gitlab-rake time:zones:all`.
 
 NOTE:
-This Rake task does not list timezones in TZInfo format required by Omnibus GitLab during a reconfigure: [#27209](https://gitlab.com/gitlab-org/gitlab/-/issues/27209).
+This Rake task does not list time zones in TZInfo format required by Omnibus GitLab during a reconfigure: [#27209](https://gitlab.com/gitlab-org/gitlab/-/issues/27209).
 
 ## Changing time zone in Omnibus installations
 
-GitLab defaults its time zone to UTC. It has a global timezone configuration parameter in `/etc/gitlab/gitlab.rb`.
+GitLab defaults its time zone to UTC. It has a global time zone configuration parameter in `/etc/gitlab/gitlab.rb`.
 
-To obtain a list of timezones, log in to your GitLab application server and run a command that generates a list of timezones in TZInfo format for the server. For example, install `timedatectl` and run `timedatectl list-timezones`.
+To obtain a list of time zones, log in to your GitLab application server and run a command that generates a list of time zones in TZInfo format for the server. For example, install `timedatectl` and run `timedatectl list-timezones`.
 
-To update, add the timezone that best applies to your location. For example:
+To update, add the time zone that best applies to your location. For example:
 
 ```ruby
 gitlab_rails['time_zone'] = 'America/New_York'