diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md
index 5c1f8a332463e985058a55a8deedd4ef0e5783a6..209744cc66a282e96028a42b9ba82c9e33d791f6 100644
--- a/doc/administration/gitaly/praefect.md
+++ b/doc/administration/gitaly/praefect.md
@@ -748,7 +748,7 @@ documentation](index.md#configure-gitaly-servers).
 
 After all Gitaly nodes are configured, you can run the Praefect connection
 checker to verify Praefect can connect to all Gitaly servers in the Praefect
-config.
+configuration.
 
 1. SSH into each **Praefect** node and run the Praefect connection checker:
 
diff --git a/doc/administration/packages/index.md b/doc/administration/packages/index.md
index f7a652ef346549b5d843a0414d87f90c48fe5243..0f391371a6a6db4ca6cfe95a50b8d1e6803fbe6a 100644
--- a/doc/administration/packages/index.md
+++ b/doc/administration/packages/index.md
@@ -137,7 +137,7 @@ store packages.
 [Read more about using object storage with GitLab](../object_storage.md).
 
 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.
 
 **Omnibus GitLab installations**
 
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md
index 87ccbe6747c75582b1bd931c22a3bb46f20ba75c..2dee9639cce24dcdd64bd01d61c3e97a7d9a5579 100644
--- a/doc/administration/pages/index.md
+++ b/doc/administration/pages/index.md
@@ -204,7 +204,7 @@ control over how the Pages daemon runs and serves content in your environment.
 | `artifacts_server_url` |  API URL to proxy artifact requests to. Defaults to GitLab `external URL` + `/api/v4`, for example `https://gitlab.com/api/v4`.
 | `auth_redirect_uri` |  Callback URL for authenticating with GitLab. Defaults to project's subdomain of `pages_external_url` + `/auth`.
 | `auth_secret` |  Secret key for signing authentication requests. Leave blank to pull automatically from GitLab during OAuth registration.
-| `dir` |  Working directory for config and secrets files.
+| `dir` |  Working directory for configuration and secrets files.
 | `enable` |  Enable or disable GitLab Pages on the current system.
 | `external_http` |  Configure Pages to bind to one or more secondary IP addresses, serving HTTP requests. Multiple addresses can be given as an array, along with exact ports, for example `['1.2.3.4', '1.2.3.5:8063']`. Sets value for `listen_http`.
 | `external_https` |  Configure Pages to bind to one or more secondary IP addresses, serving HTTPS requests. Multiple addresses can be given as an array, along with exact ports, for example `['1.2.3.4', '1.2.3.5:8063']`. Sets value for `listen_https`.
@@ -241,7 +241,7 @@ control over how the Pages daemon runs and serves content in your environment.
 | `pages_path` | The directory on disk where pages are stored, defaults to `GITLAB-RAILS/shared/pages`.
 | `pages_nginx[]` | |
 | `enable` | Include a virtual host `server{}` block for Pages inside NGINX. Needed for NGINX to proxy traffic back to the Pages daemon. Set to `false` if the Pages daemon should directly receive all requests, for example, when using [custom domains](index.md#custom-domains).
-| `FF_ENABLE_REDIRECTS` | Feature flag to disable redirects (enabled by default). Read the [redirects documentation](../../user/project/pages/redirects.md#disable-redirects) for more info. |
+| `FF_ENABLE_REDIRECTS` | Feature flag to disable redirects (enabled by default). Read the [redirects documentation](../../user/project/pages/redirects.md#disable-redirects) for more information. |
 
 ---
 
diff --git a/doc/administration/pages/source.md b/doc/administration/pages/source.md
index 79021e42f0eb4405402bcd7280371e1ab1da5240..c7c25f0f3a72090d9c9500181eb4a96bf4a2c7c5 100644
--- a/doc/administration/pages/source.md
+++ b/doc/administration/pages/source.md
@@ -395,7 +395,7 @@ API to check that the user is authorized to read that site.
 From [GitLab 12.8](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/3689) onward,
 Access Control parameters for Pages are set in a configuration file, which
 by convention is named `gitlab-pages-config`. The configuration file is passed to
-pages using the `-config flag` or CONFIG environment variable.
+pages using the `-config flag` or `CONFIG` environment variable.
 
 Pages access control is disabled by default. To enable it:
 
diff --git a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
index 8f342030a80f3f37efbc8361ae488c805fb0333d..07a7baf338b28a03f5d11c2b13a7f6f9a04e6838 100644
--- a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
+++ b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
@@ -207,7 +207,7 @@ all Kubernetes resources and dependent charts:
   helm get manifest <release name>
   ```
 
-## Installation of minimal GitLab config via Minikube on macOS
+## Installation of minimal GitLab configuration via Minikube on macOS
 
 This section is based on [Developing for Kubernetes with Minikube](https://docs.gitlab.com/charts/development/minikube/index.html)
 and [Helm](https://docs.gitlab.com/charts/installation/tools.html#helm). Refer
diff --git a/doc/administration/troubleshooting/linux_cheat_sheet.md b/doc/administration/troubleshooting/linux_cheat_sheet.md
index 5a7d0113c194a9cd8b4ed3d4c276a8ac2aba3d5d..c61a78624c3fc59859e7dcba732a134872915659 100644
--- a/doc/administration/troubleshooting/linux_cheat_sheet.md
+++ b/doc/administration/troubleshooting/linux_cheat_sheet.md
@@ -23,7 +23,7 @@ on. Contributions are welcome to help add them.
 
 ## System Commands
 
-### Distro Information
+### Distribution Information
 
 ```shell
 # Debian/Ubuntu
@@ -200,7 +200,7 @@ or you can build it from source if you have the Rust compiler.
 
 #### How to use the tool
 
-First run the tool with no arguments other than the strace output file name to get
+First run the tool with no arguments other than the strace output filename to get
 a summary of the top processes sorted by time spent actively performing tasks. You
 can also sort based on total time, # of syscalls made, PID #, and # of child processes
 using the `-S` or `--sort` flag. The number of results defaults to 25 processes, but
diff --git a/doc/administration/troubleshooting/tracing_correlation_id.md b/doc/administration/troubleshooting/tracing_correlation_id.md
index a83f913b40b3f043f49616dd614836e742e3d501..2981b9e1368d106c7ddecb5aac5706023edfabea 100644
--- a/doc/administration/troubleshooting/tracing_correlation_id.md
+++ b/doc/administration/troubleshooting/tracing_correlation_id.md
@@ -56,7 +56,7 @@ interested in.
 
 ### Getting the correlation ID from curl
 
-If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug info.
+If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug information.
 
 ```shell
 ➜  ~ curl --verbose "https://gitlab.example.com/api/v4/projects"
diff --git a/doc/api/issues.md b/doc/api/issues.md
index cbb0dad98413a62fa2c7b356660c861f7f5d7479..f6bab9ce6766b0df3ee70e2a5f125dec1641a353 100644
--- a/doc/api/issues.md
+++ b/doc/api/issues.md
@@ -2155,7 +2155,7 @@ POST /projects/:id/issues/:issue_iid/metric_images
 | `id`        | integer/string | yes      | The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user  |
 | `issue_iid` | integer | yes      | The internal ID of a project's issue |
 | `file` | file | yes      | The image file to be uploaded |
-| `url` | string | no      | The URL to view more metric info |
+| `url` | string | no      | The URL to view more metric information |
 
 ```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" --form 'file=@/path/to/file.png' \
diff --git a/doc/api/search.md b/doc/api/search.md
index d92b8c71dc24bda005809d4fe6150789f774eabc..bfa5eb576dc2039685062e9cf40c1f25e9677612 100644
--- a/doc/api/search.md
+++ b/doc/api/search.md
@@ -293,7 +293,7 @@ Example response:
 ```
 
 NOTE:
-`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
+`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
 
 ### Scope: commits **(STARTER)**
 
@@ -675,7 +675,7 @@ Example response:
 ```
 
 NOTE:
-`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
+`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
 
 ### Scope: commits **(STARTER)**
 
@@ -1072,7 +1072,7 @@ Example response:
 ```
 
 NOTE:
-`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
+`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
 
 ### Scope: commits
 
@@ -1146,7 +1146,7 @@ Example response:
 ```
 
 NOTE:
-`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the file name and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
+`filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` will be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521).
 
 ### Scope: users
 
diff --git a/doc/architecture/blueprints/cloud_native_gitlab_pages/index.md b/doc/architecture/blueprints/cloud_native_gitlab_pages/index.md
index 03a4776108a007cd99393f2bf0daddf351903c27..4f929495a12f08db2a490039a4ec2c7230f164ce 100644
--- a/doc/architecture/blueprints/cloud_native_gitlab_pages/index.md
+++ b/doc/architecture/blueprints/cloud_native_gitlab_pages/index.md
@@ -93,7 +93,7 @@ too.
 1. ✓ Redesign GitLab Pages configuration source to use GitLab's API
 1. ✓ Evaluate performance and build reliable caching mechanisms
 1. ✓ Incrementally rollout the new source on GitLab.com
-1. ✓ Make GitLab Pages API domains config source enabled by default
+1. ✓ Make GitLab Pages API domains configuration source enabled by default
 1. Enable experimentation with different servings through feature flags
 1. Triangulate object store serving design through meaningful experiments
 1. Design pages migration mechanisms that can work incrementally
diff --git a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
index cdfb3059181635d549af710dfba77534b2ff9160..6d564010aae8d2e7b770a9b7de9ea9420b86dca0 100644
--- a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
+++ b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
@@ -14,7 +14,7 @@ GitLab CI/CD can be used with Bitbucket Cloud by:
 
 To use GitLab CI/CD with a Bitbucket Cloud repository:
 
-1. In GitLab create a **CI/CD for external repo**, select **Repo by URL** and
+1. In GitLab create a **CI/CD for external repository**, select **Repo by URL** and
    create the project.
 
    ![Create project](img/external_repository.png)
diff --git a/doc/ci/ci_cd_for_external_repos/github_integration.md b/doc/ci/ci_cd_for_external_repos/github_integration.md
index dad54f09e5610bf6721e23659d7a5d77eb4d1a4b..8e3d609b5dc1f0db8a2ed8522660c1032acdc6a0 100644
--- a/doc/ci/ci_cd_for_external_repos/github_integration.md
+++ b/doc/ci/ci_cd_for_external_repos/github_integration.md
@@ -35,7 +35,7 @@ repositories:
    your project, update commit statuses, and create a web hook to notify
    GitLab of new commits.
 
-1. In GitLab, go to the [new project page](../../gitlab-basics/create-project.md#create-a-project-in-gitlab), select the **CI/CD for external repo** tab, and then click
+1. In GitLab, go to the [new project page](../../gitlab-basics/create-project.md#create-a-project-in-gitlab), select the **CI/CD for external repository** tab, and then click
    **GitHub**.
 
 1. Paste the token into the **Personal access token** field and click **List
diff --git a/doc/ci/ci_cd_for_external_repos/index.md b/doc/ci/ci_cd_for_external_repos/index.md
index 1aeeff06265b636f434af11776e5794dd92cd728..44534ddf793d86abcdb0028875a81874d60d81c4 100644
--- a/doc/ci/ci_cd_for_external_repos/index.md
+++ b/doc/ci/ci_cd_for_external_repos/index.md
@@ -26,7 +26,7 @@ snippets disabled. These features
 To connect to an external repository:
 
 1. From your GitLab dashboard, click **New project**.
-1. Switch to the **CI/CD for external repo** tab.
+1. Switch to the **CI/CD for external repository** tab.
 1. Choose **GitHub** or **Repo by URL**.
 1. The next steps are similar to the [import flow](../../user/project/import/index.md).
 
diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md
index 78fde2767ded4dfc75ea4ed51c58346aba9cbcbe..8e5ce2fb35972e172fbcffdb39c12b3c5bb42925 100644
--- a/doc/ci/docker/using_docker_build.md
+++ b/doc/ci/docker/using_docker_build.md
@@ -629,7 +629,7 @@ Then every job that the runner picks up will be authenticated already. If you
 are using the official `docker:19.03.13` image, the home directory is
 under `/root`.
 
-If you mount the config file, any `docker` command
+If you mount the configuration file, any `docker` command
 that modifies the `~/.docker/config.json` (for example, `docker login`)
 fails, because the file is mounted as read-only. Do not change it from
 read-only, because other problems will occur.
@@ -703,7 +703,7 @@ There are multiple ways to define this. For example:
 
 - Inside
   [`pre_build_script`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section)
-  inside of the runner config file.
+  inside of the runner configuration file.
 - Inside [`before_script`](../yaml/README.md#before_script).
 - Inside of [`script`](../yaml/README.md#script).
 
diff --git a/doc/ci/examples/deploy_spring_boot_to_cloud_foundry/index.md b/doc/ci/examples/deploy_spring_boot_to_cloud_foundry/index.md
index 65808f66b48654b054a7817fbd41cc57506497c3..f4f3bf306efb58c76294ab31536a3a89a0708ffc 100644
--- a/doc/ci/examples/deploy_spring_boot_to_cloud_foundry/index.md
+++ b/doc/ci/examples/deploy_spring_boot_to_cloud_foundry/index.md
@@ -16,7 +16,7 @@ Deployment](https://about.gitlab.com/blog/2016/08/05/continuous-integration-deli
 method.
 
 All the code for this project can be found in this [GitLab
-repo](https://gitlab.com/gitlab-examples/spring-gitlab-cf-deploy-demo).
+repository](https://gitlab.com/gitlab-examples/spring-gitlab-cf-deploy-demo).
 
 In case you're interested in deploying Spring Boot applications to Kubernetes
 using GitLab CI/CD, read through the blog post [Continuous Delivery of a Spring Boot application with GitLab CI and Kubernetes](https://about.gitlab.com/blog/2016/12/14/continuous-delivery-of-a-spring-boot-application-with-gitlab-ci-and-kubernetes/).
diff --git a/doc/ci/examples/devops_and_game_dev_with_gitlab_ci_cd/index.md b/doc/ci/examples/devops_and_game_dev_with_gitlab_ci_cd/index.md
index 2405ce31413d2bee84d3fe043a8f592317618416..7abdcf1f9be7f332b92d8f32e280d41cfc2dbf67 100644
--- a/doc/ci/examples/devops_and_game_dev_with_gitlab_ci_cd/index.md
+++ b/doc/ci/examples/devops_and_game_dev_with_gitlab_ci_cd/index.md
@@ -421,7 +421,7 @@ fully understand [IAM Best Practices in AWS](https://docs.aws.amazon.com/IAM/lat
 1. Go to your GitLab project, click **Settings > CI/CD** on the left sidebar
 1. Expand the **Variables** section
 
-   ![GitLab Secret Config](img/gitlab_config.png)
+   ![GitLab Secret Configuration](img/gitlab_config.png)
 
 1. Add a key named `AWS_KEY_ID` and copy the key ID from Step 2 into the **Value** field
 1. Add a key named `AWS_KEY_SECRET` and copy the key secret from Step 2 into the **Value** field
diff --git a/doc/ci/examples/semantic-release.md b/doc/ci/examples/semantic-release.md
index 5d716b571bae34392f5f602b4603dd2ee92dd1fd..70d29b739b1cf6a4651e38ebb3fe0c0131ffdade 100644
--- a/doc/ci/examples/semantic-release.md
+++ b/doc/ci/examples/semantic-release.md
@@ -12,7 +12,7 @@ You can also view or fork the complete [example source](https://gitlab.com/gitla
 
 ## Initialize the module
 
-1. Open a terminal and navigate to the project's repo
+1. Open a terminal and navigate to the project's repository
 1. Run `npm init`. Name the module according to [the Package Registry's naming conventions](../../user/packages/npm_registry/index.md#package-naming-convention). For example, if the project's path is `gitlab-examples/semantic-release-npm`, name the module `@gitlab-examples/semantic-release-npm`.
 
 1. Install the following NPM packages:
@@ -97,7 +97,7 @@ As part of publishing a package, semantic-release increases the version number i
 
 ## Configure semantic-release
 
-semantic-release pulls its configuration info from a `.releaserc.json` file in the project. Create a `.releaserc.json` at the root of the repository:
+semantic-release pulls its configuration information from a `.releaserc.json` file in the project. Create a `.releaserc.json` at the root of the repository:
 
 ```json
 {
diff --git a/doc/ci/quick_start/README.md b/doc/ci/quick_start/README.md
index 1dcd55926968452052c9775e0530847568b51617..7fd88d011b3797e533d6b5199a6c694ee9e91851 100644
--- a/doc/ci/quick_start/README.md
+++ b/doc/ci/quick_start/README.md
@@ -79,7 +79,7 @@ To create a `.gitlab-ci.yml` file:
 
    ![New file](img/new_file_v13_6.png)
 
-1. For the **File name** type `.gitlab-ci.yml` and in the larger window,
+1. For the **Filename**, type `.gitlab-ci.yml` and in the larger window,
    paste this sample code:
 
    ```yaml
diff --git a/doc/ci/yaml/visualization.md b/doc/ci/yaml/visualization.md
index 14502db427f24352322cf6a241fba3496a476def..04ffd304080ed015930e38beed7ccefdc0fbe160 100644
--- a/doc/ci/yaml/visualization.md
+++ b/doc/ci/yaml/visualization.md
@@ -20,11 +20,11 @@ configuration file and click on the `Visualization` tab. The visualization shows
 all stages and jobs. [`needs`](README.md#needs) relationships are displayed as lines
 connecting jobs together, showing the hierarchy of execution:
 
-![CI Config Visualization](img/ci_config_visualization_v13_5.png)
+![CI Configuration Visualization](img/ci_config_visualization_v13_5.png)
 
 Hovering on a job highlights its `needs` relationships:
 
-![CI Config Visualization on hover](img/ci_config_visualization_hover_v13_5.png)
+![CI Configuration Visualization on hover](img/ci_config_visualization_hover_v13_5.png)
 
 If the configuration does not have any `needs` relationships, then no lines are drawn because
 each job depends only on the previous stage being completed successfully.
diff --git a/doc/development/contributing/community_roles.md b/doc/development/contributing/community_roles.md
index b0078ee480f016cad7d821cf4a2bc5153f2edbc2..5419992517b03bfc4c9a33003cf69f5c58c73ec6 100644
--- a/doc/development/contributing/community_roles.md
+++ b/doc/development/contributing/community_roles.md
@@ -10,7 +10,7 @@ GitLab community members and their privileges/responsibilities.
 
 | Roles | Responsibilities | Requirements |
 |-------|------------------|--------------|
-| Maintainer | Accepts merge requests on several GitLab projects | Added to the [team page](https://about.gitlab.com/company/team/). An expert on code reviews and knows the product/code base |
+| Maintainer | Accepts merge requests on several GitLab projects | Added to the [team page](https://about.gitlab.com/company/team/). An expert on code reviews and knows the product/codebase |
 | Reviewer | Performs code reviews on MRs | Added to the [team page](https://about.gitlab.com/company/team/) |
 | Developer |Has access to GitLab internal infrastructure & issues (e.g. HR-related) | GitLab employee or a Core Team member (with an NDA) |
 | Contributor | Can make contributions to all GitLab public projects | Have a GitLab.com account |
diff --git a/doc/development/database/strings_and_the_text_data_type.md b/doc/development/database/strings_and_the_text_data_type.md
index d770a0622992918ec8e5e3459080dc5da1b5dacd..8b839e929c7c0674050fa1d4fd869d428a2e8185 100644
--- a/doc/development/database/strings_and_the_text_data_type.md
+++ b/doc/development/database/strings_and_the_text_data_type.md
@@ -17,7 +17,7 @@ The `text` data type can not be defined with a limit, so `add_text_limit` is enf
 adding a [check constraint](https://www.postgresql.org/docs/11/ddl-constraints.html) on the
 column and then validating it at a followup step.
 
-## Background info
+## Background information
 
 The reason we always want to use `text` instead of `string` is that `string` columns have the
 disadvantage that if you want to update their limit, you have to run an `ALTER TABLE ...` command.
@@ -256,7 +256,7 @@ end
 
 To keep this guide short, we skipped the definition of the background migration and only
 provided a high level example of the post-deployment migration that is used to schedule the batches.
-You can find more info on the guide about [background migrations](../background_migrations.md)
+You can find more information on the guide about [background migrations](../background_migrations.md)
 
 #### Validate the text limit (next release)
 
diff --git a/doc/development/database_review.md b/doc/development/database_review.md
index 504f90b29d3141e628f9b383a516ba099f52f93c..f3422e8cfd307de3e7c22cce032cd1e1b1f3c498 100644
--- a/doc/development/database_review.md
+++ b/doc/development/database_review.md
@@ -153,7 +153,7 @@ test its execution using `CREATE INDEX CONCURRENTLY` in the `#database-lab` Slac
    projects provide enough data to serve as a good example.
   - That means that no query plan should return 0 records or less records than the provided limit (if a limit is included). If a query is used in batching, a proper example batch with adequate included results should be identified and provided.
   - If your queries belong to a new feature in GitLab.com and thus they don't return data in production, it's suggested to analyze the query and to provide the plan from a local environment.
-  - More info on how to find the number of actual returned records in [Understanding EXPLAIN plans](understanding_explain_plans.md)
+  - More information on how to find the number of actual returned records in [Understanding EXPLAIN plans](understanding_explain_plans.md)
 - For query changes, it is best to provide both the SQL queries along with the
   plan _before_ and _after_ the change. This helps spot differences quickly.
 - Include data that shows the performance improvement, preferably in
diff --git a/doc/development/diffs.md b/doc/development/diffs.md
index 105fec10fcd246af3776b9ce2efc3a9edd419ff4..f1f165f48c4f5132a27b3e8eff425bd0f6e0a628 100644
--- a/doc/development/diffs.md
+++ b/doc/development/diffs.md
@@ -14,7 +14,14 @@ Currently we rely on different sources to present diffs, these include:
 
 ## Deep Dive
 
-In January 2019, Oswaldo Ferreira hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`) on GitLab's Diffs and Commenting on Diffs functionality to share his domain specific knowledge with anyone who may work in this part of the code base in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=K6G3gMcFyek), and the slides on [Google Slides](https://docs.google.com/presentation/d/1bGutFH2AT3bxOPZuLMGl1ANWHqFnrxwQwjiwAZkF-TU/edit) and in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/b5ad2f336e0afcfe0f99db0af0ccc71a/). Everything covered in this deep dive was accurate as of GitLab 11.7, and while specific details may have changed since then, it should still serve as a good introduction.
+In January 2019, Oswaldo Ferreira hosted a Deep Dive (GitLab team members only:
+`https://gitlab.com/gitlab-org/create-stage/issues/1`) on GitLab's Diffs and Commenting on Diffs
+functionality to share his domain specific knowledge with anyone who may work in this part of the
+codebase in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=K6G3gMcFyek),
+and the slides on [Google Slides](https://docs.google.com/presentation/d/1bGutFH2AT3bxOPZuLMGl1ANWHqFnrxwQwjiwAZkF-TU/edit)
+and in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/b5ad2f336e0afcfe0f99db0af0ccc71a/).
+Everything covered in this deep dive was accurate as of GitLab 11.7, and while specific details may
+have changed since then, it should still serve as a good introduction.
 
 ## Architecture overview
 
diff --git a/doc/development/documentation/index.md b/doc/development/documentation/index.md
index e59990d792a1f380cacc0e2d75c883ab998a14fa..5fb5e9b433a4eb4bbc330bf3b448451076386aeb 100644
--- a/doc/development/documentation/index.md
+++ b/doc/development/documentation/index.md
@@ -253,7 +253,7 @@ available under `https://docs.gitlab.com/my-old-location/README.html` to a new l
 `https://docs.gitlab.com/my-new-location/index.html`.
 
 Into the **new document** front matter, we add the following information. You must
-include the file name in the `disqus_identifier` URL, even if it's `index.html` or `README.html`.
+include the filename in the `disqus_identifier` URL, even if it's `index.html` or `README.html`.
 
 ```yaml
 ---
@@ -498,7 +498,7 @@ To run the tool on an existing screenshot generator, take the following steps:
 1. Set up the [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/gitlab_docs.md).
 1. Navigate to the subdirectory with your cloned GitLab repository, typically `gdk/gitlab`.
 1. Make sure that your GDK database is fully migrated: `bin/rake db:migrate RAILS_ENV=development`.
-1. Install pngquant, see the tool website for more info: [`pngquant`](https://pngquant.org/)
+1. Install pngquant, see the tool website for more information: [`pngquant`](https://pngquant.org/)
 1. Run `scripts/docs_screenshots.rb spec/docs_screenshots/<name_of_screenshot_generator>.rb <milestone-version>`.
 1. Identify the location of the screenshots, based on the `gitlab/doc` location defined by the `it` parameter in your script.
 1. Commit the newly created screenshots.
diff --git a/doc/development/documentation/structure.md b/doc/development/documentation/structure.md
index d73494699cb7400d946c5ef3fb85a81827ebb0f6..fd0c29f0fc1f84a4387039158c31e1848293f4a7 100644
--- a/doc/development/documentation/structure.md
+++ b/doc/development/documentation/structure.md
@@ -39,7 +39,7 @@ pre-deployment and post-deployment tasks.
 
 ## Template for new docs
 
-Follow the [folder structure and file name guidelines](styleguide/index.md#folder-structure-overview)
+Follow the [folder structure and filename guidelines](styleguide/index.md#folder-structure-overview)
 and create a new topic by using this template:
 
 ```markdown
diff --git a/doc/development/documentation/testing.md b/doc/development/documentation/testing.md
index ce02c01d8745db0de9e775bbe75202d9211ff6e5..5ec79d48e5dd1f7d40d0470ffbe501896f295375 100644
--- a/doc/development/documentation/testing.md
+++ b/doc/development/documentation/testing.md
@@ -225,9 +225,9 @@ To match the versions of `markdownlint-cli` and `vale` used in the GitLab projec
 [versions used](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/master/.gitlab-ci.yml#L447)
 when building the `image:docs-lint-markdown` Docker image containing these tools for CI/CD.
 
-| Tool               | Version  | Command                                   | Additional info |
-|--------------------|----------|-------------------------------------------|-----------------|
-| `markdownlint-cli` | Latest   | `yarn global add markdownlint-cli`        | n/a             |
+| Tool               | Version  | Command                                   | Additional information |
+|--------------------|----------|-------------------------------------------|------------------------|
+| `markdownlint-cli` | Latest   | `yarn global add markdownlint-cli`        | n/a                    |
 | `markdownlint-cli` | Specfic  | `yarn global add markdownlint-cli@0.23.2` | The `@` indicates a specific version, and this example updates the tool to version `0.23.2`. |
 | Vale               | Latest   | `brew update && brew upgrade vale`        | This command is for macOS only. |
 | Vale               | Specific | n/a                                       | Not possible using `brew`, but can be [directly downloaded](https://github.com/errata-ai/vale/releases). |
diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md
index bf7ab8096adefe51b070fcf01cb2f167c2f92063..60d0d682e3eb9e57da0cf5df66061ac670bd3f47 100644
--- a/doc/development/elasticsearch.md
+++ b/doc/development/elasticsearch.md
@@ -13,7 +13,7 @@ the [Elasticsearch integration documentation](../integration/elasticsearch.md#en
 
 ## Deep Dive
 
-In June 2019, Mario de la Ossa hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`) on GitLab's [Elasticsearch integration](../integration/elasticsearch.md) to share his domain specific knowledge with anyone who may work in this part of the code base in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=vrvl-tN2EaA), and the slides on [Google Slides](https://docs.google.com/presentation/d/1H-pCzI_LNrgrL5pJAIQgvLX8Ji0-jIKOg1QeJQzChug/edit) and in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/c5aa32b6b07476fa8b597004899ec538/Elasticsearch_Deep_Dive.pdf). Everything covered in this deep dive was accurate as of GitLab 12.0, and while specific details may have changed since then, it should still serve as a good introduction.
+In June 2019, Mario de la Ossa hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`) on GitLab's [Elasticsearch integration](../integration/elasticsearch.md) to share his domain specific knowledge with anyone who may work in this part of the codebase in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=vrvl-tN2EaA), and the slides on [Google Slides](https://docs.google.com/presentation/d/1H-pCzI_LNrgrL5pJAIQgvLX8Ji0-jIKOg1QeJQzChug/edit) and in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/c5aa32b6b07476fa8b597004899ec538/Elasticsearch_Deep_Dive.pdf). Everything covered in this deep dive was accurate as of GitLab 12.0, and while specific details may have changed since then, it should still serve as a good introduction.
 
 In August 2020, a second Deep Dive was hosted, focusing on [GitLab's specific architecture for multi-indices support](#zero-downtime-reindexing-with-multiple-indices). The [recording on YouTube](https://www.youtube.com/watch?v=0WdPR9oB2fg) and the [slides](https://lulalala.gitlab.io/gitlab-elasticsearch-deepdive/) are available. Everything covered in this deep dive was accurate as of GitLab 13.3.
 
@@ -192,7 +192,7 @@ NOTE:
 This only supported for indices created with GitLab 13.0 or greater.
 
 Migrations are stored in the [`ee/elastic/migrate/`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/ee/elastic/migrate) folder with `YYYYMMDDHHMMSS_migration_name.rb`
-file name format, which is similar to Rails database migrations:
+filename format, which is similar to Rails database migrations:
 
 ```ruby
 # frozen_string_literal: true
diff --git a/doc/development/fe_guide/droplab/droplab.md b/doc/development/fe_guide/droplab/droplab.md
index 903efcd4ba7d51d4fda19718ec1c1ed57bf4652f..85d94d7e5883ec6a3896d1ac8c4eb8064e80c170 100644
--- a/doc/development/fe_guide/droplab/droplab.md
+++ b/doc/development/fe_guide/droplab/droplab.md
@@ -234,7 +234,7 @@ If no modules API is detected, the library will fall back as it does with
 
 To use plugins, you can pass them in an array as the third argument of
 `DropLab.prototype.init` or `DropLab.prototype.addHook`. Some plugins require
-configuration values; the config object can be passed as the fourth argument.
+configuration values; the configuration object can be passed as the fourth argument.
 
 ```html
 <a href="#" id="trigger" data-dropdown-trigger="#list">Toggle</a>
diff --git a/doc/development/fe_guide/editor_lite.md b/doc/development/fe_guide/editor_lite.md
index e758631039eb86dc94a40fb9292ee956ef501b7b..465d64ff63c0717494f309ffd946734896b64854 100644
--- a/doc/development/fe_guide/editor_lite.md
+++ b/doc/development/fe_guide/editor_lite.md
@@ -68,7 +68,7 @@ The editor follows the same public API as [provided by Monaco editor](https://mi
 Editor Lite comes with the loading state built-in, making spinners and loaders rarely needed in HTML. To benefit the built-in loading state, set the `data-editor-loading` property on the HTML element that is supposed to contain the editor. Editor Lite will show the loader automatically while it's bootstrapping.
 ![Editor Lite: loading state](img/editor_lite_loading.png)
 
-1. Update syntax highlighting if the file name changes.
+1. Update syntax highlighting if the filename changes.
 
 ```javascript
 // fileNameEl here is the HTML input element that contains the file name
diff --git a/doc/development/fe_guide/graphql.md b/doc/development/fe_guide/graphql.md
index cad5fd75bec0dfa5df7318b63716c4eb7bb05676..35b3f9d7d14f083dbf4b908d0f3a66d65636c4a5 100644
--- a/doc/development/fe_guide/graphql.md
+++ b/doc/development/fe_guide/graphql.md
@@ -187,7 +187,7 @@ As shown in the code example by using `produce`, we can perform any kind of dire
 `draftState`. Besides, `immer` guarantees that a new state which includes the changes to `draftState` will be generated.
 
 Finally, to verify whether the immutable cache update is working properly, we need to change
-`assumeImmutableResults` to `true` in the `default client config` (see [Apollo Client](#apollo-client) for more info).
+`assumeImmutableResults` to `true` in the default client configuration (see [Apollo Client](#apollo-client) for more information).
 
 If everything is working properly `assumeImmutableResults` should remain set to `true`.
 
diff --git a/doc/development/feature_flags/controls.md b/doc/development/feature_flags/controls.md
index 7d89cde424553b2d17626c661ab6c44702263dc5..7551199aa584135f81dadb6159d214396ac84462 100644
--- a/doc/development/feature_flags/controls.md
+++ b/doc/development/feature_flags/controls.md
@@ -274,7 +274,7 @@ To remove a feature flag:
 
 ### Cleanup ChatOps
 
-When a feature gate has been removed from the code base, the feature
+When a feature gate has been removed from the codebase, the feature
 record still exists in the database that the flag was deployed too.
 The record can be deleted once the MR is deployed to each environment:
 
diff --git a/doc/development/geo.md b/doc/development/geo.md
index 767bf3fbe0174f04b5f3421d2a3b19df47ad3ed0..ed1837f95644d90fecc2cbf6c1caa25f8f83c64b 100644
--- a/doc/development/geo.md
+++ b/doc/development/geo.md
@@ -102,7 +102,7 @@ projects that need updating. Those projects can be:
 When we fail to fetch a repository on the secondary `RETRIES_BEFORE_REDOWNLOAD`
 times, Geo does a so-called _re-download_. It will do a clean clone
 into the `@geo-temporary` directory in the root of the storage. When
-it's successful, we replace the main repo with the newly cloned one.
+it's successful, we replace the main repository with the newly cloned one.
 
 ### Uploads replication
 
diff --git a/doc/development/git_object_deduplication.md b/doc/development/git_object_deduplication.md
index 11ffcd709684d9e91bbbedb77ca6bb152a090913..00993cc2932a8d6bd2074c0b0d7504a6fb9404fd 100644
--- a/doc/development/git_object_deduplication.md
+++ b/doc/development/git_object_deduplication.md
@@ -170,18 +170,18 @@ the fly by Gitaly.
 
 There are three different things that can go wrong here.
 
-#### 1. SQL says repo A belongs to pool P but Gitaly says A has no alternate objects
+#### 1. SQL says repository A belongs to pool P but Gitaly says A has no alternate objects
 
 In this case, we miss out on disk space savings but all RPC's on A
 itself function fine. The next time garbage collection runs on A,
 the alternates connection gets established in Gitaly. This is done by
 `Projects::GitDeduplicationService` in GitLab Rails.
 
-#### 2. SQL says repo A belongs to pool P1 but Gitaly says A has alternate objects in pool P2
+#### 2. SQL says repository A belongs to pool P1 but Gitaly says A has alternate objects in pool P2
 
 In this case `Projects::GitDeduplicationService` throws an exception.
 
-#### 3. SQL says repo A does not belong to any pool but Gitaly says A belongs to P
+#### 3. SQL says repository A does not belong to any pool but Gitaly says A belongs to P
 
 In this case `Projects::GitDeduplicationService` tries to
 "re-duplicate" the repository A using the DisconnectGitAlternates RPC.
diff --git a/doc/development/gitaly.md b/doc/development/gitaly.md
index b885b8459e41d6796d705e0fcb940c085252262c..3d1568c7f49a43b05bd835dd73e1669d020de3e8 100644
--- a/doc/development/gitaly.md
+++ b/doc/development/gitaly.md
@@ -15,7 +15,7 @@ Workhorse and GitLab Shell.
 In May 2019, Bob Van Landuyt hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`)
 on GitLab's [Gitaly project](https://gitlab.com/gitlab-org/gitaly) and how to contribute to it as a
 Ruby developer, to share his domain specific knowledge with anyone who may work in this part of the
-code base in the future.
+codebase in the future.
 
 You can find the [recording on YouTube](https://www.youtube.com/watch?v=BmlEWFS8ORo), and the slides
 on [Google Slides](https://docs.google.com/presentation/d/1VgRbiYih9ODhcPnL8dS0W98EwFYpJ7GXMPpX-1TM6YE/edit)
diff --git a/doc/development/gotchas.md b/doc/development/gotchas.md
index 2f8ff826358b31ef320504ec0dca3589f2ff9b88..2b34aedddf652ba7978a36633f7429eaf1b7a49c 100644
--- a/doc/development/gotchas.md
+++ b/doc/development/gotchas.md
@@ -292,7 +292,7 @@ While the code above works in local environments, it errors out in production in
 
 ### Solution
 
-The alternative is the `lib/assets` folder. Use it if you need to add assets (like images) to the repo that meet the following conditions:
+The alternative is the `lib/assets` folder. Use it if you need to add assets (like images) to the repository that meet the following conditions:
 
 - The assets do not need to be directly served to the user (and hence need not be pre-compiled).
 - The assets do need to be accessed via application code.
diff --git a/doc/development/integrations/secure.md b/doc/development/integrations/secure.md
index d9a54b5ab7f918106d1f5eda8a74418963c2a26c..96e201e6ce706b59153d2b2b61d5629591e06941 100644
--- a/doc/development/integrations/secure.md
+++ b/doc/development/integrations/secure.md
@@ -82,9 +82,9 @@ mysec_sast:
       sast: gl-sast-report.json
 ```
 
-Note that `gl-sast-report.json` is an example file path but any other file name can be used. See
+Note that `gl-sast-report.json` is an example file path but any other filename can be used. See
 [the Output file section](#output-file) for more details. It's processed as a SAST report because
-it's declared under the `reports:sast` key in the job definition, not because of the file name.
+it's declared under the `reports:sast` key in the job definition, not because of the filename.
 
 ### Policies
 
@@ -207,12 +207,12 @@ given by the `CI_PROJECT_DIR` environment variable.
 
 It is recommended to name the output file after the type of scanning, and to use `gl-` as a prefix.
 Since all Secure reports are JSON files, it is recommended to use `.json` as a file extension.
-For instance, a suggested file name for a Dependency Scanning report is `gl-dependency-scanning.json`.
+For instance, a suggested filename for a Dependency Scanning report is `gl-dependency-scanning.json`.
 
 The [`artifacts:reports`](../../ci/pipelines/job_artifacts.md#artifactsreports) keyword
 of the job definition must be consistent with the file path where the Security report is written.
 For instance, if a Dependency Scanning analyzer writes its report to the CI project directory,
-and if this report file name is `depscan.json`,
+and if this report filename is `depscan.json`,
 then `artifacts:reports:dependency_scanning` must be set to `depscan.json`.
 
 ### Exit code
diff --git a/doc/development/iterating_tables_in_batches.md b/doc/development/iterating_tables_in_batches.md
index 45f76bfa2b0da7a9fa1c224c78ae4996cde12f12..3953e7097dd231c886609b398fd55d88b1db4362 100644
--- a/doc/development/iterating_tables_in_batches.md
+++ b/doc/development/iterating_tables_in_batches.md
@@ -61,7 +61,9 @@ In case the column is not unique (no unique index definition), calling the `dist
 
 When dealing with data migrations the preferred way to iterate over large volume of data is using `EachBatch`.
 
-A special case of data migration is a background migration where the actual data modification is executed in a background job. The migration code that determines the data ranges (slices) and schedules the background jobs uses `each_batch`. More info: [background migration scheduling](background_migrations.md#scheduling)
+A special case of data migration is a [background migration](background_migrations.md#scheduling)
+where the actual data modification is executed in a background job. The migration code that determines
+the data ranges (slices) and schedules the background jobs uses `each_batch`.
 
 ## Efficient usage of `each_batch`
 
diff --git a/doc/development/lfs.md b/doc/development/lfs.md
index d4324c28a01514edcb2e8bce5d4485e07b29fc5f..34ad09ad732658afb55b9feb322cd91714d20e6d 100644
--- a/doc/development/lfs.md
+++ b/doc/development/lfs.md
@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 In April 2019, Francisco Javier López hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`)
 on GitLab's [Git LFS](../topics/git/lfs/index.md) implementation to share his domain
-specific knowledge with anyone who may work in this part of the code base in the future.
+specific knowledge with anyone who may work in this part of the codebase in the future.
 You can find the [recording on YouTube](https://www.youtube.com/watch?v=Yyxwcksr0Qc),
 and the slides on [Google Slides](https://docs.google.com/presentation/d/1E-aw6-z0rYd0346YhIWE7E9A65zISL9iIMAOq2zaw9E/edit)
 and in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/07a89257a140db067bdfb484aecd35e1/Git_LFS_Deep_Dive__Create_.pdf).
diff --git a/doc/development/logging.md b/doc/development/logging.md
index f6c1e0835baa26fff63afff965e927e1a7b81f49..07ec9d53145197855a130fa25f36254a05a8de1f 100644
--- a/doc/development/logging.md
+++ b/doc/development/logging.md
@@ -12,7 +12,7 @@ administrators and GitLab team members to diagnose problems in the field.
 ## Don't use `Rails.logger`
 
 Currently `Rails.logger` calls all get saved into `production.log`, which contains
-a mix of Rails' logs and other calls developers have inserted in the code base.
+a mix of Rails' logs and other calls developers have inserted in the codebase.
 For example:
 
 ```plaintext
diff --git a/doc/development/pipelines.md b/doc/development/pipelines.md
index 16625f20ea8552b9006d0e3458611b07cde03a84..b4a3cbd028cd84256d9a0cfc675614e4fbea7bbb 100644
--- a/doc/development/pipelines.md
+++ b/doc/development/pipelines.md
@@ -697,10 +697,10 @@ and included in `rules` definitions via [YAML anchors](../ci/yaml/README.md#anch
 
 | `changes:` patterns          | Description                                                              |
 |------------------------------|--------------------------------------------------------------------------|
-| `ci-patterns`                | Only create job for CI config-related changes.                           |
-| `ci-build-images-patterns`   | Only create job for CI config-related changes related to the `build-images` stage. |
-| `ci-review-patterns`         | Only create job for CI config-related changes related to the `review` stage. |
-| `ci-qa-patterns`             | Only create job for CI config-related changes related to the `qa` stage. |
+| `ci-patterns`                | Only create job for CI configuration-related changes.                    |
+| `ci-build-images-patterns`   | Only create job for CI configuration-related changes related to the `build-images` stage. |
+| `ci-review-patterns`         | Only create job for CI configuration-related changes related to the `review` stage. |
+| `ci-qa-patterns`             | Only create job for CI configuration-related changes related to the `qa` stage. |
 | `yaml-lint-patterns`         | Only create job for YAML-related changes.                                |
 | `docs-patterns`              | Only create job for docs-related changes.                                |
 | `frontend-dependency-patterns` | Only create job when frontend dependencies are updated (i.e. `package.json`, and `yarn.lock`). changes. |
diff --git a/doc/development/python_guide/index.md b/doc/development/python_guide/index.md
index adb73edd3525dce8582a9d16ccd60d3ba39d2ff4..3291b6c31a99217a47ab414d900f22deb9be2baf 100644
--- a/doc/development/python_guide/index.md
+++ b/doc/development/python_guide/index.md
@@ -33,7 +33,7 @@ To install `pyenv` on Linux, you can run the command below:
 curl "https://pyenv.run" | bash
 ```
 
-Alternatively, you may find `pyenv` available as a system package via your distro package manager.
+Alternatively, you may find `pyenv` available as a system package via your distribution's package manager.
 
 You can read more about it in: <https://github.com/pyenv/pyenv-installer#prerequisites>.
 
diff --git a/doc/development/renaming_features.md b/doc/development/renaming_features.md
index 94fea651d47d9f43d5279cc940372a388f59165c..2a94fd2cbc3fdf1f3d45a685e2fc1709264ea6cc 100644
--- a/doc/development/renaming_features.md
+++ b/doc/development/renaming_features.md
@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 Sometimes the business asks to change the name of a feature. Broadly speaking, there are 2 approaches to that task. They basically trade between immediate effort and future complexity/bug risk:
 
-- Complete, rename everything in the repo.
+- Complete, rename everything in the repository.
   - Pros: does not increase code complexity.
   - Cons: more work to execute, and higher risk of immediate bugs.
 - Façade, rename as little as possible; only the user-facing content like interfaces,
diff --git a/doc/development/repository_mirroring.md b/doc/development/repository_mirroring.md
index ef0a4ae8de90de57df1f5005cb59d148637951bc..f69ca5d5ce34ad3c90f654e64c195197379ab0cf 100644
--- a/doc/development/repository_mirroring.md
+++ b/doc/development/repository_mirroring.md
@@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 In December 2018, Tiago Botelho hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`)
 on GitLab's [Pull Repository Mirroring functionality](../user/project/repository/repository_mirroring.md#pulling-from-a-remote-repository)
 to share his domain specific knowledge with anyone who may work in this part of the
-code base in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=sSZq0fpdY-Y),
+codebase in the future. You can find the [recording on YouTube](https://www.youtube.com/watch?v=sSZq0fpdY-Y),
 and the slides in [PDF](https://gitlab.com/gitlab-org/create-stage/uploads/8693404888a941fd851f8a8ecdec9675/Gitlab_Create_-_Pull_Mirroring_Deep_Dive.pdf).
 Everything covered in this deep dive was accurate as of GitLab 11.6, and while specific
 details may have changed since then, it should still serve as a good introduction.
diff --git a/doc/development/scalability.md b/doc/development/scalability.md
index 78922e550e97d0dfea2e92134fce5fce62bbe86d..a9b8fb4389ffa0a94c5f32a0516b006207abc574 100644
--- a/doc/development/scalability.md
+++ b/doc/development/scalability.md
@@ -251,7 +251,7 @@ The full list of jobs can be found in the
 [`app/workers`](https://gitlab.com/gitlab-org/gitlab/tree/master/app/workers)
 and
 [`ee/app/workers`](https://gitlab.com/gitlab-org/gitlab/tree/master/ee/app/workers)
-directories in the GitLab code base.
+directories in the GitLab codebase.
 
 #### Runaway Queues
 
diff --git a/doc/development/secure_coding_guidelines.md b/doc/development/secure_coding_guidelines.md
index 95145a75f1fbdae63b5610c5c9b6f324bce3534d..44a95f6e820243638305970108a335eca9bffb4d 100644
--- a/doc/development/secure_coding_guidelines.md
+++ b/doc/development/secure_coding_guidelines.md
@@ -121,7 +121,7 @@ For example when the regex `.*!$` matches the string `hello!`, the `.*` first ma
 the entire string but then the `!` from the regex is unable to match because the
 character has already been used. In that case, the Ruby regex engine _backtracks_
 one character to allow the `!` to match.
- 
+
 [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS)
 is an attack in which the attacker knows or controls the regular expression used.
 The attacker may be able to enter user input that triggers this backtracking behavior in a
@@ -331,7 +331,7 @@ Once you've [determined when and where](#setting-expectations) the user submitte
 - Content placed inside [HTML URL GET parameters](https://youtu.be/2VFavqfDS6w?t=3494) need to be [URL-encoded](https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html#rule-5---url-escape-before-inserting-untrusted-data-into-html-url-parameter-values)
 - [Additional contexts may require context-specific encoding](https://youtu.be/2VFavqfDS6w?t=2341).
 
-### Additional info
+### Additional information
 
 #### XSS mitigation and prevention in Rails
 
@@ -590,4 +590,3 @@ In order to prevent this from happening, it is recommended to use the method `us
           forbidden!(api_access_denied_message(user))
         end
 ```
-  
\ No newline at end of file
diff --git a/doc/development/testing_guide/testing_migrations_guide.md b/doc/development/testing_guide/testing_migrations_guide.md
index cdce711c36e93b6cb22c1a3c77be091a45f99a0f..9844754cd974118b6af3a63b1fac7600ddf661d8 100644
--- a/doc/development/testing_guide/testing_migrations_guide.md
+++ b/doc/development/testing_guide/testing_migrations_guide.md
@@ -59,13 +59,13 @@ RSpec.describe ...
 
 Since the migration files are not autoloaded by Rails, you will need to manually
 load the migration file. To do so, you can use the `require_migration!` helper method
-which can automatically load the correct migration file based on the spec file name.
+which can automatically load the correct migration file based on the spec filename.
 
 For example, if your spec file is named as `populate_foo_column_spec.rb` then the
 helper method will try to load `${schema_version}_populate_foo_column.rb` migration file.
 
 In case there is no pattern between your spec file and the actual migration file,
-you can provide the migration file name without the schema version, like so:
+you can provide the migration filename without the schema version, like so:
 
 ```ruby
 require_migration!('populate_foo_column')
diff --git a/doc/gitlab-basics/start-using-git.md b/doc/gitlab-basics/start-using-git.md
index ea8a58154db85592b332f27ad52c70e407b794ed..ac8ea6161dd9f04aea205bd282561c3f74524eb4 100644
--- a/doc/gitlab-basics/start-using-git.md
+++ b/doc/gitlab-basics/start-using-git.md
@@ -104,7 +104,7 @@ If you omit `--global` or use `--local`, the configuration will be applied only
 repository.
 
 You can read more on how Git manages configurations in the
-[Git Config](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) documentation.
+[Git configuration documentation](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration).
 
 ## Git authentication methods
 
@@ -183,7 +183,7 @@ changes to GitLab. This is referred to as **pushing** to GitLab, as this is achi
 [`git push`](#send-changes-to-gitlabcom).
 
 When the remote repository changes, your local copy will be behind it. You can update it with the new
-changes in the remote repo.
+changes in the remote repository.
 This is referred to as **pulling** from GitLab, as this is achieved by the command
 [`git pull`](#download-the-latest-changes-in-the-project).
 
diff --git a/doc/install/aws/index.md b/doc/install/aws/index.md
index 49916035616ff62dc7c1d99309d6190038f05b69..54a1c831fa2b0bb619d9cbd3f02b35c5063a65d7 100644
--- a/doc/install/aws/index.md
+++ b/doc/install/aws/index.md
@@ -63,7 +63,7 @@ Here's a list of the AWS services we will use, with links to pricing information
 
 ## Create an IAM EC2 instance role and profile
 
-As we'll be using [Amazon S3 object storage](#amazon-s3-object-storage), our EC2 instances need to have read, write, and list permissions for our S3 buckets. To avoid embedding AWS keys in our GitLab config, we'll make use of an [IAM Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) to allow our GitLab instance with this access. We'll need to create an IAM policy to attach to our IAM role:
+As we'll be using [Amazon S3 object storage](#amazon-s3-object-storage), our EC2 instances need to have read, write, and list permissions for our S3 buckets. To avoid embedding AWS keys in our GitLab configuration, we'll make use of an [IAM Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) to allow our GitLab instance with this access. We'll need to create an IAM policy to attach to our IAM role:
 
 ### Create an IAM Policy
 
diff --git a/doc/install/google_cloud_platform/index.md b/doc/install/google_cloud_platform/index.md
index c895cd26e0bc47044ad40f2d05d3edfcdd7cd57e..22f32d69c020c1cd658c17d78b758f172301e3c2 100644
--- a/doc/install/google_cloud_platform/index.md
+++ b/doc/install/google_cloud_platform/index.md
@@ -91,7 +91,7 @@ here's how you configure GitLab to be aware of the change:
    In the future you might want to set up [connecting with an SSH key](https://cloud.google.com/compute/docs/instances/connecting-to-instance)
    instead.
 
-1. Edit the config file of Omnibus GitLab using your favorite text editor:
+1. Edit the configuration file of Omnibus GitLab using your favorite text editor:
 
    ```shell
    sudo vim /etc/gitlab/gitlab.rb
diff --git a/doc/install/installation.md b/doc/install/installation.md
index 6bfd83fcddfa618b1a8e47b11f037e0d83908242..80b3914addab15bb1c5407ad4b99b225f49aece4 100644
--- a/doc/install/installation.md
+++ b/doc/install/installation.md
@@ -773,14 +773,14 @@ sudo apt-get install -y nginx
 
 ### Site Configuration
 
-Copy the example site config:
+Copy the example site configuration:
 
 ```shell
 sudo cp lib/support/nginx/gitlab /etc/nginx/sites-available/gitlab
 sudo ln -s /etc/nginx/sites-available/gitlab /etc/nginx/sites-enabled/gitlab
 ```
 
-Make sure to edit the config file to match your setup. Also, ensure that you match your paths to GitLab, especially if installing for a user other than the `git` user:
+Make sure to edit the configuration file to match your setup. Also, ensure that you match your paths to GitLab, especially if installing for a user other than the `git` user:
 
 ```shell
 # Change YOUR_SERVER_FQDN to the fully-qualified
@@ -795,21 +795,21 @@ Make sure to edit the config file to match your setup. Also, ensure that you mat
 sudo editor /etc/nginx/sites-available/gitlab
 ```
 
-If you intend to enable GitLab Pages, there is a separate NGINX config you need
+If you intend to enable GitLab Pages, there is a separate NGINX configuration you need
 to use. Read all about the needed configuration at the
 [GitLab Pages administration guide](../administration/pages/index.md).
 
-If you want to use HTTPS, replace the `gitlab` NGINX config with `gitlab-ssl`. See [Using HTTPS](#using-https) for HTTPS configuration details.
+If you want to use HTTPS, replace the `gitlab` NGINX configuration with `gitlab-ssl`. See [Using HTTPS](#using-https) for HTTPS configuration details.
 
 ### Test Configuration
 
-Validate your `gitlab` or `gitlab-ssl` NGINX config file with the following command:
+Validate your `gitlab` or `gitlab-ssl` NGINX configuration file with the following command:
 
 ```shell
 sudo nginx -t
 ```
 
-You should receive `syntax is okay` and `test is successful` messages. If you receive errors check your `gitlab` or `gitlab-ssl` NGINX config file for typos, etc. as indicated in the error message given.
+You should receive `syntax is okay` and `test is successful` messages. If you receive errors check your `gitlab` or `gitlab-ssl` NGINX configuration file for typos, etc. as indicated in the error message given.
 
 Verify that the installed version is greater than 1.12.1:
 
@@ -878,7 +878,7 @@ To use GitLab with HTTPS:
 1. In the `config.yml` of GitLab Shell:
    1. Set `gitlab_url` option to the HTTPS endpoint of GitLab (e.g. `https://git.example.com`).
    1. Set the certificates using either the `ca_file` or `ca_path` option.
-1. Use the `gitlab-ssl` NGINX example config instead of the `gitlab` config.
+1. Use the `gitlab-ssl` NGINX example configuration instead of the `gitlab` configuration.
    1. Update `YOUR_SERVER_FQDN`.
    1. Update `ssl_certificate` and `ssl_certificate_key`.
    1. Review the configuration file and consider applying other security and performance enhancing features.
@@ -951,7 +951,7 @@ production:
 
 ### Custom SSH Connection
 
-If you are running SSH on a non-standard port, you must change the GitLab user's SSH config.
+If you are running SSH on a non-standard port, you must change the GitLab user's SSH configuration.
 
 ```plaintext
 # Add to /home/git/.ssh/config
@@ -973,7 +973,7 @@ As of GitLab 12.9, [Puma](https://github.com/puma/puma) has replaced Unicorn as
 If you want to switch back to Unicorn, follow these steps:
 
 1. Finish the GitLab setup so you have it up and running.
-1. Copy the supplied example Unicorn config file into place:
+1. Copy the supplied example Unicorn configuration file into place:
 
    ```shell
    cd /home/git/gitlab
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 39a5c3d5c2700e65a955dfbd24c3d970873e948f..f495b7114ee3c7b2964fa907f93ee526b758c4bb 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -111,7 +111,7 @@ Since file system performance may affect GitLab's overall performance, [we don't
 
 ### CPU
 
-CPU requirements are dependent on the number of users and expected workload. Your exact needs may be more, depending on your workload. Your workload is influenced by factors such as - but not limited to - how active your users are, how much automation you use, mirroring, and repo/change size.
+CPU requirements are dependent on the number of users and expected workload. Your exact needs may be more, depending on your workload. Your workload is influenced by factors such as - but not limited to - how active your users are, how much automation you use, mirroring, and repository/change size.
 
 The following is the recommended minimum CPU hardware guidance for a handful of example GitLab user base sizes.
 
@@ -121,7 +121,7 @@ The following is the recommended minimum CPU hardware guidance for a handful of
 
 ### Memory
 
-Memory requirements are dependent on the number of users and expected workload. Your exact needs may be more, depending on your workload. Your workload is influenced by factors such as - but not limited to - how active your users are, how much automation you use, mirroring, and repo/change size.
+Memory requirements are dependent on the number of users and expected workload. Your exact needs may be more, depending on your workload. Your workload is influenced by factors such as - but not limited to - how active your users are, how much automation you use, mirroring, and repository/change size.
 
 The following is the recommended minimum Memory hardware guidance for a handful of example GitLab user base sizes.
 
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md
index 02b5d4a8a62729d4d44c5d22af03852b76df191c..94195ec87a000e1bde845fdad4ad2e3aaf49d0e3 100644
--- a/doc/integration/jenkins.md
+++ b/doc/integration/jenkins.md
@@ -203,7 +203,7 @@ If those are present, the request is exceeding the
 which is set to 10 seconds by default.
 
 To fix this the `gitlab_rails['webhook_timeout']` value must be increased
-in the `gitlab.rb` config file, followed by the [`gitlab-ctl reconfigure` command](../administration/restart_gitlab.md).
+in the `gitlab.rb` configuration file, followed by the [`gitlab-ctl reconfigure` command](../administration/restart_gitlab.md).
 
 If you don't find the errors above, but do find *duplicate* entries like below (in `/var/log/gitlab/gitlab-rail`), this
 could also indicate that [webhook requests are timing out](../user/project/integrations/webhooks.md#webhook-fails-or-multiple-webhook-requests-are-triggered):
diff --git a/doc/integration/jenkins_deprecated.md b/doc/integration/jenkins_deprecated.md
index 8fcd6eace31aaea525c48625cb689c198cd1b0f7..b5d68e3183f7b913cbbda459ac6ebec18abbdc05 100644
--- a/doc/integration/jenkins_deprecated.md
+++ b/doc/integration/jenkins_deprecated.md
@@ -18,13 +18,13 @@ This service was [removed in v13.0](https://gitlab.com/gitlab-org/gitlab/-/issue
 
 Integration includes:
 
-- Trigger Jenkins build after push to repo
+- Trigger Jenkins build after push to repository
 - Show build status on Merge Request page
 
 Requirements:
 
 - [Jenkins GitLab Hook plugin](https://wiki.jenkins.io/display/JENKINS/GitLab+Hook+Plugin)
-- Git clone access for Jenkins from GitLab repo (via SSH key)
+- Git clone access for Jenkins from GitLab repository (via SSH key)
 
 ## Jenkins
 
diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md
index 2dc7b39386c678617c819102c922e1ea5bf202e1..390c3ae3e7c093ce464fc5bec04ac766eac44d17 100644
--- a/doc/integration/kerberos.md
+++ b/doc/integration/kerberos.md
@@ -220,7 +220,7 @@ WARNING:
 There is a [known issue](https://github.com/curl/curl/issues/1261) with `libcurl`
 older than version 7.64.1 wherein it won't reuse connections when negotiating.
 This leads to authorization issues when push is larger than `http.postBuffer`
-config. Ensure that Git is using at least `libcurl` 7.64.1 to avoid this. To
+configuration. Ensure that Git is using at least `libcurl` 7.64.1 to avoid this. To
 know the `libcurl` version installed, run `curl-config --version`.
 
 ### HTTP Git access with Kerberos token (passwordless authentication)
diff --git a/doc/integration/oauth2_generic.md b/doc/integration/oauth2_generic.md
index 6cef4b0294cd522cea1df81c7fdf7dc0bb832472..88e9e3ef05cfddc126365d744b8f034a0c49a55e 100644
--- a/doc/integration/oauth2_generic.md
+++ b/doc/integration/oauth2_generic.md
@@ -26,7 +26,7 @@ This strategy is designed to allow configuration of the simple OmniAuth SSO proc
 - It is not able to fetch user information from more than one URL
 - It has not been tested with user information formats other than JSON
 
-## Config Instructions
+## Configuration Instructions
 
 1. Register your application in the OAuth2 provider you wish to authenticate with.
 
diff --git a/doc/integration/shibboleth.md b/doc/integration/shibboleth.md
index 52b51f755543814901189e35243c0a91627f8790..4b085af14a1d9089cd4b4797ec553f08f6b49cd8 100644
--- a/doc/integration/shibboleth.md
+++ b/doc/integration/shibboleth.md
@@ -16,7 +16,7 @@ To enable the Shibboleth OmniAuth provider you must configure Apache Shibboleth
 The installation and configuration of the module itself is out of the scope of this document.
 Check <https://wiki.shibboleth.net/confluence/display/SP3/Apache> for more information.
 
-You can find Apache config in [GitLab Recipes](https://gitlab.com/gitlab-org/gitlab-recipes/tree/master/web-server/apache).
+You can find Apache configuration in [GitLab Recipes](https://gitlab.com/gitlab-org/gitlab-recipes/tree/master/web-server/apache).
 
 The following changes are needed to enable Shibboleth:
 
@@ -40,7 +40,7 @@ The following changes are needed to enable Shibboleth:
    </Location>
    ```
 
-1. Exclude Shibboleth URLs from rewriting. Add `RewriteCond %{REQUEST_URI} !/Shibboleth.sso` and `RewriteCond %{REQUEST_URI} !/shibboleth-sp`. Config should look like this:
+1. Exclude Shibboleth URLs from rewriting. Add `RewriteCond %{REQUEST_URI} !/Shibboleth.sso` and `RewriteCond %{REQUEST_URI} !/shibboleth-sp`. Configuration should look like this:
 
    ```apache
    # Apache equivalent of Nginx try files