Merge branch 'docs-aqualls-spelling-issues' into 'master'

Tidy up some more spelling issues

See merge request gitlab-org/gitlab!45336

doc/.vale/gitlab/spelling-exceptions.txt

@@ -257,6 +257,7 @@ memoize
 memoized
 memoizing
 Memorystore
+mergeability
 mergeable
 Microsoft
 middleware
@@ -371,6 +372,8 @@ reindex
 reindexed
 reindexes
 reindexing
+reinitialize
+reinitializing
 relicensing
 remediations
 repmgr
@@ -462,6 +465,7 @@ substring
 substrings
 subtree
 subtrees
+sudo
 syslog
 tcpdump
 Tiller

doc/administration/auth/ldap/index.md

@@ -510,7 +510,7 @@ GitLab group membership to be automatically updated based on LDAP group members.
 The `group_base` configuration should be a base LDAP 'container', such as an
 'organization' or 'organizational unit', that contains LDAP groups that should
 be available to GitLab. For example, `group_base` could be
-`ou=groups,dc=example,dc=com`. In the config file it will look like the
+`ou=groups,dc=example,dc=com`. In the configuration file it will look like the
 following.
 
 **Omnibus configuration**

doc/administration/object_storage.md

@@ -17,7 +17,7 @@ GitLab has been tested on a number of object storage providers:
 - [Google Cloud Storage](https://cloud.google.com/storage)
 - [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces/)
 - [Oracle Cloud Infrastructure](https://docs.cloud.oracle.com/en-us/iaas/Content/Object/Tasks/s3compatibleapi.htm)
-- [Openstack Swift](https://docs.openstack.org/swift/latest/s3_compat.html)
+- [OpenStack Swift](https://docs.openstack.org/swift/latest/s3_compat.html)
 - [Azure Blob storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)
 - On-premises hardware and appliances from various storage vendors.
 - MinIO. We have [a guide to deploying this](https://docs.gitlab.com/charts/advanced/external-object-storage/minio.html) within our Helm Chart documentation.
@@ -383,7 +383,7 @@ and comparing the output of the returned headers.
 
 The following YAML shows how the `object_store` section defines
 object-specific configuration block and how the `enabled` and
-`proxy_download` flags can be overriden. The `bucket` is the only
+`proxy_download` flags can be overridden. The `bucket` is the only
 required parameter within each type:
 
 ```yaml
@@ -687,7 +687,7 @@ in the `storage_options` configuration section:
 
 |            Setting                  | Description |
 |-------------------------------------|-------------|
-| `server_side_encryption`            | Encryption mode (AES256 or aws:kms) |
+| `server_side_encryption`            | Encryption mode (`AES256` or `aws:kms`) |
 | `server_side_encryption_kms_key_id` | Amazon Resource Name. Only needed when `aws:kms` is used in `server_side_encryption`. See the [Amazon documentation on using KMS encryption](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html) |
 
 As with the case for default encryption, these options only work when

doc/administration/postgresql/replication_and_failover.md

@@ -425,7 +425,7 @@ Check the [Troubleshooting section](#troubleshooting) before proceeding.
 
 1. Make sure you collect [`CONSUL_SERVER_NODES`](#consul-information), [`CONSUL_PASSWORD_HASH`](#consul-information), and [`PGBOUNCER_PASSWORD_HASH`](#pgbouncer-information) before executing the next step.
 
-1. One each node, edit the `/etc/gitlab/gitlab.rb` config file and replace values noted in the `# START user configuration` section as below:
+1. One each node, edit the `/etc/gitlab/gitlab.rb` configuration file and replace values noted in the `# START user configuration` section as below:
 
    ```ruby
    # Disable all components except PgBouncer and Consul agent

doc/administration/redis/replication_and_failover_external.md

@@ -71,7 +71,7 @@ requirements:
 
 - All Redis servers in this guide must be configured to use a TCP connection
   instead of a socket. To configure Redis to use TCP connections you need to
-  define both `bind` and `port` in the Redis config file. You can bind to all
+  define both `bind` and `port` in the Redis configuration file. You can bind to all
   interfaces (`0.0.0.0`) or specify the IP of the desired interface
   (e.g., one from an internal network).
 - Since Redis 3.2, you must define a password to receive external connections

doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md

@@ -565,7 +565,7 @@ emails = [email1, email2]
 
 emails.each do |e|
   delete_bad_scim(e,'GROUPPATH')
-end  
+end
 ```
 
 ## Routes

doc/administration/troubleshooting/kubernetes_cheat_sheet.md

@@ -84,7 +84,7 @@ and they will assist you with any issues you are having.
 
 ## GitLab-specific Kubernetes information
 
-- Minimal config that can be used to [test a Kubernetes Helm chart](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/620).
+- Minimal configuration that can be used to [test a Kubernetes Helm chart](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/620).
 
 - Tailing logs of a separate pod. An example for a Webservice pod:
 
@@ -189,7 +189,7 @@ and they will assist you with any issues you are having.
   be possible to use [Updating GitLab using the Helm Chart](https://docs.gitlab.com/charts/index.html#updating-gitlab-using-the-helm-chart)
   for upgrades.
 
-- How to apply changes to GitLab config:
+- How to apply changes to GitLab configuration:
 
   - Modify the `gitlab.yaml` file.
   - Run the following command to apply changes:
@@ -254,7 +254,7 @@ to those documents for details.
   helm install gitlab -f <path-to-yaml-file> gitlab/gitlab
   ```
 
-  If you want to modify some GitLab settings, you can use the above-mentioned config
+  If you want to modify some GitLab settings, you can use the above-mentioned configuration
   as a base and create your own YAML file.
 
 - Monitor the installation progress via `helm status gitlab` and `minikube dashboard`.

doc/administration/troubleshooting/log_parsing.md

@@ -7,7 +7,7 @@ but if they are not available you can still quickly parse
 
 ## What is JQ?
 
-As noted in its [manual](https://stedolan.github.io/jq/manual/), jq is a command-line JSON processor. The following examples
+As noted in its [manual](https://stedolan.github.io/jq/manual/), `jq` is a command-line JSON processor. The following examples
 include use cases targeted for parsing GitLab log files.
 
 ## Parsing Logs

doc/administration/uploads.md

@@ -58,7 +58,7 @@ This configuration relies on valid AWS credentials to be configured already.
 [Read more about using object storage with GitLab](object_storage.md).
 
 NOTE: **Note:**
-We recommend using the [consolidated object storage settings](object_storage.md#consolidated-object-storage-configuration). The following instructions apply to the original config format.
+We recommend using the [consolidated object storage settings](object_storage.md#consolidated-object-storage-configuration). The following instructions apply to the original configuration format.
 
 ## Object Storage Settings
 

doc/api/import.md

@@ -50,8 +50,8 @@ POST /import/bitbucket_server
 | `personal_access_token` | string | yes | Bitbucket Server personal access token/password |
 | `bitbucket_server_project` | string | yes | Bitbucket Project Key |
 | `bitbucket_server_repo` | string | yes | Bitbucket Repository Name |
-| `new_name` | string | no | New repo name |
-| `target_namespace` | string | no | Namespace to import repo into |
+| `new_name` | string | no | New repository name |
+| `target_namespace` | string | no | Namespace to import repository into |
 
 ```shell
 curl --request POST \

doc/api/merge_requests.md

@@ -1310,7 +1310,7 @@ curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" "https://git
 
 Merge changes submitted with MR using this API.
 
-If merge request is unable to be accepted (ie: Draft, Closed, Pipeline Pending Completion, or Failed while requiring Success) - you'll get a `405` and the error message 'Method Not Allowed'
+If merge request is unable to be accepted (such as Draft, Closed, Pipeline Pending Completion, or Failed while requiring Success) - you'll get a `405` and the error message 'Method Not Allowed'
 
 If it has some conflicts and can not be merged - you'll get a `406` and the error message 'Branch cannot be merged'
 

doc/api/project_badges.md

@@ -16,7 +16,7 @@ Badges support placeholders that will be replaced in real time in both the link
 - **%{project_path}**: will be replaced by the project path.
 - **%{project_id}**: will be replaced by the project ID.
 - **%{default_branch}**: will be replaced by the project default branch.
-- **%{commit_sha}**: will be replaced by the last project's commit sha.
+- **%{commit_sha}**: will be replaced by the last project's commit SHA.
 
 ## List all badges of a project
 

doc/api/settings.md

@@ -300,7 +300,7 @@ listed in the descriptions of the relevant settings.
 | `mirror_max_capacity`                    | integer          | no                                   | **(PREMIUM)** Maximum number of mirrors that can be synchronizing at the same time. |
 | `mirror_max_delay`                       | integer          | no                                   | **(PREMIUM)** Maximum time (in minutes) between updates that a mirror can have when scheduled to synchronize. |
 | `npm_package_requests_forwarding`        | boolean          | no                                   | **(PREMIUM)** Use npmjs.org as a default remote repository when the package is not found in the GitLab NPM Registry  |
-| `outbound_local_requests_whitelist`      | array of strings | no                                   | Define a list of trusted domains or ip addresses to which local requests are allowed when local requests for hooks and services are disabled.
+| `outbound_local_requests_whitelist`      | array of strings | no                                   | Define a list of trusted domains or IP addresses to which local requests are allowed when local requests for hooks and services are disabled.
 | `pages_domain_verification_enabled`      | boolean          | no                                   | Require users to prove ownership of custom domains. Domain verification is an essential security measure for public GitLab sites. Users are required to demonstrate they control a domain before it is enabled. |
 | `password_authentication_enabled_for_git` | boolean         | no                                   | Enable authentication for Git over HTTP(S) via a GitLab account password. Default is `true`. |
 | `password_authentication_enabled_for_web` | boolean         | no                                   | Enable authentication for the web interface via a GitLab account password. Default is `true`. |
@@ -363,7 +363,7 @@ listed in the descriptions of the relevant settings.
 | `throttle_unauthenticated_requests_per_period` | integer    | required by:<br>`throttle_unauthenticated_enabled` | Max requests per period per IP. |
 | `time_tracking_limit_to_hours`           | boolean          | no                                   | Limit display of time tracking units to hours. Default is `false`. |
 | `two_factor_grace_period`                | integer          | required by: `require_two_factor_authentication` | Amount of time (in hours) that users are allowed to skip forced configuration of two-factor authentication. |
-| `unique_ips_limit_enabled`               | boolean          | no                                   | (**If enabled, requires:** `unique_ips_limit_per_user` and `unique_ips_limit_time_window`) Limit sign in from multiple ips. |
+| `unique_ips_limit_enabled`               | boolean          | no                                   | (**If enabled, requires:** `unique_ips_limit_per_user` and `unique_ips_limit_time_window`) Limit sign in from multiple IPs. |
 | `unique_ips_limit_per_user`              | integer          | required by: `unique_ips_limit_enabled` | Maximum number of IPs per user. |
 | `unique_ips_limit_time_window`           | integer          | required by: `unique_ips_limit_enabled` | How many seconds an IP will be counted towards the limit. |
 | `usage_ping_enabled`                     | boolean          | no                                   | Every week GitLab will report license usage back to GitLab, Inc. |

doc/architecture/blueprints/cloud_native_build_logs/index.md

@@ -120,6 +120,8 @@ available](https://gitlab.com/groups/gitlab-org/-/epics/3791) for everyone.
 
 Proposal:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Role                         | Who
 |------------------------------|-------------------------|
 | Author                       |     Grzegorz Bizon      |
@@ -135,3 +137,5 @@ DRIs:
 | Product                      |     Jason Yavorska     |
 | Leadership                   |       Darby Frey       |
 | Engineering                  |     Grzegorz Bizon     |
+
+<!-- vale gitlab.Spelling = YES -->

doc/architecture/blueprints/cloud_native_gitlab_pages/index.md

@@ -103,6 +103,8 @@ epic with detailed roadmap is also available.
 
 Proposal:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Role                         | Who
 |------------------------------|-------------------------|
 | Author                       |    Grzegorz Bizon       |
@@ -129,3 +131,5 @@ Domain Experts:
 | Domain Expert                |    Vladimir Shushlin   |
 | Domain Expert                |    Jaime Martinez      |
 | Domain Expert                |    Krasimir Angelov    |
+
+<!-- vale gitlab.Spelling = YES -->

doc/architecture/blueprints/feature_flags_development/index.md

@@ -120,6 +120,8 @@ describes a meta reasons for making these changes.
 
 Proposal:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Role                         | Who
 |------------------------------|-------------------------|
 | Author                       | Kamil Trzciński         |
@@ -134,3 +136,5 @@ DRIs:
 | Product                      | Kenny Johnston         |
 | Leadership                   | Craig Gomes            |
 | Engineering                  | Kamil Trzciński        |
+
+<!-- vale gitlab.Spelling = YES -->

doc/user/project/autocomplete_characters.md

@@ -35,6 +35,8 @@ Autocomplete characters are useful when combined with [Quick Actions](quick_acti
 
 Assume your GitLab instance includes the following users:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Username        | Name |
 | :-------------- | :--- |
 | alessandra      | Rosy Grant |
@@ -43,6 +45,8 @@ Assume your GitLab instance includes the following users:
 | logan_gutkowski | Lee Wuckert |
 | shelba          | Josefine Haley |
 
+<!-- vale gitlab.Spelling = YES -->
+
 In an Issue comment, entering `@l` results in the following popup list
 appearing. Note that user `shelba` is not included, because the list includes
 only the 5 users most relevant to the Issue.

doc/user/project/repository/forking_workflow.md

@@ -14,7 +14,7 @@ can create a fork.
 
 A fork is a personal copy of the repository and all its branches, which you create
 in a namespace of your choice. This way you can make changes in your own fork and
-submit them through a merge request to the repo you don't have access to.
+submit them through a merge request to the repository you don't have access to.
 
 ## Creating a fork
 

doc/user/project/repository/repository_mirroring.md

@@ -182,7 +182,7 @@ To set up a mirror from GitLab to AWS CodeCommit:
    not confuse it with the IAM user ID or AWS keys of this user.
 
 1. Copy or download special Git HTTPS user ID and password.
-1. In the AWS CodeCommit console, create a new repository to mirror from your GitLab repo.
+1. In the AWS CodeCommit console, create a new repository to mirror from your GitLab repository.
 1. Open your new repository and click **Clone URL > Clone HTTPS** (not **Clone HTTPS (GRC)**).
 1. In GitLab, open the repository to be push-mirrored.
 1. Click **Settings > Repository** and expand **Mirroring repositories**.
@@ -193,7 +193,7 @@ To set up a mirror from GitLab to AWS CodeCommit:
    ```
 
    Replace `<your_aws_git_userid>` with the AWS **special HTTPS Git user ID** from the IAM Git
-   credentials created earlier. Replace `<your_codecommit_repo>` with the name of your repo in CodeCommit.
+   credentials created earlier. Replace `<your_codecommit_repo>` with the name of your repository in CodeCommit.
 
 1. For **Mirror direction**, select **Push**.
 1. For **Authentication method**, select **Password** and fill in the **Password** field with the special IAM Git clone user ID **password** created earlier in AWS.

doc/user/project/requirements/index.md

@@ -48,7 +48,7 @@ list page.
 To edit a requirement:
 
 1. From the requirements list, click **Edit** (**{pencil}**).
-1. Update the title in text input field. You can also mark (and unmark) a requirement as satisfied in the edit form by using the checkbox labeled "Satisfied".
+1. Update the title in text input field. You can also mark a requirement as satisfied in the edit form by using the checkbox labeled "Satisfied".
 1. Click **Save changes**.
 
 ## Archive a requirement

doc/user/project/static_site_editor/index.md

@@ -13,7 +13,7 @@ description: "The static site editor enables users to edit content on static web
 > - Support for adding images through the WYSIWYG editor [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216640) in GitLab 13.1.
 > - Markdown front matter hidden on the WYSIWYG editor [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216834) in GitLab 13.1.
 > - Support for `*.md.erb` files [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/223171) in GitLab 13.2.
-> - Non-Markdown content blocks uneditable on the WYSIWYG mode [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216836) in GitLab 13.3.
+> - Non-Markdown content blocks not editable on the WYSIWYG mode [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216836) in GitLab 13.3.
 > - Ability to edit page front matter [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235921) in GitLab 13.4.
 
 DANGER: **Danger:**
@@ -92,7 +92,7 @@ content of the pages without prior knowledge of Git or of your site's
 codebase.
 
 NOTE: **Note:**
-From GitLab 13.1 onwards, the YAML front matter of Markdown files is hidden on the
+From GitLab 13.1 onward, the YAML front matter of Markdown files is hidden on the
 WYSIWYG editor to avoid unintended changes. To edit it, use the Markdown editing mode, the regular
 GitLab file editor, or the Web IDE.
 

doc/user/search/advanced_search_syntax.md

@@ -80,7 +80,7 @@ Examples:
 
 [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/31684) in GitLab Starter 13.3.
 
-Filters can be inversed to **filter out** results from the result set, by prefixing the filter name with a `-` (hyphen) character, such as:
+Filters can be inverted to **filter out** results from the result set, by prefixing the filter name with a `-` (hyphen) character, such as:
 
 - `-filename`
 - `-path`

doc/user/search/index.md

@@ -32,7 +32,7 @@ You can also filter the results using the search and filter field, as described
 You'll also find shortcuts to issues and merge requests created by you or assigned to you
 on the search field on the top-right of your screen:
 
-![shortcut to your issues and mrs](img/issues_mrs_shortcut.png)
+![shortcut to your issues and merge requests](img/issues_mrs_shortcut.png)
 
 ### Filtering issue and merge request lists