Update worker-configuration.md

Author: nrios14

user/enterprise/worker-configuration.md

@@ -13,7 +13,7 @@ The following section shows how to connect to the platform with different Ubuntu
 ### Connect with Ubuntu 16.04
 
 The configuration for connecting to the Travis CI Enterprise platform can be found in `/etc/default/travis-worker`.
-If you need to change the hostname the Worker should connect to, or the
+If you need to change the hostname the Worker should connect to or the
 RabbitMQ password, you can do so by updating:
 
 ```sh
@@ -23,10 +23,10 @@ export AMQP_URI="amqp://travis:<rabbitmq password>@<your-travis-ci-enterprise-do
 ### Connect with Ubuntu 14.04
 
 The configuration for connecting to the Travis CI Enterprise Platform,
-including the RabbitMQ password, can be found in
+including the RabbitMQ password, which can be found in
 `/etc/default/travis-enterprise`.
 
-If you need to change the hostname the Worker should connect to, or the
+If you need to change the hostname the Worker should connect to or the
 RabbitMQ password, you can do so by updating:
 
 ```sh
@@ -37,7 +37,7 @@ export TRAVIS_ENTERPRISE_SECURITY_TOKEN="super-secret-password"
 ## Set Timeouts
 
 The following options can be customized in `/etc/default/travis-worker`.
-It is recommended to have all Workers use the same config.
+It is recommended that all workers use the same configuration.
 
 By default, jobs can run for a maximum of 50 minutes. You can increase or
 decrease this using the following setting:
@@ -46,7 +46,7 @@ decrease this using the following setting:
 export TRAVIS_WORKER_HARD_TIMEOUT="50m"
 ```
 
-If no log output has been received for more than 10mins, the job is cancelled as
+If no log output has been received for more than 10 mins, the job is canceled as
 it is assumed the job stalled. You can customize this timeout using the
 following setting:
 
@@ -62,7 +62,7 @@ allowed for a job to use are configured with the
 variables, respectively. Each Job requires a minimum of 2 CPUs, and by
 default, each Worker runs 2 jobs. The product of
 `TRAVIS_WORKER_POOL_SIZE * TRAVIS_WORKER_POOL_SIZE` cannot exceed the
-number of CPUs the worker machine has, otherwise jobs will error and
+number of CPUs the worker machine has; otherwise, jobs will error and
 requeue.
 
 To change the number of concurrent jobs allowed for a worker to use,
@@ -81,8 +81,8 @@ export TRAVIS_WORKER_DOCKER_CPUS=2
 ```
 
 To completely disable this setting, set the value to 0. Then
-resources will be used as needed, which means a single job can for
-example use all CPU cores.
+resources will be used as needed, which means a single job can be for
+example, use all CPU cores.
 
 ```sh
 export TRAVIS_WORKER_DOCKER_CPUS=0
@@ -92,7 +92,7 @@ export TRAVIS_WORKER_DOCKER_CPUS=0
 ## Change the Worker Hostname
 
 Each Worker should have a unique hostname, making it easier to determine
-where jobs ran. By default this is set to the `hostname` of the host the
+where jobs run. By default, this is set to the `hostname` of the host the
 Worker is running on.
 
 ```sh
@@ -152,7 +152,7 @@ export TRAVIS_WORKER_MAX_LOG_LENGTH=40000000
 
 You can use [Docker bind mounts](https://docs.docker.com/storage/bind-mounts/)
 when the worker launches the container of a job. This lets you share files or directories
-across all jobs ran by a worker. Multiple binds can be provided
+across all jobs run by a worker. Multiple binds can be provided
 as _space separated_ strings.
 
 For example, the setting below shows how to share the `/tmp` directory in read/write mode,
@@ -202,17 +202,17 @@ export TRAVIS_WORKER_DOCKER_HTTP_PROXY="<YOUR PROXY URL>"
 export TRAVIS_WORKER_DOCKER_API_VERSION=1.35
 ```
 
-In this example we've used Docker-CE 17.12. According to the [API mismatch table](https://docs.docker.com/develop/sdk/#docker-ee-and-ce-api-mismatch) we need to choose `1.35` for `TRAVIS_WORKER_DOCKER_API_VERSION`.
+In this example, we've used Docker-CE 17.12. According to the [API mismatch table](https://docs.docker.com/develop/sdk/#docker-ee-and-ce-api-mismatch) we need to choose `1.35` for `TRAVIS_WORKER_DOCKER_API_VERSION`.
 
-Below you can find the full list of available environment variables and how they're accessible during the build:
+Below, you can find the full list of available environment variables and how they're accessible during the build:
 
 Environment variable | Available as:
 `TRAVIS_WORKER_DOCKER_HTTP_PROXY` | `HTTP_PROXY`, `http_proxy`
 `TRAVIS_WORKER_DOCKER_HTTPS_PROXY` | `HTTPS_PROXY`, `https_proxy`
 `TRAVIS_WORKER_DOCKER_NO_PROXY` | `NO_PROXY`, `no_proxy`
 `TRAVIS_WORKER_DOCKER_FTP_PROXY` | `FTP_PROXY`, `ftp_proxy`
 
-> Please note, that all `apt-get` commands by default respect `TRAVIS_WORKER_DOCKER_HTTP_PROXY` and `TRAVIS_WORKER_DOCKER_HTTPS_PROXY` which means that all package installs will go via the HTTP Proxy as well. If you don't want this to happen, please whitelist your apt package mirror by adding it to TRAVIS_WORKER_DOCKER_NO_PROXY` like this:
+> Please note that all `apt-get` commands by default respect `TRAVIS_WORKER_DOCKER_HTTP_PROXY` and `TRAVIS_WORKER_DOCKER_HTTPS_PROXY`, which means that all package installs will go via the HTTP Proxy as well. If you don't want this to happen, please whitelist your apt package mirror by adding it to TRAVIS_WORKER_DOCKER_NO_PROXY` like this:
 
 ```
 export TRAVIS_WORKER_DOCKER_NO_PROXY='.ubuntu.com,packagecloud.io,.postgresql.org'
@@ -222,15 +222,15 @@ export TRAVIS_WORKER_DOCKER_NO_PROXY='.ubuntu.com,packagecloud.io,.postgresql.or
 
 After running the `lxd_install.sh` the LXD worker configuration is stored in `/var/snap/travis-worker/common/worker.env`. 
 
-All parameters mentioned on this page with the exception of Docker parameters apply to LXD.
+All parameters mentioned on this page, with the exception of Docker parameters, apply to LXD.
 Below you can find a list of available parameters:
 
 Parameters | Definition:
 `TRAVIS_WORKER_LXD_CPUS` | defines how many CPU's can be used by LXD, the default is `2`.
 `TRAVIS_WORKER_LXD_CPUS_BURST` | defines if all CPU's can be used by LXD if not already in use, the default is `True`.
 `TRAVIS_WORKER_LXD_DISK` | LXD disk size limit, the default is `20Gb`.
-`TRAVIS_WORKER_LXD_ARCH_OVERRIDE` | overrides the architecture defined in the job configuration, not present by default.
-`TRAVIS_WORKER_LXD_MEMORY` | defines the memory available for each container, the default is `4Gb`.
+`TRAVIS_WORKER_LXD_ARCH_OVERRIDE` | overrides the architecture defined in the job configuration, which is not present by default.
+`TRAVIS_WORKER_LXD_MEMORY` | defines the memory available for each container; the default is `4Gb`.
 `TRAVIS_WORKER_LXD_NETWORK` | defines the network bandwidth, the default is `1Gb`.
 
 ## Contact Enterprise Support