anchor.diff:  
   ## Firewalled installs
   
  -If your GitHub Enterprise is behind a firewall you’ll need to allow Buildkite’s IP address so we can perform OAuth authentications use GitHub Enterprise API to update your pull request statuses.
  +If your GitHub Enterprise is behind a firewall, you need to allow Buildkite’s IP address so we can perform OAuth authentications use GitHub Enterprise API to update your pull request statuses.
   
  -All Buildkite network traffic to your GitHub Enterprise Server will come from the following IP address: `54.165.103.71`. Please configure your network to allow traffic from this IP address.
  +All Buildkite network traffic to your GitHub Enterprise Server will come from the following IP address: `54.165.103.71`. Configure your network to allow traffic from this IP address.
   
  -For additional security you can create a proxy which allows only the API endpoints we require:
  +For additional security you can create a proxy that allows only the API endpoints we require:
   
   * `/api/v3/repos/.*/.*/statuses`
   * `/api/v3/user`
   * `/login/oauth`
   
  -The following is an example [NGINX](https://www.nginx.com) server configuration that proxies the required URLs and can be used with the "Public API URL" GitHub Enterprise setting in Buildkite:
  +The following is an example [NGINX](https://www.nginx.com) server configuration that proxies the required URLs and can be used with the *Public API URL* GitHub Enterprise setting in Buildkite:
   
   ```nginx
   daemon off;
  
positive.code: 
  {:toc}
  
  ## Step 1: Register Buildkite as an OAuth App
  
  <div class="Docs__note">
  <p>This guide was written using GitHub Enterprise version 2.16.3. Earlier or later versions may have different menus and headings for the OAuth app registration. All of the Buildkite settings will remain the same.</p>
  <p>This guide describes the setup for self-hosted GitHub Enterprise Server. GitHub Enterprise Cloud users should refer to <a href="https://buildkite.com/docs/integrations/github" rel="nofollow">GitHub</a>.</p> 
  </div>
  
  In your GitHub Enterprise organization settings, select *OAuth Apps* under *Developer Settings*:
  
  
negative.code: 
  ## Step 3: Connect your GitHub Enterprise account to Buildkite
  
  For Buildkite to mark commits and pull requests as pass or fail, you need to authorize your GitHub Enterprise user account with Buildkite.
  
  1. In your Buildkite *Personal Settings*, select <a href="<%= url_helpers.user_authorizations_url %>" rel="nofollow">Connected Apps</a>. Here you'll see your GitHub Enterprise Server along with any other connected apps. 
  2. Select *Connect* next to *GitHub Enterprise*:
  
    <%= image "buildkite-connected-apps-settings.png", width:1960/2, height:622/2, alt:"Screenshot of the Connected Apps page in Buildkite Personal Settings with the GitHub Enterprise App" %>
  
  3. Buildkite redirects you back to your GitHub Enterprise Server, where it asks you to authorize your new Buildkite OAuth app to use your GitHub Enterprise account. Select *Authorize* to complete your setup:
  
  <%= image "authorize-buildkite.png", width:1128/2 , height:1392/2, alt:"Screenshot of the Authorization page in GitHub Enterprise" %>
  
  