Update setting-up-travis-ci-enterprise.md

Author: nrios14

user/enterprise/setting-up-travis-ci-enterprise.md

@@ -27,7 +27,7 @@ Platform* which hosts the web UI and related services, and one or more
 *Worker hosts* which run the tests/jobs in isolated containers using LXC
 and Docker.
 
-Each dedicated host or hypervisor (VMWare, OpenStack using KVM, or EC2) should run **Ubuntu 16.04**, ideally using Linux 3.16 and have at least **16 gigs of RAM and 8 CPUs**.
+Each dedicated host or hypervisor (VMWare, OpenStack using KVM, or EC2) should run **Ubuntu 16.04**, ideally using Linux 3.16, and have at least **16 gigs of RAM and 8 CPUs**.
 
 If you're running on EC2, we recommend the **c4.2xlarge** instance type for both **Platform** and **Worker**. We also recommend using an image that uses EBS for the root volume, as well as allocating 40 gigs of space to it.
 
@@ -43,7 +43,7 @@ You can also try services like [compose.com](https://compose.com/), if you would
 
 The Travis CI Enterprise Platform handles licensing, coordinates worker
 processes, and maintains the Enterprise user and admin dashboard. It must be
-installed on it's own machine instance, separate from that of the Travis CI
+installed on its own machine instance, separate from that of the Travis CI
 Enterprise worker. We recommend using AWS' `c4.2xlarge` instance running
 Ubuntu 16.04 LTS or later as the underlying operating system.
 
@@ -77,18 +77,18 @@ installation's hostname, port 8800) to complete the setup:
 
    1. Add a secure certificate or configure a trusted one.
    1. Upload your Travis CI Enterprise license.
-   1. Configure access to the Admin Console with a password or using openLDAP. This controls access to the Admin Console itself, not to the Travis CI Enterprise instance.
+   1. Configure access to the Admin Console with a password or using OpenLDAP. This controls access to the Admin Console, not the Travis CI Enterprise instance.
    1. Connect your GitHub Enterprise or GitHub.com with Travis CI enterprise.
    1. Optionally, configure Email, Metrics and Caches.
    1. Copy the *RabbitMQ password* for the Worker setup.
 
-> If you have decided to use a self-signed certificate, there may be additional configuration steps required. Please see our page on [SSL Certificate Management](/user/enterprise/ssl-certificate-management/) for more information.
+> Additional configuration steps may be required if you have decided to use a self-signed certificate. For more information, please see our page on [SSL Certificate Management](/user/enterprise/ssl-certificate-management/).
 
 ## Setup the Enterprise Worker virtual machine
 
-The Travis CI Enterprise Worker manages build containers and reports build
-statuses back to the platform. It must be installed on a separate machine
-instance from the Platform. We recommend using instance running Ubuntu 16.04 LTS or later as the underlying operating system.
+The Travis CI Enterprise Worker manages build containers, and reports build
+statuses to the platform. It must be installed on a separate machine
+instance from the Platform. We recommend using instances running Ubuntu 16.04 LTS or later as the underlying operating system.
 
 Make sure you have already [set up the Enterprise Platform](/user/enterprise/setting-up-travis-ci-enterprise/#1-setting-up-enterprise-platform-virtual-machine) and have the *RabbitMQ password* and the *hostname* from the Platform Dashboard.