diff --git a/doc/README.md b/doc/README.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL1JFQURNRS5tZA==..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL1JFQURNRS5tZA== 100644
--- a/doc/README.md
+++ b/doc/README.md
@@ -69,7 +69,7 @@
 ## Configuring
 
 - [Configuring the external url](settings/configuration.md#configuring-the-external-url-for-gitlab)
-- [Configuring a relative URL for Gitlab (experimental)](settings/configuration.md#configuring-a-relative-url-for-gitlab)
-- [Storing git data in an alternative directory](settings/configuration.md#storing-git-data-in-an-alternative-directory)
-- [Changing the name of the git user group](settings/configuration.md#changing-the-name-of-the-git-user--group)
+- [Configuring a relative URL for GitLab (experimental)](settings/configuration.md#configuring-a-relative-url-for-gitlab)
+- [Storing Git data in an alternative directory](settings/configuration.md#storing-git-data-in-an-alternative-directory)
+- [Changing the name of the Git user group](settings/configuration.md#changing-the-name-of-the-git-user--group)
 - [Specify numeric user and group identifiers](settings/configuration.md#specify-numeric-user-and-group-identifiers)
@@ -75,5 +75,5 @@
 - [Specify numeric user and group identifiers](settings/configuration.md#specify-numeric-user-and-group-identifiers)
-- [Only start omnibus-gitlab services after a given filesystem is mounted](settings/configuration.md#only-start-omnibus-gitlab-services-after-a-given-filesystem-is-mounted)
+- [Only start Omnibus GitLab services after a given filesystem is mounted](settings/configuration.md#only-start-omnibus-gitlab-services-after-a-given-filesystem-is-mounted)
 - [Disable user and group account management](settings/configuration.html#disable-user-and-group-account-management)
 - [Disable storage directory management](settings/configuration.html#disable-storage-directories-management)
 - [Configuring Rack attack](settings/configuration.md#configuring-rack-attack)
@@ -86,7 +86,7 @@
 - [Database](settings/database.md)
 - [Reply by email](https://docs.gitlab.com/ce/incoming_email/README.html)
 - [Environment variables](settings/environment-variables.md)
-- [gitlab.yml](settings/gitlab.yml.md)
+- [`gitlab.yml`](settings/gitlab.yml.md)
 - [Backups](settings/backups.md)
 - [Pages](https://docs.gitlab.com/ce/pages/administration.html)
 - [SSL](settings/ssl.md)
@@ -109,9 +109,9 @@
 ## Troubleshooting
 
 - [Hash Sum mismatch when downloading packages](common_installation_problems/README.md#hash-sum-mismatch-when-downloading-packages)
-- [Apt error: 'The requested URL returned error: 403'](common_installation_problems/README.md#apt-error-the-requested-url-returned-error-403).
+- [Apt error: `The requested URL returned error: 403`](common_installation_problems/README.md#apt-error-the-requested-url-returned-error-403).
 - [GitLab is unreachable in my browser](common_installation_problems/README.md#gitlab-is-unreachable-in-my-browser).
 - [Emails are not being delivered](common_installation_problems/README.md#emails-are-not-being-delivered).
 - [Reconfigure freezes at ruby_block[supervise_redis_sleep] action run](common_installation_problems/README.md#reconfigure-freezes-at-ruby_blocksupervise_redis_sleep-action-run).
 - [TCP ports for GitLab services are already taken](common_installation_problems/README.md#tcp-ports-for-gitlab-services-are-already-taken).
 - [Git SSH access stops working on SELinux-enabled systems](common_installation_problems/README.md#selinux-enabled-systems).
@@ -113,7 +113,7 @@
 - [GitLab is unreachable in my browser](common_installation_problems/README.md#gitlab-is-unreachable-in-my-browser).
 - [Emails are not being delivered](common_installation_problems/README.md#emails-are-not-being-delivered).
 - [Reconfigure freezes at ruby_block[supervise_redis_sleep] action run](common_installation_problems/README.md#reconfigure-freezes-at-ruby_blocksupervise_redis_sleep-action-run).
 - [TCP ports for GitLab services are already taken](common_installation_problems/README.md#tcp-ports-for-gitlab-services-are-already-taken).
 - [Git SSH access stops working on SELinux-enabled systems](common_installation_problems/README.md#selinux-enabled-systems).
-- [Postgres error 'FATAL:  could not create shared memory segment: Cannot allocate memory'](common_installation_problems/README.md#postgres-error-fatal--could-not-create-shared-memory-segment-cannot-allocate-memory).
+- [Postgres error `FATAL:  could not create shared memory segment: Cannot allocate memory`](common_installation_problems/README.md#postgres-error-fatal--could-not-create-shared-memory-segment-cannot-allocate-memory).
 - [Reconfigure complains about the GLIBC version](common_installation_problems/README.md#reconfigure-complains-about-the-glibc-version).
@@ -119,3 +119,3 @@
 - [Reconfigure complains about the GLIBC version](common_installation_problems/README.md#reconfigure-complains-about-the-glibc-version).
-- [Reconfigure fails to create the git user](common_installation_problems/README.md#reconfigure-fails-to-create-the-git-user).
+- [Reconfigure fails to create the Git user](common_installation_problems/README.md#reconfigure-fails-to-create-the-git-user).
 - [Failed to modify kernel parameters with sysctl](common_installation_problems/README.md#failed-to-modify-kernel-parameters-with-sysctl).
@@ -121,11 +121,11 @@
 - [Failed to modify kernel parameters with sysctl](common_installation_problems/README.md#failed-to-modify-kernel-parameters-with-sysctl).
-- [I am unable to install omnibus-gitlab without root access](common_installation_problems/README.md#i-am-unable-to-install-omnibus-gitlab-without-root-access).
-- [gitlab-rake assets:precompile fails with 'Permission denied'](common_installation_problems/README.md#gitlab-rake-assetsprecompile-fails-with-permission-denied).
-- ['Short read or OOM loading DB' error](common_installation_problems/README.md#short-read-or-oom-loading-db-error).
-- ['pg_dump: aborting because of server version mismatch'](settings/database.md#using-a-non-packaged-postgresql-database-management-server)
-- ['Errno::ENOMEM: Cannot allocate memory' during backup or upgrade](common_installation_problems/README.md#errnoenomem-cannot-allocate-memory-during-backup-or-upgrade)
-- [NGINX error: 'could not build server_names_hash'](common_installation_problems/README.md#nginx-error-could-not-build-server_names_hash-you-should-increase-server_names_hash_bucket_size)
-- [Reconfigure fails due to "'root' cannot chown" with NFS root_squash](common_installation_problems/README.md#reconfigure-fails-due-to-root-cannot-chown-with-nfs-root_squash)
+- [I am unable to install Omnibus GitLab without root access](common_installation_problems/README.md#i-am-unable-to-install-omnibus-gitlab-without-root-access).
+- [`gitlab-rake assets:precompile` fails with `Permission denied`](common_installation_problems/README.md#gitlab-rake-assetsprecompile-fails-with-permission-denied).
+- [`Short read or OOM loading DB` error](common_installation_problems/README.md#short-read-or-oom-loading-db-error).
+- [`pg_dump: aborting because of server version mismatch`](settings/database.md#using-a-non-packaged-postgresql-database-management-server)
+- [`Errno::ENOMEM: Cannot allocate memory` during backup or upgrade](common_installation_problems/README.md#errnoenomem-cannot-allocate-memory-during-backup-or-upgrade)
+- [NGINX error: `could not build server_names_hash`](common_installation_problems/README.md#nginx-error-could-not-build-server_names_hash-you-should-increase-server_names_hash_bucket_size)
+- [Reconfigure fails due to `'root' cannot chown` with NFS root_squash](common_installation_problems/README.md#reconfigure-fails-due-to-root-cannot-chown-with-nfs-root_squash)
 
 ## Omnibus GitLab developer documentation
 
diff --git a/doc/package-information/README.md b/doc/package-information/README.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vUkVBRE1FLm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vUkVBRE1FLm1k 100644
--- a/doc/package-information/README.md
+++ b/doc/package-information/README.md
@@ -1,6 +1,6 @@
 # Package information
 
-The omnibus-gitlab package is bundled with all dependencies required for GitLab
+The Omnibus GitLab package is bundled with all dependencies required for GitLab
 to function correctly. More details can be found
 at [bundling dependencies document](omnibus_packages.md).
 
@@ -10,7 +10,7 @@
 
 ## Defaults
 
-The omnibus-gitlab package requires various configuration to get the
+The Omnibus GitLab package requires various configuration to get the
 components in working order.
 If the configuration is not provided, the package will use the default
 values assumed in the package.
@@ -19,6 +19,6 @@
 
 ## Checking the versions of bundled software
 
-Once the omnibus-gitlab package is installed, all versions of the bundled
+Once the Omnibus GitLab package is installed, all versions of the bundled
 libraries are  located in `/opt/gitlab/version-manifest.txt`.
 
@@ -23,7 +23,7 @@
 libraries are  located in `/opt/gitlab/version-manifest.txt`.
 
-If you don't have the package installed, you can always check the omnibus-gitlab
+If you don't have the package installed, you can always check the Omnibus GitLab
 [source repository], specifically the [config directory].
 
 For example, if you take a look at the `8-6-stable` branch, you can conclude that
 8.6 packages were running [ruby 2.1.8]. Or, that 8.5 packages were bundled
@@ -26,8 +26,8 @@
 [source repository], specifically the [config directory].
 
 For example, if you take a look at the `8-6-stable` branch, you can conclude that
 8.6 packages were running [ruby 2.1.8]. Or, that 8.5 packages were bundled
-with [nginx 1.9.0].
+with [Nginx 1.9.0].
 
 ## Signatures of GitLab, Inc. provided packages
 
@@ -36,8 +36,8 @@
 ## Checking for newer configuration options on upgrade
 
 Configuration file in `/etc/gitlab/gitlab.rb` is created on initial installation
-of the omnibus-gitlab package. On subsequent package upgrades, the configuration
+of the Omnibus GitLab package. On subsequent package upgrades, the configuration
 file is not updated with new configuration. This is done in order to avoid
 accidental overwrite of user configuration provided in `/etc/gitlab/gitlab.rb`.
 
 New configuration options are noted in the
@@ -40,6 +40,6 @@
 file is not updated with new configuration. This is done in order to avoid
 accidental overwrite of user configuration provided in `/etc/gitlab/gitlab.rb`.
 
 New configuration options are noted in the
-[gitlab.rb.template file](https://gitlab.com/gitlab-org/omnibus-gitlab/raw/master/files/gitlab-config-template/gitlab.rb.template).
+[`gitlab.rb.template` file](https://gitlab.com/gitlab-org/omnibus-gitlab/raw/master/files/gitlab-config-template/gitlab.rb.template).
 
@@ -45,5 +45,5 @@
 
-The omnibus-gitlab package also provides convenience command which will
+The Omnibus GitLab package also provides convenience command which will
 compare the existing user configuration with the latest version of the
 template contained in the package.
 
@@ -61,7 +61,7 @@
 
 ## Init system detection
 
-The omnibus-gitlab will attempt to query the underlaying system in order to
+Omnibus GitLab will attempt to query the underlaying system in order to
 check which init system it uses.
 This manifests itself as a `WARNING` during the `sudo gitlab-ctl reconfigure`
 run.
diff --git a/doc/package-information/defaults.md b/doc/package-information/defaults.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vZGVmYXVsdHMubWQ=..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vZGVmYXVsdHMubWQ= 100644
--- a/doc/package-information/defaults.md
+++ b/doc/package-information/defaults.md
@@ -5,6 +5,6 @@
 
 ## Ports
 
-See the table below for the list of ports that the omnibus-gitlab assigns
+See the table below for the list of ports that the Omnibus GitLab assigns
 by default:
 
@@ -9,37 +9,37 @@
 by default:
 
-| Component                                           | On by default | Communicates via | Alternative | Connection port                        |
-| :-------------------------------------------------: | :------------:| :--------------: | :---------: | :------------------------------------: |
-| <a name="gitlab-rails"></a>        GitLab Rails     | Yes           | Port             | X           | 80 or 443                              |
-| <a name="gitlab-shell"></a>        GitLab Shell     | Yes           | Port             | X           | 22                                     |
-| <a name="postgresql"></a>          PostgreSQL       | Yes           | Socket           | Port (5432) | X                                      |
-| <a name="redis"></a>               Redis            | Yes           | Socket           | Port (6379) | X                                      |
-| <a name="unicorn"></a>             Unicorn          | Yes           | Socket           | Port (8080) | X                                      |
-| <a name="gitlab-workhorse"></a>    GitLab Workhorse | Yes           | Socket           | Port (8181) | X                                      |
-| <a name="nginx-status"></a>        Nginx status     | Yes           | Port             | X           | 8060                                   |
-| <a name="prometheus"></a>          Prometheus       | Yes           | Port             | X           | 9090                                   |
-| <a name="node-exporter"></a>       Node exporter    | Yes           | Port             | X           | 9100                                   |
-| <a name="redis-exporter"></a>      Redis exporter   | Yes           | Port             | X           | 9121                                   |
-| <a name="postgres-exporter"></a>   Postgres exporter| Yes           | Port             | X           | 9187                                   |
-| <a name="pgbouncer-exporter"></a> PgBouncer exporter| No            | Port             | X           | 9188                                   |
-| <a name="gitlab-monitor"></a>      Gitlab monitor   | Yes           | Port             | X           | 9168                                   |
-| <a name="sidekiq-exporter"></a>    Sidekiq exporter | Yes           | Port             | X           | 8082                                   |
-| <a name="geo-postgresql"></a>      Geo PostgreSQL   | No            | Socket           | Port (5431) | X                                      |
-| <a name="redis-sentinel"></a>      Redis Sentinel   | No            | Port             | X           | 26379                                  |
-| <a name="incoming-email"></a>      Incoming email   | No            | Port             | X           | 143                                    |
-| <a name="elasticsearch"></a>       Elastic search   | No            | Port             | X           | 9200                                   |
-| <a name="gitlab-pages"></a>        GitLab Pages     | No            | Port             | X           | 80 or 443                              |
-| <a name="gitlab-registry-web"></a> GitLab Registry  | No            | Port             | X           | 80 or 443                              |
-| <a name="gitlab-registry"></a>     GitLab Registry  | No            | Port             | X           | 5000                                   |
-| <a name="ldap"></a>                LDAP             | No            | Port             | X           | Depends on the component configuration |
-| <a name="kerberos"></a>            Kerberos         | No            | Port             | X           | 8443 or 8088                           |
-| <a name="omniauth"></a>            Omniauth         | Yes           | Port             | X           | Depends on the component configuration |
-| <a name="smtp"></a>                SMTP             | No            | Port             | X           | 465                                    |
-| <a name="remote-syslog"></a>       Remote syslog    | No            | Port             | X           | 514                                    |
-| <a name="mattermost"></a>          Mattermost       | No            | Port             | X           | 8065                                   |
-| <a name="mattermost-web"></a>      Mattermost       | No            | Port             | X           | 80 or 443                              |
-| <a name="pgbouncer"></a>           PgBouncer        | No            | Port             | X           | 6432                                   |
-| <a name="consul"></a>              Consul           | No            | Port             | X           | 8300, 8500                             |
+| Component                                             | On by default | Communicates via | Alternative | Connection port                        |
+| :---------------------------------------------------: | :------------:| :--------------: | :---------: | :------------------------------------: |
+| <a name="gitlab-rails"></a>        GitLab Rails       | Yes           | Port             | X           | 80 or 443                              |
+| <a name="gitlab-shell"></a>        GitLab Shell       | Yes           | Port             | X           | 22                                     |
+| <a name="postgresql"></a>          PostgreSQL         | Yes           | Socket           | Port (5432) | X                                      |
+| <a name="redis"></a>               Redis              | Yes           | Socket           | Port (6379) | X                                      |
+| <a name="unicorn"></a>             Unicorn            | Yes           | Socket           | Port (8080) | X                                      |
+| <a name="gitlab-workhorse"></a>    GitLab Workhorse   | Yes           | Socket           | Port (8181) | X                                      |
+| <a name="nginx-status"></a>        NGINX status       | Yes           | Port             | X           | 8060                                   |
+| <a name="prometheus"></a>          Prometheus         | Yes           | Port             | X           | 9090                                   |
+| <a name="node-exporter"></a>       Node exporter      | Yes           | Port             | X           | 9100                                   |
+| <a name="redis-exporter"></a>      Redis exporter     | Yes           | Port             | X           | 9121                                   |
+| <a name="postgres-exporter"></a>   Postgres exporter  | Yes           | Port             | X           | 9187                                   |
+| <a name="pgbouncer-exporter"></a>  PgBouncer exporter | No            | Port             | X           | 9188                                   |
+| <a name="gitlab-monitor"></a>      GitLab Monitor     | Yes           | Port             | X           | 9168                                   |
+| <a name="sidekiq-exporter"></a>    Sidekiq exporter   | Yes           | Port             | X           | 8082                                   |
+| <a name="geo-postgresql"></a>      Geo PostgreSQL     | No            | Socket           | Port (5431) | X                                      |
+| <a name="redis-sentinel"></a>      Redis Sentinel     | No            | Port             | X           | 26379                                  |
+| <a name="incoming-email"></a>      Incoming email     | No            | Port             | X           | 143                                    |
+| <a name="elasticsearch"></a>       Elastic search     | No            | Port             | X           | 9200                                   |
+| <a name="gitlab-pages"></a>        GitLab Pages       | No            | Port             | X           | 80 or 443                              |
+| <a name="gitlab-registry-web"></a> GitLab Registry    | No            | Port             | X           | 80 or 443                              |
+| <a name="gitlab-registry"></a>     GitLab Registry    | No            | Port             | X           | 5000                                   |
+| <a name="ldap"></a>                LDAP               | No            | Port             | X           | Depends on the component configuration |
+| <a name="kerberos"></a>            Kerberos           | No            | Port             | X           | 8443 or 8088                           |
+| <a name="omniauth"></a>            Omniauth           | Yes           | Port             | X           | Depends on the component configuration |
+| <a name="smtp"></a>                SMTP               | No            | Port             | X           | 465                                    |
+| <a name="remote-syslog"></a>       Remote syslog      | No            | Port             | X           | 514                                    |
+| <a name="mattermost"></a>          Mattermost         | No            | Port             | X           | 8065                                   |
+| <a name="mattermost-web"></a>      Mattermost         | No            | Port             | X           | 80 or 443                              |
+| <a name="pgbouncer"></a>           PgBouncer          | No            | Port             | X           | 6432                                   |
+| <a name="consul"></a>              Consul             | No            | Port             | X           | 8300, 8500                             |
 
 Legend:
 
@@ -49,7 +49,7 @@
 - `Alternative` - If it is possible to configure the component to use different type of communication. The type is listed with default port used in that case.
 - `Connection port` - Port on which the component communicates.
 
-GitLab also expects a filesystem to be ready for the storage of git repositories
+GitLab also expects a filesystem to be ready for the storage of Git repositories
 and various other files.
 
 Note that if you are using NFS (Network File System), files will be carried
diff --git a/doc/package-information/deprecation_policy.md b/doc/package-information/deprecation_policy.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vZGVwcmVjYXRpb25fcG9saWN5Lm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vZGVwcmVjYXRpb25fcG9saWN5Lm1k 100644
--- a/doc/package-information/deprecation_policy.md
+++ b/doc/package-information/deprecation_policy.md
@@ -1,6 +1,6 @@
 # Deprecation policy
 
-The omnibus-gitlab packages come with number of different libraries and services which offers users plethora of configuration options.
+The Omnibus GitLab packages come with number of different libraries and services which offers users plethora of configuration options.
 
 As libraries and services get updated, their configuration options change
 and become obsolete. To increase maintainability and preserve a working
@@ -10,7 +10,7 @@
 
 ### Policy
 
-The omnibus-gitlab package will retain configuration for at least **one major**
+The Omnibus GitLab package will retain configuration for at least **one major**
 version. We cannot guarantee that deprecated configuration
 will be available in the next major release. See [example](#example) for more details.
 
@@ -41,7 +41,7 @@
 
 Common steps:
 
-1. Create an issue at the [omnibus-gitlab issue tracker][] with details on deprecation type and other necessary information. Apply the label `deprecation`.
+1. Create an issue at the [Omnibus GitLab issue tracker](https://gitlab.com/gitlab-org/omnibus-gitlab/issues) with details on deprecation type and other necessary information. Apply the label `deprecation`.
 1. Decide on the removal target for the deprecated configuration
 1. Formulate deprecation notice for each item as noted in [Notice section](#notice)
 
@@ -87,5 +87,3 @@
 With GitLab 11, `gitlab_rails['configuration'] = true` will no longer work and you will have to manually change the configuration in `/etc/gitlab/gitlab.rb` to the new valid config.
 **Note** If this configuration option is sensitive and can put integrity of the installation or
 data in danger, installation/upgrade will be aborted.
-
-[omnibus-gitlab issue tracker]: https://gitlab.com/gitlab-org/omnibus-gitlab/issues
diff --git a/doc/package-information/licensing.md b/doc/package-information/licensing.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vbGljZW5zaW5nLm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vbGljZW5zaW5nLm1k 100644
--- a/doc/package-information/licensing.md
+++ b/doc/package-information/licensing.md
@@ -2,7 +2,7 @@
 
 ## License
 
-While GitLab itself is MIT, the omnibus-gitlab sources are licensed under the Apache-2.0.
+While GitLab itself is MIT, the Omnibus GitLab sources are licensed under the Apache-2.0.
 
 ## License file location
 
@@ -6,7 +6,7 @@
 
 ## License file location
 
-Starting with version 8.11, the omnibus-gitlab package contains license
+Starting with version 8.11, the Omnibus GitLab package contains license
 information of all software that is bundled within the package.
 
 After installing the package, licenses for each individual bundled library
@@ -15,7 +15,7 @@
 There is also one `LICENSE` file which contains all licenses compiled together.
 This compiled license can be found in `/opt/gitlab/LICENSE` file.
 
-Starting with version 9.2, the omnibus-gitlab package ships a
+Starting with version 9.2, the Omnibus GitLab package ships a
 `dependency_licenses.json` file containing version and license information of
 all bundled software, including software libraries, Ruby gems that the rails
 application uses, and JavaScript libraries that is required for the frontend
@@ -24,7 +24,7 @@
 `/opt/gitlab/dependency_licenses.json`.
 
 Starting with version 11.3, we have also made the license information available
-online, at: [http://gitlab-org.gitlab.io/omnibus-gitlab/licenses.html](http://gitlab-org.gitlab.io/omnibus-gitlab/licenses.html)
+online, at: <http://gitlab-org.gitlab.io/omnibus-gitlab/licenses.html>
 
 ## Checking licenses
 
@@ -28,7 +28,7 @@
 
 ## Checking licenses
 
-The omnibus-gitlab package is made up of many pieces of software, comprising code
+The Omnibus GitLab package is made up of many pieces of software, comprising code
 that is covered by many different licenses. Those licenses are provided and
 compiled as stated above.
 
@@ -32,9 +32,9 @@
 that is covered by many different licenses. Those licenses are provided and
 compiled as stated above.
 
-Starting with version 8.13, GitLab has placed an additional step into the
-omnibus-gitlab. The `license_check` step calls
+Starting with version 8.13, GitLab has placed an additional step into
+Omnibus GitLab. The `license_check` step calls
 `lib/gitlab/tasks/license_check.rake`, which checks the compiled `LICENSE` file
 against the current list of approved and questionable licenses as denoted in the
 arrays at the top of the script. This script will output one of `Good`,
 `Unknown` or `Check` for each piece of software that is a part of the
@@ -37,7 +37,7 @@
 `lib/gitlab/tasks/license_check.rake`, which checks the compiled `LICENSE` file
 against the current list of approved and questionable licenses as denoted in the
 arrays at the top of the script. This script will output one of `Good`,
 `Unknown` or `Check` for each piece of software that is a part of the
-omnibus-gitlab package.
+Omnibus GitLab package.
 
 - `Good`: denotes a license that is approved for all usage types, within GitLab and
@@ -42,6 +42,6 @@
 
 - `Good`: denotes a license that is approved for all usage types, within GitLab and
-  omnibus-gitlab.
+  Omnibus GitLab.
 - `Unknown`: denotes a license that is not recognized in the list of 'good' or 'bad',
   which should be immediately reviewed for implications of use.
 - `Check`: denotes a license that has the potential be incompatible with GitLab itself,
@@ -45,7 +45,7 @@
 - `Unknown`: denotes a license that is not recognized in the list of 'good' or 'bad',
   which should be immediately reviewed for implications of use.
 - `Check`: denotes a license that has the potential be incompatible with GitLab itself,
-  and thus should be checked for how it is used as a part of the omnibus-gitlab package
+  and thus should be checked for how it is used as a part of the Omnibus GitLab package
   to ensure compliance.
 
 This list is currently sourced from the [GitLab development documentation on licensing](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/licensing.md).
@@ -49,5 +49,5 @@
   to ensure compliance.
 
 This list is currently sourced from the [GitLab development documentation on licensing](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/licensing.md).
-However, due to the nature of the omnibus-gitlab package the licenses may not apply
+However, due to the nature of the Omnibus GitLab package the licenses may not apply
 in the same way. Such as with `git` and `rsync`. See the [GNU License FAQ](https://www.gnu.org/licenses/gpl-faq.en.html#MereAggregation)
diff --git a/doc/package-information/signed_packages.md b/doc/package-information/signed_packages.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vc2lnbmVkX3BhY2thZ2VzLm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3BhY2thZ2UtaW5mb3JtYXRpb24vc2lnbmVkX3BhY2thZ2VzLm1k 100644
--- a/doc/package-information/signed_packages.md
+++ b/doc/package-information/signed_packages.md
@@ -1,6 +1,6 @@
 # Package Signatures
 
-As of the release of GitLab 9.5 on August 22, 2017, GitLab provides signed Omnibus GitLab packages for RPM and DEB based distributions. This means that all packages provided on [packages.gitlab.com](https://packages.gitlab.com) are signed, starting with `9.5.0`, and all future versions of supported branches (e.g. `9.3.x` and `9.4.x` after August 22, 2017). Any package version prior to August 22, 2017, will not be signed. Please pass the appropriate argument to your package manager. (Example: `yum --nogpgcheck`)
+As of the release of GitLab 9.5 on August 22, 2017, GitLab provides signed Omnibus GitLab packages for RPM and DEB based distributions. This means that all packages provided on <https://packages.gitlab.com> are signed, starting with `9.5.0`, and all future versions of supported branches (e.g. `9.3.x` and `9.4.x` after August 22, 2017). Any package version prior to August 22, 2017, will not be signed. Please pass the appropriate argument to your package manager. (Example: `yum --nogpgcheck`)
 
 Omnibus GitLab packages produced by GitLab are created via the [Omnibus](https://github.com/chef/omnibus) tool, for which GitLab has added DEB signing via `debsigs` in [our own fork](https://gitlab.com/gitlab-org/omnibus). This addition, combined with the existing functionality of RPM signing, allows GitLab to provide signed packages for all supported distributions using DEB or RPM.
 
@@ -4,7 +4,7 @@
 
 Omnibus GitLab packages produced by GitLab are created via the [Omnibus](https://github.com/chef/omnibus) tool, for which GitLab has added DEB signing via `debsigs` in [our own fork](https://gitlab.com/gitlab-org/omnibus). This addition, combined with the existing functionality of RPM signing, allows GitLab to provide signed packages for all supported distributions using DEB or RPM.
 
-These packages are produced by the GitLab CI process, as found in the  [omnibus-gitlab project](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/.gitlab-ci.yml), prior to their delivery to [packages.gitlab.com][packages] to ensure provide assurance that the packages are not altered prior to delivery to our community.
+These packages are produced by the GitLab CI process, as found in the  [Omnibus GitLab project](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/.gitlab-ci.yml), prior to their delivery to <https://packages.gitlab.com> to ensure provide assurance that the packages are not altered prior to delivery to our community.
 
 ## GnuPG Public Keys
 
@@ -14,8 +14,6 @@
 
 Information on how to verify GitLab package signatures can be found in [Package Signatures](../update/package_signatures.md).
 
-[packages]: https://packages.gitlab.com
-
 ## GPG Signature Management
 
 Information on how GitLab manages GPG keys for package signing can be found in [the runbooks](https://gitlab.com/gitlab-com/runbooks/blob/master/howto/manage-package-signing-keys.md).
diff --git a/doc/release/README.md b/doc/release/README.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3JlbGVhc2UvUkVBRE1FLm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3JlbGVhc2UvUkVBRE1FLm1k 100644
--- a/doc/release/README.md
+++ b/doc/release/README.md
@@ -1,5 +1,5 @@
-# Omnibus-gitlab release process
+# Omnibus GitLab release process
 
 Our main goal is to make it clear which version of GitLab is in an omnibus
 package.
 
@@ -2,10 +2,10 @@
 
 Our main goal is to make it clear which version of GitLab is in an omnibus
 package.
 
-## How is the official omnibus-gitlab package built
+## How is the official Omnibus GitLab package built
 
 The official package build is fully automated by GitLab Inc.
 
 We can differentiate between two types of build:
 
@@ -7,9 +7,9 @@
 
 The official package build is fully automated by GitLab Inc.
 
 We can differentiate between two types of build:
 
-- Packages for release to packages.gitlab.com.
+- Packages for release to <https://packages.gitlab.com>.
 - Test packages built from branches available in S3 buckets.
 
 Both types are built on the same infrastructure.
@@ -21,7 +21,7 @@
 The number of build servers varies but there is always at least one build
 server per platform.
 
-The omnibus-gitlab project fully utilizes GitLab CI. This means that each push
-to omnibus-gitlab repository will trigger a build in GitLab CI which will
+The Omnibus GitLab project fully utilizes GitLab CI. This means that each push
+to the Omnibus GitLab repository will trigger a build in GitLab CI which will
 then create a package.
 
@@ -26,6 +26,6 @@
 then create a package.
 
-Since we deploy GitLab.com using omnibus-gitlab packages, we need a separate
+Since we deploy GitLab.com using Omnibus GitLab packages, we need a separate
 remote to build the packages in case of a problem with GitLab.com or due to
 a security release of a package.
 
@@ -29,7 +29,7 @@
 remote to build the packages in case of a problem with GitLab.com or due to
 a security release of a package.
 
-This remote is located on dev.gitlab.org. The only difference between
-omnibus-gitlab project on dev.gitlab.org and other public remotes is that the
+This remote is located on <https://dev.gitlab.org/>. The only difference between the
+Omnibus GitLab project on <https://dev.gitlab.org/> and other public remotes is that the
 project has active GitLab CI and has specific runners assigned to the project
 which run on the build servers. This is also the case for all GitLab components,
@@ -34,4 +34,4 @@
 project has active GitLab CI and has specific runners assigned to the project
 which run on the build servers. This is also the case for all GitLab components,
-eg. gitlab-shell is exactly the same on dev.gitlab.org as it is on GitLab.com.
+eg. GitLab Shell is exactly the same on <https://dev.gitlab.org/> as it is on GitLab.com.
 
@@ -37,10 +37,10 @@
 
-All build servers run [gitlab runner] and all runners use a deploy key
-to connect to the projects on dev.gitlab.org. The build servers also have
-access to official package repository at packages.gitlab.com and to a special
+All build servers run [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner) and all runners use a deploy key
+to connect to the projects on <https://dev.gitlab.org/>. The build servers also have
+access to official package repository at <https://packages.gitlab.com> and to a special
 Amazon S3 bucket which stores the test packages.
 
 ## Build process
 
 GitLab Inc is using the [release-tools project] to automate the release tasks
 for every release. When the release manager starts the release process, a couple
@@ -41,10 +41,10 @@
 Amazon S3 bucket which stores the test packages.
 
 ## Build process
 
 GitLab Inc is using the [release-tools project] to automate the release tasks
 for every release. When the release manager starts the release process, a couple
-of important things for omnibus-gitlab will be done:
+of important things for Omnibus GitLab will be done:
 
 1. All remotes of the project will be synced.
 1. The versions of components will be read from GitLab CE/EE repository
@@ -48,6 +48,6 @@
 
 1. All remotes of the project will be synced.
 1. The versions of components will be read from GitLab CE/EE repository
-  (eg. VERSION, GITLAB_SHELL_VERSION) and written to omnibus-gitlab repository.
-1. A specific Git tag will be created and synced to omnibus-gitlab repositories.
+  (eg. VERSION, GITLAB_SHELL_VERSION) and written to the Omnibus GitLab repository.
+1. A specific Git tag will be created and synced to Omnibus GitLab repositories.
 
@@ -53,4 +53,4 @@
 
-When the omnibus-gitlab repository on dev.gitlab.org gets updated, GitLab CI
+When the Omnibus GitLab repository on <https://dev.gitlab.org/> gets updated, GitLab CI
 build gets triggered.
 
@@ -55,5 +55,5 @@
 build gets triggered.
 
-The specific steps can be seen in `.gitlab-ci.yml` file in omnibus-gitlab
+The specific steps can be seen in the `.gitlab-ci.yml` file in the Omnibus GitLab
 repository. The builds are executed on all platforms at the same time.
 
@@ -58,7 +58,7 @@
 repository. The builds are executed on all platforms at the same time.
 
-During the build, omnibus-gitlab will pull external libraries from their source
-locations and GitLab components like GitLab, gitlab-shell, gitlab-workhorse, and
-so on will be pulled from dev.gitlab.org.
+During the build, Omnibus GitLab will pull external libraries from their source
+locations and GitLab components like GitLab, GitLab Shell, GitLab Workhorse, and
+so on will be pulled from <https://dev.gitlab.org/>.
 
 Once the build completes and the .deb or .rpm packages are built, depending on
@@ -63,6 +63,6 @@
 
 Once the build completes and the .deb or .rpm packages are built, depending on
-the build type package will be pushed to packages.gitlab.com or to a temporary
+the build type package will be pushed to <https://packages.gitlab.com> or to a temporary
 (files older than 30 days are purged) S3 bucket.
 
 ## Specifying component versions manually
@@ -70,7 +70,7 @@
 ### On your development machine
 
 1. Pick a tag of GitLab to package (e.g. `v6.6.0`).
-1. Create a release branch in omnibus-gitlab (e.g. `6-6-stable`).
+1. Create a release branch in your Omnibus GitLab repo (e.g. `6-6-stable`).
 1. If the release branch already exists, for instance because you are doing a
    patch release, make sure to pull the latest changes to your local machine:
 
@@ -80,7 +80,7 @@
 
 1. Use `support/set-revisions` to set the revisions of files in
    `config/software/`. It will take tag names and look up the Git SHA1's, and set
-   the download sources to dev.gitlab.org. Use `set-revisions --ee` for an EE
+   the download sources to <https://dev.gitlab.org/>. Use `set-revisions --ee` for an EE
    release:
 
    ```sh
@@ -100,7 +100,7 @@
    git commit
    ```
 
-1. Create an annotated tag on omnibus-gitlab corresponding to the GitLab tag.
+1. Create an annotated tag in Omnibus GitLab corresponding to the GitLab tag.
    The omnibus tag looks like: `MAJOR.MINOR.PATCH+OTHER.OMNIBUS_RELEASE`, where
    `MAJOR.MINOR.PATCH` is the GitLab version, `OTHER` can be something like `ce`,
    `ee` or `rc1` (or `rc1.ee`), and `OMNIBUS_RELEASE` is a number (starting at 0):
@@ -110,7 +110,7 @@
    ```
 
    CAUTION: **WARNING:**
-   Do NOT use a hyphen `-` anywhere in the omnibus-gitlab tag.
+   Do NOT use a hyphen `-` anywhere in the Omnibus GitLab tag.
 
    Examples of converting an upstream tag to an omnibus tag sequence:
 
@@ -120,10 +120,10 @@
    | `v7.10.4-ee`     | `7.10.4+ee.0`, `7.10.4+ee.1`, `...`         |
    | `v7.11.0.rc1-ee` | `7.11.0+rc1.ee.0`, `7.11.0+rc1.ee.1`, `...` |
 
-1. Push the branch and the tag to both gitlab.com and dev.gitlab.org:
+1. Push the branch and the tag to both <https://gitlab.com> and <https://dev.gitlab.org/>:
 
    ```sh
    git push git@gitlab.com:gitlab-org/omnibus-gitlab.git 6-6-stable 6.6.0+ce.0
    git push git@dev.gitlab.org:gitlab/omnibus-gitlab.git 6-6-stable 6.6.0+ce.0
    ```
 
@@ -124,10 +124,10 @@
 
    ```sh
    git push git@gitlab.com:gitlab-org/omnibus-gitlab.git 6-6-stable 6.6.0+ce.0
    git push git@dev.gitlab.org:gitlab/omnibus-gitlab.git 6-6-stable 6.6.0+ce.0
    ```
 
-   Pushing an annotated tag to dev.gitlab.org triggers a package release.
+   Pushing an annotated tag to <https://dev.gitlab.org/> triggers a package release.
 
 ### Publishing the packages
 
@@ -131,7 +131,7 @@
 
 ### Publishing the packages
 
-You can track the progress of package building on [dev.gitlab.org].
+You can track the progress of package building on <https://dev.gitlab.org/gitlab/omnibus-gitlab/builds>.
 They are pushed to [packagecloud repositories] automatically after
 successful builds.
 
@@ -149,5 +149,5 @@
 
 Image specific release documentation:
 
-- (**Deprecated**) OpenShift: [openshift.md](openshift.md).
+- (**Deprecated**) [OpenShift](openshift.md).
 
@@ -153,3 +153,2 @@
 
-[dev.gitlab.org]: https://dev.gitlab.org/gitlab/omnibus-gitlab/builds
 [release-tools project]: https://gitlab.com/gitlab-org/release-tools/tree/master
@@ -155,3 +154,2 @@
 [release-tools project]: https://gitlab.com/gitlab-org/release-tools/tree/master
-[gitlab runner]: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner
 [packagecloud repositories]: https://packages.gitlab.com/gitlab/
diff --git a/doc/release/openshift.md b/doc/release/openshift.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3JlbGVhc2Uvb3BlbnNoaWZ0Lm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3JlbGVhc2Uvb3BlbnNoaWZ0Lm1k 100644
--- a/doc/release/openshift.md
+++ b/doc/release/openshift.md
@@ -14,7 +14,7 @@
 
 Then update the image stream in the template with the name and tag:
 
-```
+```json
 {
   "kind": "ImageStream",
   "apiVersion": "v1",
@@ -40,7 +40,7 @@
 
 And then also update the GitLab Deployment config to use the new tag in it's ImageChange trigger:
 
-```
+```json
 {
   "type": "ImageChange",
   "imageChangeParams": {
@@ -59,7 +59,7 @@
 ## Test
 
 For setting up a OpenShift Origin development environment for testing see
-[doc/development/openshift/README.md.](../development/openshift/README.md)
+[`doc/development/openshift/README.md`](../development/openshift/README.md).
 
 Set up a new GitLab install using the updated template. Smoke test the install:
 
@@ -74,5 +74,5 @@
 
 ## Notify
 
-Once the Merge Request has been accepted, alert the #gitlab-openshift slack channel that a new
+Once the Merge Request has been accepted, alert the `#gitlab-openshift` slack channel that a new
 version has been pushed to master. Effectively handing off the template to OpenShift for inclusion in the all-in-one.
diff --git a/doc/update/README.md b/doc/update/README.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3VwZGF0ZS9SRUFETUUubWQ=..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3VwZGF0ZS9SRUFETUUubWQ= 100644
--- a/doc/update/README.md
+++ b/doc/update/README.md
@@ -320,7 +320,7 @@
   sudo gitlab-rake db:migrate
   ```
 
-**For nodes that run unicorn or sidekiq**
+**For nodes that run Unicorn or sidekiq**
 
 - Hot reload `unicorn` and `sidekiq` services
 
diff --git a/doc/update/convert_to_omnibus.md b/doc/update/convert_to_omnibus.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3VwZGF0ZS9jb252ZXJ0X3RvX29tbmlidXMubWQ=..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3VwZGF0ZS9jb252ZXJ0X3RvX29tbmlidXMubWQ= 100644
--- a/doc/update/convert_to_omnibus.md
+++ b/doc/update/convert_to_omnibus.md
@@ -20,8 +20,8 @@
 sudo gitlab-rake gitlab:check
 ```
 
-If you receive an error similar to "No such file or directory @ realpath_rec - /home/git",
-run this one liner to fix the git hooks path:
+If you receive an error similar to `No such file or directory @ realpath_rec - /home/git`,
+run this one liner to fix the Git hooks path:
 
 ```sh
 find . -lname /home/git/gitlab-shell/hooks -exec sh -c 'ln -snf /opt/gitlab/embedded/service/gitlab-shell/hooks $0' {} \;
@@ -31,5 +31,5 @@
 
 ## Upgrading from non-Omnibus PostgreSQL to an Omnibus installation in-place
 
-It is also possible to upgrade a source GitLab installation to omnibus-gitlab
+It is also possible to upgrade a source GitLab installation to Omnibus GitLab
 in-place.  Below we assume you are using PostgreSQL on Ubuntu, and that you
@@ -35,5 +35,5 @@
 in-place.  Below we assume you are using PostgreSQL on Ubuntu, and that you
-have an omnibus-gitlab package matching your current GitLab version.  We also
+have an Omnibus GitLab package matching your current GitLab version.  We also
 assume that your source installation of GitLab uses all the default paths and
 users.
 
@@ -37,7 +37,7 @@
 assume that your source installation of GitLab uses all the default paths and
 users.
 
-First, stop and disable GitLab, Redis and Nginx.
+First, stop and disable GitLab, Redis and NGINX.
 
 ```sh
 # Ubuntu
@@ -53,7 +53,7 @@
 
 If you are using a configuration management system to manage GitLab on your
 server, remember to also disable GitLab and its related services there. Also
-note that in the following steps, the existing home directory of the git user
+note that in the following steps, the existing home directory of the Git user
 (`/home/git`) will be changed to `/var/opt/gitlab`.
 
 Next, create a `gitlab.rb` file for your new setup:
@@ -84,7 +84,7 @@
 ```
 
 You are not done yet! The `gitlab-ctl reconfigure` run has changed the home
-directory of the git user, so OpenSSH can no longer find its authorized_keys
+directory of the Git user, so OpenSSH can no longer find its authorized_keys
 file. Rebuild the keys file with the following command:
 
 ```sh
@@ -95,7 +95,7 @@
 repositories and users that were there before.
 
 If you can log into the GitLab web interface, the next step is to reboot your
-server to make sure none of the old services interferes with omnibus-gitlab.
+server to make sure none of the old services interferes with Omnibus GitLab.
 
 If you are using special features such as LDAP you will have to put your
 settings in `gitlab.rb`, see the [settings docs](../settings/README.md).
diff --git a/doc/update/gitlab_11_changes.md b/doc/update/gitlab_11_changes.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3VwZGF0ZS9naXRsYWJfMTFfY2hhbmdlcy5tZA==..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3VwZGF0ZS9naXRsYWJfMTFfY2hhbmdlcy5tZA== 100644
--- a/doc/update/gitlab_11_changes.md
+++ b/doc/update/gitlab_11_changes.md
@@ -11,8 +11,8 @@
 ## Clients supporting TLS v1.2
 
 - **Git-Credential-Manager** - support since **1.14.0**
-- **git on Red Hat Enterprise Linux 6** - support since **6.8**
-- **git on Red Hat Enteprirse Linux 7** - support since **7.2**
+- **Git on Red Hat Enterprise Linux 6** - support since **6.8**
+- **Git on Red Hat Enteprirse Linux 7** - support since **7.2**
 - **JGit / Java** - support since **JDK 7**
 - **Visual Studio** - support since version **2017**
 
@@ -35,7 +35,7 @@
 
 If either of the above requirements are not satisfied, upgrade process will
 abort without making changes to user's existing installation. This is to ensure
-that users does not end up with a broken Gitlab due to these unsupported
+that users does not end up with a broken GitLab due to these unsupported
 configurations.
 
 ## Removed configurations
@@ -103,7 +103,7 @@
 
 ### 11.6
 
-1. [Sidekiq probe of gitlab-monitor](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_monitor_exporter.html)
+1. [Sidekiq probe of GitLab Monitor](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_monitor_exporter.html)
    will be disabled by default if GitLab is configured in [Redis HA mode](https://docs.gitlab.com/ee/administration/high_availability/redis.html).
    To manually enable it, users can set `gitlab_monitor['probe_sidekiq'] = true`
    in `/etc/gitlab/gitlab.rb` file. However, when manually enabling it in Redis
@@ -120,5 +120,5 @@
    ```
 
    NOTE: **Note**: In the above configuration, when a failover happens after the
-   master node fails, gitlab-monitor will still be probing the original master
+   master node fails, GitLab Monitor will still be probing the original master
    node, since it is specified in `gitlab.rb`. Users will have to manually update
@@ -124,4 +124,4 @@
    node, since it is specified in `gitlab.rb`. Users will have to manually update
-   gitlab.rb to point it to the new master node.
+   `gitlab.rb` to point it to the new master node.
 
 1. Ruby has been updated to 2.5.3. GitLab will be down during the upgrade until
@@ -126,5 +126,5 @@
 
 1. Ruby has been updated to 2.5.3. GitLab will be down during the upgrade until
-   the unicorn processes have been restarted. The restart is done automatically
+   the Unicorn processes have been restarted. The restart is done automatically
    at the end of `gitlab-ctl reconfigure`, which is run by default on upgrade.
 
@@ -129,6 +129,6 @@
    at the end of `gitlab-ctl reconfigure`, which is run by default on upgrade.
 
-   NOTE: **Note**: the application will throw 500 http errors until the unicorn
+   NOTE: **Note**: the application will throw 500 http errors until the Unicorn
    restart is completed.
 
 ### 11.8
diff --git a/doc/update/gitlab_12_changes.md b/doc/update/gitlab_12_changes.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3VwZGF0ZS9naXRsYWJfMTJfY2hhbmdlcy5tZA==..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3VwZGF0ZS9naXRsYWJfMTJfY2hhbmdlcy5tZA== 100644
--- a/doc/update/gitlab_12_changes.md
+++ b/doc/update/gitlab_12_changes.md
@@ -28,7 +28,7 @@
 So, if you are on an HA instance, run this command only as the last step, after
 performing all database related actions.
 
-## Removal of support for /etc/gitlab/skip-auto-migrations file
+## Removal of support for `/etc/gitlab/skip-auto-migrations` file
 
 Before GitLab 10.6, the file `/etc/gitlab/skip-auto-migrations` was used to
 prevent automatic reconfigure (and thus automatic database migrations) as part
@@ -86,4 +86,4 @@
 
 ### 12.2
 
-The default formula for calculating the number of unicorn worker processes has been updated to increase the number of workers by 50% per CPU. This will increase the CPU and memory utilization slightly. This has been done to improve performance by reducing the amount of request queuing.
+The default formula for calculating the number of Unicorn worker processes has been updated to increase the number of workers by 50% per CPU. This will increase the CPU and memory utilization slightly. This has been done to improve performance by reducing the amount of request queuing.
diff --git a/doc/update/gitlab_6_changes.md b/doc/update/gitlab_6_changes.md
index 87080649d0c1971f5da955bfcf6e03d2ca37fd2b_ZG9jL3VwZGF0ZS9naXRsYWJfNl9jaGFuZ2VzLm1k..079f5b7af31aff32190200e7dd416c26b68e28b9_ZG9jL3VwZGF0ZS9naXRsYWJfNl9jaGFuZ2VzLm1k 100644
--- a/doc/update/gitlab_6_changes.md
+++ b/doc/update/gitlab_6_changes.md
@@ -43,7 +43,7 @@
 1. First, download the latest package from <https://about.gitlab.com/install/>
    to your GitLab server.
 
-1. Stop unicorn and Sidekiq so we can do database migrations:
+1. Stop Unicorn and Sidekiq so we can do database migrations:
 
    ```sh
    sudo gitlab-ctl stop unicorn