And yet MORE spelling corrections!

Continuing the process of cleaning up our documentation and building
a spelling-exceptions file.

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

@@ -3,6 +3,7 @@ Alertmanager
 Algolia
 Alibaba
 allowlist
+allowlisted
 allowlisting
 allowlists
 anonymized
@@ -54,6 +55,7 @@ blockquoted
 blockquotes
 blockquoting
 boolean
+booleans
 Bootsnap
 browsable
 Bugzilla
@@ -131,6 +133,8 @@ Disqus
 Divio
 Dockerfile
 Dockerfiles
+Dockerize
+Dockerizing
 dogfood
 dogfooding
 dogfoods
@@ -156,6 +160,7 @@ failsafe
 Falco
 fastlane
 favicon
+favorited
 Figma
 Filebeat
 Fio
@@ -322,6 +327,8 @@ negatable
 Netlify
 Nokogiri
 npm
+nullability
+nullable
 Nurtch
 nyc
 OAuth
@@ -387,6 +394,7 @@ pseudonymizer
 Puma
 Python
 Qualys
+queryable
 Quicktime
 Rackspace
 Raspbian
@@ -551,6 +559,9 @@ Twitter
 TypeScript
 Ubuntu
 unapplied
+unapprove
+unapproved
+unapproving
 unarchive
 unarchived
 unarchives
@@ -587,6 +598,7 @@ unoptimizing
 unprioritized
 unprotect
 unprotected
+unprotecting
 unprotects
 unprovision
 unprovisioned
@@ -627,6 +639,7 @@ uploader
 uploaders
 upvoted
 upvotes
+URIs
 validator
 validators
 vendored
@@ -643,6 +656,8 @@ WebdriverIO
 Webex
 webpack
 webserver
+websocket
+websockets
 whitepaper
 whitepapers
 wireframe

doc/api/namespaces.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Namespaces API
 
-Usernames and groupnames fall under a special category called namespaces.
+Usernames and group names fall under a special category called namespaces.
 
 For users and groups supported API calls see the [users](users.md) and
 [groups](groups.md) documentation respectively.

doc/api/oauth2.md

