Add more allowed exceptions to the spelling file

More words that should not trip up the spell checker.

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

 Akismet
 Alertmanager
 Algolia
+Alibaba
 allowlist
 allowlisting
 allowlists
@@ -48,6 +49,7 @@ blockquoted
 blockquotes
 blockquoting
 boolean
+Bootsnap
 browsable
 Bugzilla
 Buildkite
@@ -60,6 +62,8 @@ cacheable
 CAS
 CentOS
 Chatops
+checksummed
+checksumming
 Citrix
 Citus
 clonable
@@ -72,6 +76,7 @@ compilable
 composable
 Conda
 Consul
+Corosync
 cron
 crons
 crontab
@@ -91,6 +96,7 @@ deduplication
 denylist
 denylisting
 denylists
+deployers
 deprovision
 deprovisioned
 deprovisioning
@@ -115,6 +121,7 @@ failovers
 failsafe
 fastlane
 favicon
+Fio
 firewalled
 Flawfinder
 Flowdock
@@ -157,6 +164,7 @@ hotfixing
 http
 https
 idempotence
+idmapper
 Ingress
 initializer
 initializers
@@ -185,6 +193,7 @@ Kubernetes
 Kubesec
 Laravel
 LDAP
+ldapsearch
 Libravatar
 Lograge
 Logstash
@@ -193,6 +202,7 @@ lookaheads
 lookbehind
 lookbehinds
 lookups
+loopback
 Lucene
 Maildir
 Makefile
@@ -247,6 +257,7 @@ OpenShift
 Packagist
 parallelization
 parallelizations
+passwordless
 performant
 Pipfile
 Pipfiles
@@ -273,8 +284,8 @@ Prometheus
 proxied
 proxies
 proxying
-Pseudonymized
-Pseudonymizer
+pseudonymized
+pseudonymizer
 Puma
 Python
 Qualys
@@ -298,8 +309,8 @@ reindexes
 reindexing
 relicensing
 remediations
-Repmgr
-Repmgrd
+repmgr
+repmgrd
 repurposing
 requeue
 requeued
@@ -320,6 +331,7 @@ reverifies
 reverify
 Rubix
 Rubocop
+Rubular
 runbook
 runbooks
 runit
@@ -355,6 +367,7 @@ SpotBugs
 SSH
 Stackdriver
 storable
+storages
 strace
 strikethrough
 strikethroughs
@@ -379,6 +392,7 @@ subquerying
 substring
 substrings
 syslog
+tcpdump
 Tiller
 todos
 tokenizer
@@ -433,6 +447,9 @@ unpublished
 unpublishes
 unpublishing
 unreferenced
+unregister
+unregistered
+unregisters
 unreplicated
 unresolve
 unresolved

doc/administration/auth/ldap/index.md

@@ -93,7 +93,7 @@ NOTE: **Note:**
 The `encryption` value `simple_tls` corresponds to 'Simple TLS' in the LDAP
 library. `start_tls` corresponds to StartTLS, not to be confused with regular TLS.
 Normally, if you specify `simple_tls` it will be on port 636, while `start_tls` (StartTLS)
-would be on port 389. `plain` also operates on port 389. Removed values: "tls" was replaced with "start_tls" and "ssl" was replaced with "simple_tls".
+would be on port 389. `plain` also operates on port 389. Removed values: `tls` was replaced with `start_tls` and `ssl` was replaced with `simple_tls`.
 NOTE: **Note:**
 LDAP users must have an email address set, regardless of whether it is used to log in.
@@ -173,7 +173,7 @@ production:
 | `bind_dn` | The full DN of the user you will bind with. | no | `'america\momo'` or `'CN=Gitlab,OU=Users,DC=domain,DC=com'` |
 | `password` | The password of the bind user. | no | `'your_great_password'` |
 | `encryption` | Encryption method. The `method` key is deprecated in favor of `encryption`. | yes | `'start_tls'` or `'simple_tls'` or `'plain'` |
