Merge branch 'docs-aqualls-spelling3' into 'master'

More spelling fixes and changes

See merge request gitlab-org/gitlab!52382

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

@@ -15,6 +15,7 @@ Asana
 Asciidoctor
 Assembla
 Atlassian
+auditability
 Auth0
 Authentiq
 autocomplete
@@ -101,6 +102,7 @@ CSV
 Dangerfile
 datetime
 Debian
+Decompressor
 deduplicate
 deduplicated
 deduplicates
@@ -158,6 +160,7 @@ Flowdock
 Fluentd
 Forgerock
 Fugit
+fuzzer
 Gantt
 Gemnasium
 Gemojione
@@ -173,6 +176,7 @@ Gitpod
 Gitter
 globals
 Gmail
+Godep
 Gollum
 Google
 goroutine
@@ -333,6 +337,7 @@ Phabricator
 phaser
 phasers
 phpenv
+pipenv
 Pipfile
 Pipfiles
 Piwik
@@ -384,6 +389,7 @@ reauthenticate
 reauthenticated
 reauthenticates
 reauthenticating
+rebar
 rebase
 rebased
 rebases
@@ -434,6 +440,7 @@ Rubix
 Rubocop
 Rubular
 ruleset
+rulesets
 runbook
 runbooks
 runit
@@ -512,6 +519,10 @@ tcpdump
 Thanos
 throughputs
 Tiller
+timebox
+timeboxed
+timeboxes
+timeboxing
 timecop
 todos
 tokenizer

doc/user/application_security/api_fuzzing/index.md

@@ -519,7 +519,7 @@ increases as the numbers go up. To use a configuration file, add it to your repo
 ### Overrides
 
 API Fuzzing provides a method to add or override headers and cookies for all outbound HTTP requests
-made. You can use this to inject semver headers, authentication, and so on. The
+made. You can use this to inject semantic version headers, authentication, and so on. The
 [authentication section](#authentication) includes examples of using overrides for that purpose.
 
 Overrides uses a JSON document to define the headers and cookies:

doc/user/application_security/sast/index.md

@@ -117,7 +117,7 @@ The following analyzers have multi-project support:
 #### Enable multi-project support for Security Code Scan
 
 Multi-project support in the Security Code Scan requires a Solution (`.sln`) file in the root of
-the repository. For details on the Solution format, see the Microsoft reference [Solution (.sln) file](https://docs.microsoft.com/en-us/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2019).
+the repository. For details on the Solution format, see the Microsoft reference [Solution (`.sln`) file](https://docs.microsoft.com/en-us/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2019).
 
 ### Making SAST analyzers available to all GitLab tiers
 
@@ -753,4 +753,4 @@ For Maven builds, add the following to your `pom.xml` file:
 
 ### Flawfinder encoding error
 
-This occurs when Flawfinder encounters an invalid UTF-8 character. To fix this, convert all source code in your project to UTF-8 character encoding. This can be done with [cvt2utf](https://github.com/x1angli/cvt2utf) or [iconv](https://www.gnu.org/software/libiconv/documentation/libiconv-1.13/iconv.1.html) either over the entire project or per job using the [`before_script`](../../../ci/yaml/README.md#before_script) feature.
+This occurs when Flawfinder encounters an invalid UTF-8 character. To fix this, convert all source code in your project to UTF-8 character encoding. This can be done with [`cvt2utf`](https://github.com/x1angli/cvt2utf) or [`iconv`](https://www.gnu.org/software/libiconv/documentation/libiconv-1.13/iconv.1.html) either over the entire project or per job using the [`before_script`](../../../ci/yaml/README.md#before_script) feature.

doc/user/asciidoc.md

@@ -40,7 +40,7 @@ Notice how line breaks are now preserved.
 
 An indented (literal) paragraph disables text formatting,
 preserves spaces and line breaks, and is displayed in a
-monospaced font:
+fixed-width font:
 
 ```plaintext
  This literal paragraph is indented with one space.

doc/user/compliance/license_compliance/index.md

@@ -58,7 +58,7 @@ Java 8 and Gradle 1.x projects are not supported. The minimum supported version
 | JavaScript | [Bower](https://bower.io/), [npm](https://www.npmjs.com/)                                    |       |
 | Go         | [Godep](https://github.com/tools/godep), [go mod](https://github.com/golang/go/wiki/Modules) |       |
 | Java       | [Gradle](https://gradle.org/), [Maven](https://maven.apache.org/)                            |       |
-| .NET       | [Nuget](https://www.nuget.org/)                                                              | The .NET Framework is supported via the [mono project](https://www.mono-project.com/). There are, however, some limitations. The scanner doesn't support Windows-specific dependencies and doesn't report dependencies of your project's listed dependencies. Also, the scanner always marks detected licenses for all dependencies as `unknown`. |
+| .NET       | [NuGet](https://www.nuget.org/)                                                              | The .NET Framework is supported via the [mono project](https://www.mono-project.com/). There are, however, some limitations. The scanner doesn't support Windows-specific dependencies and doesn't report dependencies of your project's listed dependencies. Also, the scanner always marks detected licenses for all dependencies as `unknown`. |
 | Python     | [pip](https://pip.pypa.io/en/stable/)                                                        | Python is supported through [requirements.txt](https://pip.pypa.io/en/stable/user_guide/#requirements-files) and [Pipfile.lock](https://github.com/pypa/pipfile#pipfilelock). |
 | Ruby       | [gem](https://rubygems.org/) |  |
 
@@ -70,7 +70,7 @@ The reported licenses might be incomplete or inaccurate.
 | Language   | Package managers                                                                                              |
 |------------|---------------------------------------------------------------------------------------------------------------|
 | JavaScript | [Yarn](https://yarnpkg.com/)                                                                                  |
-| Go         | go get, gvt, glide, dep, trash, govendor                                                                      |
+| Go         | `go get`, `gvt`, `glide`, `dep`, `trash`, `govendor`                                                          |
 | Erlang     | [Rebar](https://www.rebar3.org/)                                                                              |
 | Objective-C, Swift | [Carthage](https://github.com/Carthage/Carthage), [CocoaPods](https://cocoapods.org/) v0.39 and below |
 | Elixir     | [Mix](https://elixir-lang.org/getting-started/mix-otp/introduction-to-mix.html)                               |
@@ -137,11 +137,11 @@ License Compliance can be configured using environment variables.
 | `ASDF_NODEJS_VERSION`       | no       | Version of Node.js to use for the scan. |
 | `ASDF_PYTHON_VERSION`       | no       | Version of Python to use for the scan. |
 | `ASDF_RUBY_VERSION`         | no       | Version of Ruby to use for the scan. |
-| `GRADLE_CLI_OPTS`           | no       | Additional arguments for the gradle executable. If not supplied, defaults to `--exclude-task=test`. |
+| `GRADLE_CLI_OPTS`           | no       | Additional arguments for the Gradle executable. If not supplied, defaults to `--exclude-task=test`. |
 | `LICENSE_FINDER_CLI_OPTS`   | no       | Additional arguments for the `license_finder` executable. For example, if you have multiple projects in nested directories, you can update your `.gitlab-ci-yml` template to specify a recursive scan, like `LICENSE_FINDER_CLI_OPTS: '--recursive'`. |
 | `LM_JAVA_VERSION`           | no       | Version of Java. If set to `11`, Maven and Gradle use Java 11 instead of Java 8. |
 | `LM_PYTHON_VERSION`         | no       | Version of Python. If set to `3`, dependencies are installed using Python 3 instead of Python 2.7. |
-| `MAVEN_CLI_OPTS`            | no       | Additional arguments for the mvn executable. If not supplied, defaults to `-DskipTests`. |
+| `MAVEN_CLI_OPTS`            | no       | Additional arguments for the `mvn` executable. If not supplied, defaults to `-DskipTests`. |
 | `PIP_INDEX_URL`             | no       | Base URL of Python Package Index (default: `https://pypi.org/simple/`). |
 | `SECURE_ANALYZERS_PREFIX`   | no       | Set the Docker registry base address to download the analyzer from. |
 | `SETUP_CMD`                 | no       | Custom setup for the dependency installation (experimental). |
@@ -217,12 +217,12 @@ to explicitly add `-DskipTests` to your options.
 If you still need to run tests during `mvn install`, add `-DskipTests=false` to
 `MAVEN_CLI_OPTS`.
 
-#### Using private Maven repos
+#### Using private Maven repositories
 
 If you have a private Maven repository which requires login credentials,
 you can use the `MAVEN_CLI_OPTS` environment variable.
 
-Read more on [how to use private Maven repos](../../application_security/index.md#using-private-maven-repos).
+Read more on [how to use private Maven repositories](../../application_security/index.md#using-private-maven-repos).
 
 You can also use `MAVEN_CLI_OPTS` to connect to a trusted Maven repository that uses a self-signed
 or internally trusted certificate. For example:
@@ -264,7 +264,7 @@ license_scanning:
 You can supply a custom root certificate to complete TLS verification by using the
 `ADDITIONAL_CA_CERT_BUNDLE` [environment variable](#available-variables).
 
-#### Using private Python repos
+#### Using private Python repositories
 
 If you have a private Python repository you can use the `PIP_INDEX_URL` [environment variable](#available-variables)
 to specify its location.
@@ -560,11 +560,11 @@ You can supply a custom root certificate to complete TLS verification by using t
 In GitLab 12.8 a new name for `license_management` job was introduced. This change was made to improve clarity around the purpose of the scan, which is to scan and collect the types of licenses present in a projects dependencies.
 GitLab 13.0 drops support for `license_management`.
 If you're using a custom setup for License Compliance, you're required
-to update your CI config accordingly:
+to update your CI configuration accordingly:
 
 1. Change the CI template to `License-Scanning.gitlab-ci.yml`.
 1. Change the job name to `license_scanning` (if you mention it in `.gitlab-ci.yml`).
-1. Change the artifact name to `license_scanning`, and the file name to `gl-license-scanning-report.json` (if you mention it in `.gitlab-ci.yml`).
+1. Change the artifact name to `license_scanning`, and the filename to `gl-license-scanning-report.json` (if you mention it in `.gitlab-ci.yml`).
 
 For example, the following `.gitlab-ci.yml`:
 
@@ -662,9 +662,9 @@ Additional configuration may be needed for connecting to
 [private Bundler registries](#using-private-bundler-registries),
 [private Conan registries](#using-private-bower-registries),
 [private Go registries](#using-private-go-registries),
-[private Maven repositories](#using-private-maven-repos),
+[private Maven repositories](#using-private-maven-repositories),
 [private NPM registries](#using-private-npm-registries),
-[private Python repositories](#using-private-python-repos),
+[private Python repositories](#using-private-python-repositories),
 and [private Yarn registries](#using-private-yarn-registries).
 
 ### SPDX license list name matching

doc/user/discussions/index.md

@@ -44,7 +44,7 @@ Thread resolution helps keep track of progress during planning or code review.
 Every standard comment or thread in merge requests, commits, commit diffs, and
 snippets is initially displayed as unresolved. They can then be individually resolved by anyone
 with at least Developer access to the project or by the author of the change being reviewed.
-If the thread has been resolved and a non-member unresolves their own response,
+If the thread has been resolved and a non-member un-resolves their own response,
 this will also unresolve the discussion thread.
 If the non-member then resolves this same response, this will resolve the discussion thread.
 

doc/user/group/epics/manage_epics.md

@@ -176,7 +176,7 @@ To add a new issue to an epic:
    - Search for the desired issue by entering part of the issue's title, then selecting the desired
      match (introduced in [GitLab 12.5](https://gitlab.com/gitlab-org/gitlab/-/issues/9126)).
 
-   If there are multiple issues to be added, press <kbd>Spacebar</kbd> and repeat this step.
+   If there are multiple issues to be added, press <kbd>Space</kbd> and repeat this step.
 1. Select **Add**.
 
 #### Create an issue from an epic
@@ -278,7 +278,7 @@ To add a child epic to an epic:
    - Search for the desired issue by entering part of the epic's title, then selecting the desired
      match (introduced in [GitLab 12.5](https://gitlab.com/gitlab-org/gitlab/-/issues/9126)).
 
-   If there are multiple epics to be added, press <kbd>Spacebar</kbd> and repeat this step.
+   If there are multiple epics to be added, press <kbd>Space</kbd> and repeat this step.
 1. Select **Add**.
 
 ### Move child epics between epics

doc/user/group/index.md

@@ -404,6 +404,8 @@ If an LDAP user is a group member when LDAP Synchronization is added, and they a
 
 To create group links via CN:
 
+<!-- vale gitlab.Spelling = NO -->
+
 1. Select the **LDAP Server** for the link.
 1. Select `LDAP Group cn` as the **Sync method**.
 1. In the **LDAP Group cn** text input box, begin typing the CN of the group. There will be a dropdown menu with matching CNs within the configured `group_base`. Select your CN from this list.
@@ -412,6 +414,8 @@ To create group links via CN:
 
 ![Creating group links via CN](img/ldap_sync_cn_v13_1.png)
 
+<!-- vale gitlab.Spelling = YES -->
+
 ### Creating group links via filter **(PREMIUM ONLY)**
 
 To create group links via filter:

doc/user/group/issues_analytics/index.md

@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7478) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.5.
 
 Issue Analytics is a bar graph which illustrates the number of issues created each month.
-The default timespan is 13 months, which includes the current month, and the 12 months
+The default time span is 13 months, which includes the current month, and the 12 months
 prior.
 
 To access the chart, navigate to your group sidebar and select **{chart}** **Analytics > Issue Analytics**.

doc/user/group/repositories_analytics/index.md

@@ -30,10 +30,10 @@ You can get a CSV of the code coverage data for all of the projects in your grou
 To get the report:
 
 1. Go to your group's **Analytics > Repositories** page
-1. Click **Download historic test coverage data (.csv)**,
+1. Click **Download historic test coverage data (`.csv`)**,
 1. In the popup, select the projects you want to include in the report.
 1. Select the date range for the report from the preset options.
-1. Click **Download test coverage data (.csv)**.
+1. Click **Download test coverage data (`.csv`)**.
 
 The projects dropdown shows up to 100 projects from your group. If the project you want to check is not in the dropdown list, you can select **All projects** to download the report for all projects in your group, including any projects that are not listed. There is a plan to improve this behavior in this [related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/250684).
 

doc/user/group/saml_sso/index.md

@@ -281,7 +281,7 @@ If a user is already a member of the group, linking the SAML identity does not c
 
 To rescind access to the group, perform the following steps, in order:
 
-1. Remove the user from the user datastore on the identity provider or the list of users on the specific app.
+1. Remove the user from the user data store on the identity provider or the list of users on the specific app.
 1. Remove the user from the GitLab.com group.
 
 ### Unlinking accounts
@@ -293,7 +293,7 @@ Users can unlink SAML for a group from their profile page. This can be helpful i
 
 WARNING:
 Unlinking an account removes all roles assigned to that user within the group.
-If a user relinks their account, roles need to be reassigned.
+If a user re-links their account, roles need to be reassigned.
 
 For example, to unlink the `MyOrg` account, the following **Disconnect** button is available under **Profile > Accounts**:
 
@@ -342,7 +342,7 @@ access.
 
 | Term | Description |
 |------|-------------|
-| Identity Provider | The service which manages your user identities such as ADFS, Okta, Onelogin, or Ping Identity. |
+| Identity Provider | The service which manages your user identities such as ADFS, Okta, OneLogin, or Ping Identity. |
 | Service Provider | SAML considers GitLab to be a service provider. |
 | Assertion | A piece of information about a user's identity, such as their name or role. Also known as claims or attributes. |
 | SSO | Single Sign On. |
@@ -377,7 +377,7 @@ For convenience, we've included some [example resources](../../../administration
 
 ### Verifying NameID
 
-In troubleshooting the Group SAML setup, any authenticated user can use the API to verify the NameID GitLab already has linked to the user by visiting [https://gitlab.com/api/v4/user](https://gitlab.com/api/v4/user) and checking the `extern_uid` under identities.
+In troubleshooting the Group SAML setup, any authenticated user can use the API to verify the NameID GitLab already has linked to the user by visiting [`https://gitlab.com/api/v4/user`](https://gitlab.com/api/v4/user) and checking the `extern_uid` under identities.
 
 Similarly, group members of a role with the appropriate permissions can make use of the [members API](../../../api/members.md) to view group SAML identity information for members of the group.
 
@@ -388,7 +388,7 @@ This can then be compared to the [NameID](#nameid) being sent by the Identity Pr
 If a user is trying to sign in for the first time and the GitLab single sign-on URL has not [been configured](#configuring-your-identity-provider), they may see a 404.
 As outlined in the [user access section](#linking-saml-to-your-existing-gitlabcom-account), a group Owner will need to provide the URL to users.
 
-### Message: "SAML authentication failed: Extern uid has already been taken"
+### Message: "SAML authentication failed: Extern UID has already been taken"
 
 This error suggests you are signed in as a GitLab user but have already linked your SAML identity to a different GitLab user. Sign out and then try to sign in again using the SSO SAML link, which should log you into GitLab with the linked user account.
 
@@ -409,7 +409,7 @@ Here are possible causes and solutions:
 |------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|
 | When a user account with the email address already exists in GitLab, but the user does not have the SAML identity tied to their account. | The user will need to [link their account](#user-access-and-management). |
 
-### Message: "SAML authentication failed: Extern uid has already been taken, User has already been taken"
+### Message: "SAML authentication failed: Extern UID has already been taken, User has already been taken"
 
 Getting both of these errors at the same time suggests the NameID capitalization provided by the Identity Provider didn't exactly match the previous value for that user.
 

doc/user/group/saml_sso/scim_setup.md

@@ -260,7 +260,7 @@ It is important not to update these to incorrect values, since this will cause u
 
 Individual users can follow the instructions in the ["SAML authentication failed: User has already been taken"](index.md#i-need-to-change-my-saml-app) section.
 
-Alternatively, users can be removed from the SCIM app which will delink all removed users. Sync can then be turned on for the new SCIM app to [link existing users](#user-access-and-linking-setup).
+Alternatively, users can be removed from the SCIM app which de-links all removed users. Sync can then be turned on for the new SCIM app to [link existing users](#user-access-and-linking-setup).
 
 ### The SCIM app is throwing `"User has already been taken","status":409` error message
 

doc/user/packages/index.md

@@ -35,6 +35,8 @@ You can also use the [API](../../api/packages.md) to administer the Package Regi
 The below table lists formats that are not supported, but are accepting Community contributions for. Consider contributing to GitLab. This [development documentation](../../development/packages.md)
 guides you through the process.
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Format | Status |
 | ------ | ------ |
 | Chef      | [#36889](https://gitlab.com/gitlab-org/gitlab/-/issues/36889) |
@@ -51,6 +53,7 @@ guides you through the process.
 | Terraform | [WIP: Merge Request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/18834) |
 | Vagrant   | [#36899](https://gitlab.com/gitlab-org/gitlab/-/issues/36899) |
 
+<!-- vale gitlab.Spelling = YES -->
 ## Container Registry
 
 The GitLab [Container Registry](container_registry/index.md) is a secure and private registry for container images. It's built on open source software and completely integrated within GitLab. Use GitLab CI/CD to create and publish images. Use the GitLab [API](../../api/container_registry.md) to manage the registry across groups and projects.

doc/user/profile/notifications.md

@@ -173,7 +173,7 @@ In most of the below cases, the notification is sent to:
 - Custom: Users with notification level "custom" who turned on notifications for any of the events present in the table below
 
 NOTE:
-To minimize the number of notifications that do not require any action, from [GitLab 12.9 onwards](https://gitlab.com/gitlab-org/gitlab/-/issues/616), eligible approvers are no longer notified for all the activities in their projects. To receive them they have to change their user notification settings to **Watch** instead.
+To minimize the number of notifications that do not require any action, in [GitLab versions 12.9 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/616), eligible approvers are no longer notified for all the activities in their projects. To receive them they have to change their user notification settings to **Watch** instead.
 
 | Event                  | Sent to |
 |------------------------|---------|