@@ -21,7 +21,7 @@ GitLab currently supports the following authorization flows:
 
 - **Authorization code with [Proof Key for Code Exchange (PKCE)](https://tools.ietf.org/html/rfc7636):**
   Most secure. Without PKCE, you'd have to include client secrets on mobile clients,
-  and is recommended for both client and server aoos.
+  and is recommended for both client and server apps.
 - **Authorization code:** Secure and common flow. Recommended option for secure
   server-side apps.
 - **Implicit grant:** Originally designed for user-agent only apps, such as

doc/api/project_badges.md

@@ -13,11 +13,14 @@ type: reference, api
 
 Badges support placeholders that will be replaced in real time in both the link and image URL. The allowed placeholders are:
 
+<!-- vale gitlab.Spelling = NO -->
+
 - **%{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.
 
+<!-- vale gitlab.Spelling = YES -->
 ## List all badges of a project
 
 Gets a list of a project's badges and its group badges.

doc/api/project_level_variables.md

@@ -17,7 +17,7 @@ GET /projects/:id/variables
 
 | Attribute | Type    | required | Description         |
 |-----------|---------|----------|---------------------|
-| `id`      | integer/string | yes      | The ID of a project or [urlencoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user |
+| `id`      | integer/string | yes      | The ID of a project or [URL-encoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user |
 
 ```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/variables"
@@ -48,7 +48,7 @@ GET /projects/:id/variables/:key
 
 | Attribute | Type    | required | Description           |
 |-----------|---------|----------|-----------------------|
-| `id`      | integer/string | yes      | The ID of a project or [urlencoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user   |
+| `id`      | integer/string | yes      | The ID of a project or [URL-encoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user   |
 | `key`     | string  | yes      | The `key` of a variable |
 | `filter`  | hash    | no       | Available filters: `[environment_scope]`. See the [`filter` parameter details](#the-filter-parameter). |
 
@@ -76,7 +76,7 @@ POST /projects/:id/variables
 
 | Attribute           | Type    | required | Description           |
 |---------------------|---------|----------|-----------------------|
-| `id`                | integer/string | yes      | The ID of a project or [urlencoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user   |
+| `id`                | integer/string | yes      | The ID of a project or [URL-encoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user   |
 | `key`               | string  | yes      | The `key` of a variable; must have no more than 255 characters; only `A-Z`, `a-z`, `0-9`, and `_` are allowed |
 | `value`             | string  | yes      | The `value` of a variable |
 | `variable_type`     | string  | no       | The type of a variable. Available types are: `env_var` (default) and `file` |
@@ -109,7 +109,7 @@ PUT /projects/:id/variables/:key
 
 | Attribute           | Type    | required | Description             |
 |---------------------|---------|----------|-------------------------|
-| `id`                | integer/string | yes      | The ID of a project or [urlencoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user     |
+| `id`                | integer/string | yes      | The ID of a project or [URL-encoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user     |
 | `key`               | string  | yes      | The `key` of a variable   |
 | `value`             | string  | yes      | The `value` of a variable |
 | `variable_type`     | string  | no       | The type of a variable. Available types are: `env_var` (default) and `file` |
@@ -143,7 +143,7 @@ DELETE /projects/:id/variables/:key
 
 | Attribute | Type    | required | Description             |
 |-----------|---------|----------|-------------------------|
-| `id`      | integer/string | yes      | The ID of a project or [urlencoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user     |
+| `id`      | integer/string | yes      | The ID of a project or [URL-encoded NAMESPACE/PROJECT_NAME of the project](README.md#namespaced-path-encoding) owned by the authenticated user     |
 | `key`     | string  | yes      | The `key` of a variable |
 | `filter`  | hash    | no       | Available filters: `[environment_scope]`. See the [`filter` parameter details](#the-filter-parameter). |
 

doc/api/services.md

@@ -748,7 +748,7 @@ Send IRC messages, on update, to a list of recipients through an Irker gateway.
 Set Irker (IRC gateway) service for a project.
 
 NOTE:
-Irker does NOT have built-in authentication, which makes it vulnerable to spamming IRC channels if it is hosted outside of a firewall. Please make sure you run the daemon within a secured network to prevent abuse. For more details, read: <http://www.catb.org/~esr/irker/security.html>.
+Irker does NOT have built-in authentication, which makes it vulnerable to spamming IRC channels if it is hosted outside of a firewall. Please make sure you run the daemon within a secured network to prevent abuse. For more details, read [Security analysis of `irker`](http://www.catb.org/~esr/irker/security.html).
 
 ```plaintext
 PUT /projects/:id/services/irker

doc/api/settings.md

@@ -300,11 +300,11 @@ listed in the descriptions of the relevant settings.
 | `housekeeping_incremental_repack_period` | integer          | required by: `housekeeping_enabled`  | Number of Git pushes after which an incremental `git repack` is run. |
 | `html_emails_enabled`                    | boolean          | no                                   | Enable HTML emails. |
 | `import_sources`                         | array of strings | no                                   | Sources to allow project import from, possible values: `github`, `bitbucket`, `bitbucket_server`, `gitlab`, `fogbugz`, `git`, `gitlab_project`, `gitea`, `manifest`, and `phabricator`. |
-| `invisible_captcha_enabled`              | boolean          | no                                   | Enable Invisible Captcha spam detection during signup. Disabled by default. |
+| `invisible_captcha_enabled`              | boolean          | no                                   | Enable Invisible Captcha spam detection during sign-up. Disabled by default. |
 | `issues_create_limit`                    | integer          | no                                   | Max number of issue creation requests per minute per user. Disabled by default.|
 | `local_markdown_version`                 | integer          | no                                   | Increase this value when any cached Markdown should be invalidated. |
 | `maintenance_mode_message`               | string           | no                                   | **(PREMIUM)** Message displayed when instance is in maintenance mode |
-| `maintenance_mode`                       | boolean          | no                                   | **(PREMIUM)** When instance is in maintenance mode, non-admin users can sign in with read-only access and make read-only API requests |
+| `maintenance_mode`                       | boolean          | no                                   | **(PREMIUM)** When instance is in maintenance mode, non-administrative users can sign in with read-only access and make read-only API requests |
 | `max_artifacts_size`                     | integer          | no                                   | Maximum artifacts size in MB |
 | `max_attachment_size`                    | integer          | no                                   | Limit attachment size in MB |
 | `max_import_size`                        | integer          | no                                   | Maximum import size in MB. 0 for unlimited. Default = 0 (unlimited) [Modified](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50MB to 0 in GitLab 13.8. |

doc/architecture/blueprints/feature_flags_development/index.md

@@ -105,7 +105,7 @@ These are reason why these changes are needed:
 - we have ambiguous usage of feature flag with different `default_enabled:` and
   different `actors` used
 - we lack a clear indication who owns what feature flag and where to find
-  relevant informations
+  relevant information
 - we do not emphasise the desire to create feature flag rollout issue to
   indicate that feature flag is in fact a ~"technical debt"
 - we don't know exactly what feature flags we have in our codebase

doc/architecture/blueprints/image_resizing/index.md

@@ -59,6 +59,8 @@ The MVC Avatar resizing implementation is integrated into Workhorse. With the ex
 
 Proposal:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Role                         | Who
 |------------------------------|-------------------------|
 | Author                       |    Craig Gomes          |
@@ -67,10 +69,16 @@ Proposal:
 | Domain Expert                |    Matthias Kaeppler    |
 | Domain Expert                |    Aleksei Lipniagov    |
 
+<!-- vale gitlab.Spelling = YES -->
+
 DRIs:
 
+<!-- vale gitlab.Spelling = NO -->
+
 | Role                         | Who
 |------------------------------|------------------------|
 | Product                      |    Josh Lambert        |
 | Leadership                   |    Craig Gomes         |
 | Engineering                  |    Matthias Kaeppler   |
+
+<!-- vale gitlab.Spelling = YES -->

doc/ci/README.md

@@ -204,7 +204,7 @@ been necessary. These are:
 
 #### 12.0
 
-- [Use refspec to clone/fetch Git repository](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4069).
+- [Use `refspec` to clone/fetch Git repository](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4069).
 - [Old cache configuration](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4070).
 - [Old metrics server configuration](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4072).
 - [Remove `FF_K8S_USE_ENTRYPOINT_OVER_COMMAND`](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4073).

doc/ci/cloud_deployment/index.md

@@ -47,11 +47,11 @@ Some credentials are required to be able to run `aws` commands:
      You might want to check if the AWS service you intend to use is
      [available in the chosen region](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/).
 
-   | Env. variable name      | Value                  |
-   |:------------------------|:-----------------------|
-   | `AWS_ACCESS_KEY_ID`     | Your Access key ID     |
-   | `AWS_SECRET_ACCESS_KEY` | Your Secret access key |
-   | `AWS_DEFAULT_REGION`    | Your region code       |
+   | Environment variable name      | Value                  |
+   |:-------------------------------|:-----------------------|
+   | `AWS_ACCESS_KEY_ID`            | Your Access key ID     |
+   | `AWS_SECRET_ACCESS_KEY`        | Your Secret access key |
+   | `AWS_DEFAULT_REGION`           | Your region code       |
 
 1. You can now use `aws` commands in the `.gitlab-ci.yml` file of this project:
 

doc/ci/docker/using_kaniko.md

@@ -76,7 +76,7 @@ If you use a custom GitLab Runner behind an http(s) proxy, kaniko needs to be se
 up accordingly. This means:
 
 - Adding the proxy to `/kaniko/.docker/config.json`
-- Passing the `http_proxy` environment variables as build args so the Dockerfile
+- Passing the `http_proxy` environment variables as build arguments so the Dockerfile
   instructions can use the proxy when building the image.
 
 The previous example can be extended as follows:

doc/ci/examples/README.md

@@ -34,10 +34,10 @@ The following table lists examples with step-by-step tutorials that are containe
 | NPM with semantic-release     | [Publish NPM packages to the GitLab Package Registry using semantic-release](semantic-release.md). |
 | PHP with Laravel, Envoy       | [Test and deploy Laravel applications with GitLab CI/CD and Envoy](laravel_with_gitlab_and_envoy/index.md). |
 | PHP with NPM, SCP             | [Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD](deployment/composer-npm-deploy.md). |
-| PHP with PHPunit, atoum       | [Testing PHP projects](php.md). |
+| PHP with PHPunit, `atoum`       | [Testing PHP projects](php.md). |
 | Python on Heroku              | [Test and deploy a Python application with GitLab CI/CD](test-and-deploy-python-application-to-heroku.md). |
 | Ruby on Heroku                | [Test and deploy a Ruby application with GitLab CI/CD](test-and-deploy-ruby-application-to-heroku.md). |
-| Secrets management with Vault | [Authenticating and Reading Secrets With Hashicorp Vault](authenticating-with-hashicorp-vault/index.md). |
+| Secrets management with Vault | [Authenticating and Reading Secrets With HashiCorp Vault](authenticating-with-hashicorp-vault/index.md). |
 
 ### Contributed examples
 
@@ -47,7 +47,7 @@ separate example projects:
 
 | Use case                      | Resource |
 |-------------------------------|----------|
-| Game development              | [DevOps and Game Dev with GitLab CI/CD](https://gitlab.com/gitlab-examples/gitlab-game-demo/). |
+| Game development              | [DevOps and Game Development with GitLab CI/CD](https://gitlab.com/gitlab-examples/gitlab-game-demo/). |
 | Java with Maven               | [How to deploy Maven projects to Artifactory with GitLab CI/CD](https://gitlab.com/gitlab-examples/maven/simple-maven-example). |
 | Java with Spring Boot         | [Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD](https://gitlab.com/gitlab-examples/spring-gitlab-cf-deploy-demo). |
 | Parallel testing Ruby & JS    | [GitLab CI/CD parallel jobs testing for Ruby & JavaScript projects](https://docs.knapsackpro.com/2019/how-to-run-parallel-jobs-for-rspec-tests-on-gitlab-ci-pipeline-and-speed-up-ruby-javascript-testing). |
@@ -99,7 +99,7 @@ choose one of these templates:
 
 If a programming language or framework template is not in this list, you can contribute
 one. To create a template, submit a merge request
-to <https://gitlab.com/gitlab-org/gitlab/tree/master/lib/gitlab/ci/templates>.
+to [the templates list](https://gitlab.com/gitlab-org/gitlab/tree/master/lib/gitlab/ci/templates).
 
 ### Adding templates to your GitLab installation **(PREMIUM ONLY)**
 
@@ -131,7 +131,7 @@ See also the following video overviews:
 
 For some customer experiences with GitLab CI/CD, see:
 
-- [How Verizon Connect reduced datacenter deploys from 30 days to under 8 hours with GitLab](https://about.gitlab.com/blog/2019/02/14/verizon-customer-story/)
+- [How Verizon Connect reduced data center deploys from 30 days to under 8 hours with GitLab](https://about.gitlab.com/blog/2019/02/14/verizon-customer-story/)
 - [How Wag! cut their release process from 40 minutes to just 6](https://about.gitlab.com/blog/2019/01/16/wag-labs-blog-post/)
 - [How Jaguar Land Rover embraced CI to speed up their software lifecycle](https://about.gitlab.com/blog/2018/07/23/chris-hill-devops-enterprise-summit-talk/)
 

doc/ci/examples/authenticating-with-hashicorp-vault/index.md

@@ -5,13 +5,13 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: tutorial
 ---
 
-# Authenticating and Reading Secrets With Hashicorp Vault
+# Authenticating and Reading Secrets With HashiCorp Vault
 
 This tutorial demonstrates how to authenticate, configure, and read secrets with HashiCorp's Vault from GitLab CI/CD.
 
 NOTE:
 [GitLab Premium](https://about.gitlab.com/pricing/) supports read access to a
-Hashicorp Vault, and enables you to
+HashiCorp Vault, and enables you to
 [use Vault secrets in a CI job](../../secrets/index.md#use-vault-secrets-in-a-ci-job).
 To learn more, read [Using external secrets in CI](../../secrets/index.md).
 
@@ -155,11 +155,11 @@ This example uses [bound_claims](https://www.vaultproject.io/api/auth/jwt#bound_
 
 Combined with [protected branches](../../../user/project/protected_branches.md), you can restrict who is able to authenticate and read the secrets.
 
-[token_explicit_max_ttl](https://www.vaultproject.io/api/auth/jwt#token_explicit_max_ttl) specifies that the token issued by Vault, upon successful authentication, has a hard lifetime limit of 60 seconds.
+[`token_explicit_max_ttl`](https://www.vaultproject.io/api/auth/jwt#token_explicit_max_ttl) specifies that the token issued by Vault, upon successful authentication, has a hard lifetime limit of 60 seconds.
 
-[user_claim](https://www.vaultproject.io/api/auth/jwt#user_claim) specifies the name for the Identity alias created by Vault upon a successful login.
+[`user_claim`](https://www.vaultproject.io/api/auth/jwt#user_claim) specifies the name for the Identity alias created by Vault upon a successful login.
 
-[bound_claims_type](https://www.vaultproject.io/api-docs/auth/jwt#bound_claims_type) configures the interpretation of the `bound_claims` values. If set to `glob`, the values are interpreted as globs, with `*` matching any number of characters.
+[`bound_claims_type`](https://www.vaultproject.io/api-docs/auth/jwt#bound_claims_type) configures the interpretation of the `bound_claims` values. If set to `glob`, the values are interpreted as globs, with `*` matching any number of characters.
 
 For the full list of options, see Vault's [Create Role documentation](https://www.vaultproject.io/api/auth/jwt#create-role).
 

doc/ci/examples/deployment/README.md

@@ -39,7 +39,7 @@ The Dpl provides support for vast number of services, including: Heroku, Cloud F
 To use it simply define provider and any additional parameters required by the provider.
 
 For example if you want to use it to deploy your application to Heroku, you need to specify `heroku` as provider, specify `api-key` and `app`.
-All possible parameters can be found here: <https://github.com/travis-ci/dpl#heroku-api>.
+All possible parameters can be found in the [Heroku API section](https://github.com/travis-ci/dpl#heroku-api).
 
 ```yaml
 staging:

doc/ci/examples/php.md

@@ -66,8 +66,7 @@ docker-php-ext-install pdo_mysql
 
 You might wonder what `docker-php-ext-install` is. In short, it is a script
 provided by the official PHP Docker image that you can use to easily install
-extensions. For more information read the documentation at
-<https://hub.docker.com/_/php>.
+extensions. For more information read [the documentation](https://hub.docker.com/_/php).
 
 Now that we created the script that contains all prerequisites for our build
 environment, let's add it in `.gitlab-ci.yml`:
@@ -179,8 +178,8 @@ phpenv config-add my_config.ini
 
 *__Important note:__ It seems `phpenv/phpenv`
  [is abandoned](https://github.com/phpenv/phpenv/issues/57). There is a fork
- at [madumlao/phpenv](https://github.com/madumlao/phpenv) that tries to bring
- the project back to life. [CHH/phpenv](https://github.com/CHH/phpenv) also
+ at [`madumlao/phpenv`](https://github.com/madumlao/phpenv) that tries to bring
+ the project back to life. [`CHH/phpenv`](https://github.com/CHH/phpenv) also
  seems like a good alternative. Picking any of the mentioned tools works
  with the basic phpenv commands. Guiding you to choose the right phpenv is out
  of the scope of this tutorial.*
@@ -201,10 +200,10 @@ command once, only to set up the build environment.
 
 ## Extend your tests
 
-### Using atoum
+### Using `atoum`
 
 Instead of PHPUnit, you can use any other tool to run unit tests. For example
-you can use [atoum](https://github.com/atoum/atoum):
+you can use [`atoum`](https://github.com/atoum/atoum):
 
 ```yaml
 before_script:

doc/ci/migration/circleci.md

@@ -271,8 +271,8 @@ CircleCI provides [Contexts](https://circleci.com/docs/2.0/contexts/) to securel
 
 There are two GitLab issues open addressing CircleCI Orbs and how GitLab can achieve similar functionality.
 
-- <https://gitlab.com/gitlab-com/Product/-/issues/1151>
-- <https://gitlab.com/gitlab-org/gitlab/-/issues/195173>
+- [issue #1151](https://gitlab.com/gitlab-com/Product/-/issues/1151)
+- [issue #195173](https://gitlab.com/gitlab-org/gitlab/-/issues/195173)
 
 ## Build environments
 

doc/ci/review_apps/index.md

@@ -180,11 +180,11 @@ After you have the route mapping set up, it takes effect in the following locati
 
 - In the diff for a merge request, comparison, or commit.
 
-  !["View on env" button in merge request diff](img/view_on_env_mr.png)
+  ![View on environment button in merge request diff](img/view_on_env_mr.png)
 
 - In the blob file view.
 
-  !["View on env" button in file view](img/view_on_env_blob.png)
+  ![View on environment button in file view](img/view_on_env_blob.png)
 
 ## Visual Reviews **(STARTER)**
 

doc/ci/variables/README.md

@@ -1076,7 +1076,7 @@ if [[ -d "/builds/gitlab-examples/ci-debug-trace/.git" ]]; then
 
 ## Video walkthrough of a working example
 
-The [Managing the Complex Configuration Data Management Monster Using GitLab](https://www.youtube.com/watch?v=v4ZOJ96hAck) video is a walkthrough of the [Complex Config Data Monorepo](https://gitlab.com/guided-explorations/config-data-top-scope/config-data-subscope/config-data-monorepo) working example project. It explains how multiple levels of group CI/CD variables can be combined with environment-scoped project variables for complex configuration of application builds or deployments.
+The [Managing the Complex Configuration Data Management Monster Using GitLab](https://www.youtube.com/watch?v=v4ZOJ96hAck) video is a walkthrough of the [Complex Configuration Data Monorepo](https://gitlab.com/guided-explorations/config-data-top-scope/config-data-subscope/config-data-monorepo) working example project. It explains how multiple levels of group CI/CD variables can be combined with environment-scoped project variables for complex configuration of application builds or deployments.
 
 The example can be copied to your own group or instance for testing. More details
 on what other GitLab CI patterns are demonstrated are available at the project page.

doc/ci/yaml/gitlab_ci_yaml.md

@@ -5,7 +5,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---
 <!-- markdownlint-disable MD044 -->
+<!-- vale gitlab.Spelling = NO -->
 # The .gitlab-ci.yml file
+<!-- vale gitlab.Spelling = YES -->
 <!-- markdownlint-enable MD044 -->
 
 To use GitLab CI/CD, you need:

doc/development/README.md

@@ -230,7 +230,7 @@ See [database guidelines](database/index.md).
 - [Security Scanners](integrations/secure.md)
 - [Secure Partner Integration](integrations/secure_partner_integration.md)
 - [How to run Jenkins in development environment](integrations/jenkins.md)
-- [How to run local Codesandbox integration for Web IDE Live Preview](integrations/codesandbox.md)
+- [How to run local `Codesandbox` integration for Web IDE Live Preview](integrations/codesandbox.md)
 
 ## Testing guides
 

doc/development/api_graphql_styleguide.md

@@ -10,7 +10,9 @@ This document outlines the style guide for the GitLab [GraphQL API](../api/graph
 
 ## How GitLab implements GraphQL
 
+<!-- vale gitlab.Spelling = NO -->
 We use the [GraphQL Ruby gem](https://graphql-ruby.org/) written by [Robert Mosolgo](https://github.com/rmosolgo/).
+<!-- vale gitlab.Spelling = YES -->
 
 All GraphQL queries are directed to a single endpoint
 ([`app/controllers/graphql_controller.rb#execute`](https://gitlab.com/gitlab-org/gitlab/blob/master/app%2Fcontrollers%2Fgraphql_controller.rb)),

doc/development/api_styleguide.md

@@ -28,7 +28,7 @@ See the [Documentation Style Guide RESTful API page](documentation/restful_api_s
 ## Methods and parameters description
 
 Every method must be described using the [Grape DSL](https://github.com/ruby-grape/grape#describing-methods)
-(see <https://gitlab.com/gitlab-org/gitlab/blob/master/lib/api/environments.rb>
+(see [`environments.rb`](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/api/environments.rb)
 for a good example):
 
 - `desc` for the method summary. You should pass it a block for additional