-| `verify_certificates` | Enables SSL certificate verification if encryption method is "start_tls" or "simple_tls". Defaults to true. | no | boolean |
+| `verify_certificates` | Enables SSL certificate verification if encryption method is `start_tls` or `simple_tls`. Defaults to true. | no | boolean |
 | `timeout` | Set a timeout, in seconds, for LDAP queries. This helps avoid blocking a request if the LDAP server becomes unresponsive. A value of 0 means there is no timeout. | no | `10` or `30` |
 | `active_directory` | This setting specifies if LDAP server is Active Directory LDAP server. For non-AD servers it skips the AD specific queries. If your LDAP server is not AD, set this to false. | no | boolean |
 | `allow_username_or_email_login` | If enabled, GitLab will ignore everything after the first `@` in the LDAP username submitted by the user on login. If you are using `uid: 'userPrincipalName'` on ActiveDirectory you need to disable this setting, because the userPrincipalName contains an `@`. | no | boolean |
@@ -595,7 +595,7 @@ When enabled, the following applies:
 NOTE: **Note:**
 These are cron formatted values. You can use a crontab generator to create
-these values, for example <http://www.crontabgenerator.com/>.
+these values, for example [Crontab Generator](http://www.crontabgenerator.com/).
 By default, GitLab runs a group sync process every hour, on the hour.

doc/administration/auth/okta.md

@@ -17,7 +17,7 @@ The following documentation enables Okta as a SAML provider.
 1. Now, very important, add a logo
    (you can choose it from <https://about.gitlab.com/press/>). You'll have to
    crop and resize it.
-1. Next, you'll need the to fill in the SAML general config. Here's an example
+1. Next, you'll need the to fill in the SAML general configuration. Here's an example
    image.
    ![Okta admin panel view](img/okta_admin_panel.png)
@@ -25,14 +25,14 @@ The following documentation enables Okta as a SAML provider.
 1. The last part of the configuration is the feedback section where you can
    just say you're a customer and creating an app for internal use.
 1. When you have your app you'll have a few tabs on the top of the app's
-   profile. Click on the SAML 2.0 config instructions button which should
+   profile. Click on the SAML 2.0 configuration instructions button which should
    look like the following:
    ![Okta SAML settings](img/okta_saml_settings.png)
 1. On the screen that comes up take note of the
    **Identity Provider Single Sign-On URL** which you'll use for the
-   `idp_sso_target_url` on your GitLab config file.
+   `idp_sso_target_url` on your GitLab configuration file.
 1. **Before you leave Okta make sure you add your user and groups if any.**

doc/administration/auth/smartcard.md

@@ -159,7 +159,7 @@ attribute. As a prerequisite, you must use an LDAP server that:
      ```
    For example, the following is an example server context in an NGINX
-   configuration file (eg. in `/etc/nginx/sites-available/gitlab-ssl`):
+   configuration file (such as in `/etc/nginx/sites-available/gitlab-ssl`):
    ```plaintext
    server {

doc/administration/geo/disaster_recovery/index.md

@@ -60,7 +60,7 @@ must disable the **primary** node.
    NOTE: **Note:**
    (**Ubuntu 14.04 LTS**) If you are using an older version of Ubuntu
-   or any other distro based on the Upstart init system, you can prevent GitLab
+   or any other distribution based on the Upstart init system, you can prevent GitLab
    from starting if the machine reboots by doing the following:
    ```shell

doc/administration/geo/replication/database.md

@@ -317,7 +317,7 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
    to the private key, which is **only** present on the **primary** node.
 1. Test that the `gitlab-psql` user can connect to the **primary** node's database
-   (the default Omnibus database name is gitlabhq_production):
+   (the default Omnibus database name is `gitlabhq_production`):
    ```shell
    sudo \

doc/administration/geo/replication/docker_registry.md

@@ -5,7 +5,7 @@ You can set up a [Docker Registry](https://docs.docker.com/registry/) on your
 ## Storage support
-Docker Registry currently supports a few types of storages. If you choose a
+Docker Registry currently supports a few types of storage. If you choose a
 distributed storage (`azure`, `gcs`, `s3`, `swift`, or `oss`) for your Docker
 Registry on the **primary** node, you can use the same storage for a **secondary**
 Docker Registry as well. For more information, read the
@@ -16,7 +16,7 @@ integrated [Container Registry](../../packages/container_registry.md#container-r
 ## Replicating Docker Registry
 You can enable a storage-agnostic replication so it
-can be used for cloud or local storages. Whenever a new image is pushed to the
+can be used for cloud or local storage. Whenever a new image is pushed to the
 **primary** node, each **secondary** node will pull it to its own container
 repository.

doc/administration/geo/replication/external_database.md

@@ -62,7 +62,7 @@ Once your read-only replica is set up, you can skip to [configure you secondary
 #### Manually configure the primary database for replication
-The [geo_primary_role](https://docs.gitlab.com/omnibus/roles/#gitlab-geo-roles)
+The [`geo_primary_role`](https://docs.gitlab.com/omnibus/roles/#gitlab-geo-roles)
 configures the **primary** node's database to be replicated by making changes to
 `pg_hba.conf` and `postgresql.conf`. Make the following configuration changes
 manually to your external database configuration and ensure that you restart PostgreSQL
@@ -123,7 +123,7 @@ hot_standby = on
 ### Configure **secondary** application nodes to use the external read-replica
 With Omnibus, the
-[geo_secondary_role](https://docs.gitlab.com/omnibus/roles/#gitlab-geo-roles)
+[`geo_secondary_role`](https://docs.gitlab.com/omnibus/roles/#gitlab-geo-roles)
 has three main functions:
 1. Configure the replica database.

doc/administration/gitaly/reference.md

@@ -15,7 +15,7 @@ The configuration file is passed as an argument to the `gitaly`
 executable. This is usually done by either Omnibus GitLab or your
 [init](https://en.wikipedia.org/wiki/Init) script.
-An [example config file](https://gitlab.com/gitlab-org/gitaly/blob/master/config.toml.example)
+An [example configuration file](https://gitlab.com/gitlab-org/gitaly/blob/master/config.toml.example)
 can be found in the Gitaly project.
 ## Format
@@ -160,7 +160,7 @@ sum(rate(gitaly_catfile_cache_total{type="hit"}[5m])) / sum(rate(gitaly_catfile_
 A Gitaly process uses one or more `gitaly-ruby` helper processes to
 execute RPC's implemented in Ruby instead of Go. The `[gitaly-ruby]`
-section of the config file contains settings for these helper processes.
+section of the configuration file contains settings for these helper processes.
 These processes are known to occasionally suffer from memory leaks.
 Gitaly restarts its `gitaly-ruby` helpers when their memory exceeds the

doc/administration/high_availability/database.md

@@ -343,7 +343,7 @@ When installing the GitLab package, do not supply `EXTERNAL_URL` value.
 > Please note:
 >
-> - If you want your database to listen on a specific interface, change the config:
+> - If you want your database to listen on a specific interface, change the configuration:
 >   `postgresql['listen_address'] = '0.0.0.0'`.
 > - If your PgBouncer service runs under a different user account,
 >   you also need to specify: `postgresql['pgbouncer_user'] = PGBOUNCER_USERNAME` in
@@ -902,7 +902,7 @@ after it has been restored to service.
 ##### Add a node as a standby server
-  From the stnadby node, run:
+  From the standby node, run:
   ```shell
   gitlab-ctl repmgr standby follow NEW_MASTER
@@ -917,7 +917,7 @@ after it has been restored to service.
 ##### Add a failed master back into the cluster as a standby node
-  Once `repmgrd` and PostgreSQL are runnning, the node will need to follow the new
+  Once `repmgrd` and PostgreSQL are running, the node will need to follow the new
   as a standby node.
   ```shell
@@ -934,7 +934,7 @@ after it has been restored to service.
   gitlab-ctl repmgr standby setup NEW_MASTER
   ```
-  Failure to unregister and readd the old master node can lead to subsequent failovers
+  Failure to unregister and read the old master node can lead to subsequent failovers
   not working.
 #### Alternate configurations

doc/administration/incoming_email.md

@@ -104,7 +104,7 @@ for a real-world example of this exploit.
 ### Omnibus package installations
 1. Find the `incoming_email` section in `/etc/gitlab/gitlab.rb`, enable the feature
-    and fill in the details for your specific IMAP server and email account (see [examples](#config-examples) below).
+    and fill in the details for your specific IMAP server and email account (see [examples](#configuration-examples) below).
 1. Reconfigure GitLab for the changes to take effect:
@@ -130,7 +130,7 @@ Reply by email should now be working.
    ```
 1. Find the `incoming_email` section in `config/gitlab.yml`, enable the feature
-  and fill in the details for your specific IMAP server and email account (see [examples](#config-examples) below).
+  and fill in the details for your specific IMAP server and email account (see [examples](#configuration-examples) below).
 1. Enable `mail_room` in the init script at `/etc/default/gitlab`:
@@ -153,7 +153,7 @@ Reply by email should now be working.
 Reply by email should now be working.
-### Config examples
+### Configuration examples
 #### Postfix

doc/administration/lfs/index.md

@@ -110,7 +110,7 @@ Here is a configuration example with GCS.
 | `provider` | The provider name | `Google` |
 | `google_project` | GCP project name | `gcp-project-12345` |
 | `google_client_email` | The email address of the service account | `foo@gcp-project-12345.iam.gserviceaccount.com` |
-| `google_json_key_location` | The json key path | `/path/to/gcp-project-12345-abcde.json` |
+| `google_json_key_location` | The JSON key path | `/path/to/gcp-project-12345-abcde.json` |
 NOTE: **Note:**
 The service account must have permission to access the bucket.

doc/administration/libravatar.md

@@ -37,7 +37,7 @@ the configuration options as follows:
 ### Your own Libravatar server
-If you are [running your own libravatar service](https://wiki.libravatar.org/running_your_own/),
+If you are [running your own Libravatar service](https://wiki.libravatar.org/running_your_own/),
 the URL will be different in the configuration, but you must provide the same
 placeholders so GitLab can parse the URL correctly.

doc/administration/logs.md

@@ -790,7 +790,7 @@ Omnibus GitLab packages or in `/home/git/gitlab/log/service_measurement.log` for
 installations from source.
 It contain only a single structured log with measurements for each service execution.
-It will contain measurement such as: number of sql calls, execution_time, gc_stats, memory usage, etc...
+It will contain measurement such as: number of SQL calls, `execution_time`, `gc_stats`, memory usage, etc...
 For example:

doc/administration/monitoring/gitlab_self_monitoring_project/index.md

@@ -53,7 +53,7 @@ you should
 ## Taking action on Prometheus alerts **(ULTIMATE)**
 You can [add a webhook](../../../user/project/integrations/prometheus.md#external-prometheus-instances)
-to the Prometheus config in order for GitLab to receive notifications of any alerts.
+to the Prometheus configuration in order for GitLab to receive notifications of any alerts.
 Once the webhook is setup, you can
 [take action on incoming alerts](../../../user/project/integrations/prometheus.md#taking-action-on-incidents-ultimate).

doc/administration/monitoring/prometheus/gitlab_metrics.md

@@ -51,14 +51,14 @@ The following metrics are available:
 | `gitlab_page_out_of_bounds`                                    | Counter   |                   12.8 | Counter for the PageLimiter pagination limit being hit                                              | `controller`, `action`, `bot`                       |
 | `gitlab_rails_queue_duration_seconds`                          | Histogram |                    9.4 | Measures latency between GitLab Workhorse forwarding a request to Rails                             |                                                     |
 | `gitlab_sql_duration_seconds`                                  | Histogram |                   10.2 | SQL execution time, excluding SCHEMA operations and BEGIN / COMMIT                                  |                                                     |
-| `gitlab_transaction_allocated_memory_bytes`                    | Histogram |                   10.2 | Allocated memory for all transactions (gitlab_transaction_* metrics)                                |                                                     |
+| `gitlab_transaction_allocated_memory_bytes`                    | Histogram |                   10.2 | Allocated memory for all transactions (`gitlab_transaction_*` metrics)                                |                                                     |
 | `gitlab_transaction_cache_<key>_count_total`                   | Counter   |                   10.2 | Counter for total Rails cache calls (per key)                                                       |                                                     |
 | `gitlab_transaction_cache_<key>_duration_total`                | Counter   |                   10.2 | Counter for total time (seconds) spent in Rails cache calls (per key)                               |                                                     |
 | `gitlab_transaction_cache_count_total`                         | Counter   |                   10.2 | Counter for total Rails cache calls (aggregate)                                                     |                                                     |
 | `gitlab_transaction_cache_duration_total`                      | Counter   |                   10.2 | Counter for total time (seconds) spent in Rails cache calls (aggregate)                             |                                                     |
 | `gitlab_transaction_cache_read_hit_count_total`                | Counter   |                   10.2 | Counter for cache hits for Rails cache calls                                                        | `controller`, `action`                              |
 | `gitlab_transaction_cache_read_miss_count_total`               | Counter   |                   10.2 | Counter for cache misses for Rails cache calls                                                      | `controller`, `action`                              |
-| `gitlab_transaction_duration_seconds`                          | Histogram |                   10.2 | Duration for all transactions (gitlab_transaction_* metrics)                                        | `controller`, `action`                              |
+| `gitlab_transaction_duration_seconds`                          | Histogram |                   10.2 | Duration for all transactions (`gitlab_transaction_*` metrics)                                        | `controller`, `action`                              |
 | `gitlab_transaction_event_build_found_total`                   | Counter   |                    9.4 | Counter for build found for API /jobs/request                                                       |                                                     |
 | `gitlab_transaction_event_build_invalid_total`                 | Counter   |                    9.4 | Counter for build invalid due to concurrency conflict for API /jobs/request                         |                                                     |
 | `gitlab_transaction_event_build_not_found_cached_total`        | Counter   |                    9.4 | Counter for cached response of build not found for API /jobs/request                                |                                                     |
@@ -124,7 +124,7 @@ configuration option in `gitlab.yml`. These metrics are served from the
 | Metric                                         | Type    | Since | Description | Labels |
 |:---------------------------------------------- |:------- |:----- |:----------- |:------ |
-| `sidekiq_jobs_cpu_seconds`                     | Histogram | 12.4 | Seconds of cpu time to run Sidekiq job                                                              | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
+| `sidekiq_jobs_cpu_seconds`                     | Histogram | 12.4 | Seconds of CPU time to run Sidekiq job                                                              | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
 | `sidekiq_jobs_completion_seconds`              | Histogram | 12.2 | Seconds to complete Sidekiq job                                                                     | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
 | `sidekiq_jobs_db_seconds`                      | Histogram | 12.9 | Seconds of DB time to run Sidekiq job                                                               | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
 | `sidekiq_jobs_gitaly_seconds`                  | Histogram | 12.9 | Seconds of Gitaly time to run Sidekiq job                                                           | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |

doc/administration/monitoring/prometheus/index.md

@@ -84,7 +84,7 @@ To change the address/port that Prometheus listens on:
 1. Save the file and [reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to
    take effect
-### Adding custom scrape configs
+### Adding custom scrape configurations
 You can configure additional scrape targets for the Omnibus GitLab-bundled
 Prometheus by editing `prometheus['scrape_configs']` in `/etc/gitlab/gitlab.rb`

doc/administration/operations/filesystem_benchmarking.md

@@ -14,7 +14,7 @@ I/O. The information on this page can be used for either scenario.
 ### Benchmarking with `fio`
 We recommend using
-[fio](https://fio.readthedocs.io/en/latest/fio_doc.html) to test I/O
+[Fio](https://fio.readthedocs.io/en/latest/fio_doc.html) to test I/O
 performance. This test should be run both on the NFS server and on the
 application nodes that talk to the NFS server.

doc/administration/operations/unicorn.md

@@ -40,9 +40,9 @@ master process has PID 56227 below.
 [2015-06-05T10:58:08.708824 #62538]  INFO -- : worker=10 ready
 ```
-### Tunables
-The main tunables for Unicorn are the number of worker processes and the
+### Tunable options
+The main tunable options for Unicorn are the number of worker processes and the
 request timeout after which the Unicorn master terminates a worker process.
 See the [Omnibus GitLab Unicorn settings
 documentation](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/unicorn.md)

doc/administration/packages/container_registry.md

@@ -376,7 +376,7 @@ The different supported drivers are:
 | swift      | OpenStack Swift Object Storage      |
 | oss        | Aliyun OSS                          |
-Read more about the individual driver's config options in the
+Read more about the individual driver's configuration options in the
 [Docker Registry docs](https://docs.docker.com/registry/configuration/#storage).
 [Read more about using object storage with GitLab](../object_storage.md).
@@ -413,7 +413,7 @@ NOTE: **Note:**
 **Installations from source**
-Configuring the storage driver is done in your registry config YML file created
+Configuring the storage driver is done in your registry configuration YML file created
 when you [deployed your Docker registry](https://docs.docker.com/registry/deploying/).
 `s3` storage driver example:
@@ -610,7 +610,7 @@ You can use GitLab as an auth endpoint with an external container registry.
 You can configure the Container Registry to send webhook notifications in
 response to events happening within the registry.
-Read more about the Container Registry notifications config options in the
+Read more about the Container Registry notifications configuration options in the
 [Docker Registry notifications documentation](https://docs.docker.com/registry/notifications/).
 NOTE: **Note:**
@@ -641,7 +641,7 @@ To configure a notification endpoint in Omnibus:
 **Installations from source**
-Configuring the notification endpoint is done in your registry config YML file created
+Configuring the notification endpoint is done in your registry configuration YML file created
 when you [deployed your Docker registry](https://docs.docker.com/registry/deploying/).
 Example: