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: 
  ## Step 2: Update your Buildkite organization settings
  
  1. Open your Buildkite organization's Settings and choose [Repository Providers](https://buildkite.com/organizations/~/repository-providers)
  2. Click GitHub Enterprise Server and enter
     - The URL and public proxy URL of your GitHub Enterprise Server
     - The  Client ID and Client Secret from the GitHub OAuth App you created in Step 1
  
  3. If you're using self-signed certificates, make sure the *Verify TLS Certificate* checkbox is not checked.
  
  Select *Save GitHub Enterprise Settings* to save your settings. After saving, the *Secret* field appears blank - Buildkite has saved it, and will not display it.
  
  <%= image "buildkite-github-enterprise-settings.png", width:1738/2, height:1216/2, alt:"Screenshot of the GitHub Enterprise settings section in Buildkite" %>
  
  
negative.code: 
  {:toc}
  
  <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>
  
  ## Step 1: Register Buildkite as an OAuth app
  
  In your GitHub Enterprise organization settings, select *OAuth Apps* under *Developer Settings*:
  
  