Minor style updates

doc/docker/README.md

@@ -6,19 +6,19 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 # GitLab Docker images
-The GitLab Docker images are monolithic images of GitLab running all the necessary
-services in a single container. If you want to install GitLab on Kubernetes instead,
-take a look at [GitLab Helm Charts](https://docs.gitlab.com/charts/).
+The GitLab Docker images are monolithic images of GitLab running all the
+necessary services in a single container. If you instead want to install GitLab
+on Kubernetes, see [GitLab Helm Charts](https://docs.gitlab.com/charts/).
 Find GitLab's official Docker image at:
 - [GitLab Docker image in Docker Hub](https://hub.docker.com/r/gitlab/gitlab-ee/)
-The Docker images do not include a mail transport agent (MTA). The recommended
-solution is to add an MTA, such as Postfix or Sendmail, running in a separate
-container. Alternatively, install an MTA directly in the GitLab container, but
-this adds maintenance overhead as you'll likely need to reinstall the MTA after
-every upgrade of restart.
+The Docker images don't include a mail transport agent (MTA). The recommended
+solution is to add an MTA (such as Postfix or Sendmail) running in a separate
+container. As another option, you can install an MTA directly in the GitLab
+container, but this adds maintenance overhead as you'll likely need to reinstall
+the MTA after every upgrade or restart.
 In the following examples, if you want to use the latest RC image, use
 `gitlab/gitlab-ee:rc` instead.
@@ -31,7 +31,7 @@ to community resources (IRC, forum, etc.) to seek help from other users.
 ## Prerequisites
-Docker is required, see the [official installation docs](https://docs.docker.com/install/).
+Docker is required. See the [official installation documentation](https://docs.docker.com/install/).
 ## Set up the volumes location
@@ -53,11 +53,11 @@ export GITLAB_HOME=$HOME/gitlab
 The GitLab container uses host mounted volumes to store persistent data:
-| Local location | Container location | Usage |
-| -------------- | ------------------ | ----- |
-| `$GITLAB_HOME/data`  | `/var/opt/gitlab` | For storing application data |
-| `$GITLAB_HOME/logs`  | `/var/log/gitlab` | For storing logs |
-| `$GITLAB_HOME/config`| `/etc/gitlab`     | For storing the GitLab configuration files |
+| Local location       | Container location | Usage                                       |
+|----------------------|--------------------|---------------------------------------------|
+| `$GITLAB_HOME/data`  | `/var/opt/gitlab`  | For storing application data.               |
+| `$GITLAB_HOME/logs`  | `/var/log/gitlab`  | For storing logs.                           |
+| `$GITLAB_HOME/config`| `/etc/gitlab`      | For storing the GitLab configuration files. |
 ## Installation
@@ -105,9 +105,9 @@ sudo docker run --detach \
 This will ensure that the Docker process has enough permissions to create the
 config files in the mounted volumes.
-If you are using the [Kerberos integration](https://docs.gitlab.com/ee/integration/kerberos.html) **(STARTER ONLY)**,
-you will also need to publish your Kerberos port (e.g., `--publish 8443:8443`).
-Failure to do so will prevent Git operations via Kerberos.
+If you're using the [Kerberos integration](https://docs.gitlab.com/ee/integration/kerberos.html) **(STARTER ONLY)**,
+you must also publish your Kerberos port (for example, `--publish 8443:8443`).
+Failing to do so prevents Git operations with Kerberos.
 The initialization process may take a long time. You can track this
 process with:
@@ -296,14 +296,14 @@ For more options about configuring GitLab, check the
 ### Pre-configure Docker container
-You can pre-configure the GitLab Docker image by adding the environment
-variable `GITLAB_OMNIBUS_CONFIG` to Docker run command. This variable can
-contain any `gitlab.rb` setting and will be evaluated before loading the
-container's `gitlab.rb` file. That way you can easily configure GitLab's
-external URL, make any database configuration or any other option from the
+You can pre-configure the GitLab Docker image by adding the environment variable
+`GITLAB_OMNIBUS_CONFIG` to Docker run command. This variable can contain any
+`gitlab.rb` setting and is evaluated before the loading of the container's
+`gitlab.rb` file. This behavior allows you to configure GitLab's external URL,
+and make database configuration or any other option from the
 [Omnibus GitLab template](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template).
-The settings contained in `GITLAB_OMNIBUS_CONFIG` will not be written to the
-`gitlab.rb` configuration file, they're evaluated on load.
+The settings contained in `GITLAB_OMNIBUS_CONFIG` aren't written to the
+`gitlab.rb` configuration file, and are evaluated on load.
 Here's an example that sets the external URL and enables LFS while starting
 the container:
@@ -507,7 +507,8 @@ Read more on how to [back up and restore GitLab](https://docs.gitlab.com/ee/rake
 [GitLab CE Docker image](https://hub.docker.com/r/gitlab/gitlab-ce/)
-To install the Community Edition, replace `ee` with `ce` in the commands on this page.
+To install the Community Edition, replace `ee` with `ce` in the commands on this
+page.
 ## Troubleshooting
@@ -597,4 +598,5 @@ If these are not correct, set them with:
 sudo setfacl -mR default:group:docker:rwx $GITLAB_HOME
 ```
-`docker` is the default group, if you've changed this, update your commands accordingly.
+The default group is `docker`. If you changed the group, be sure to update your
+commands.