anchor.diff:    </tr>
     <tr>
       <td><ul><li>Source code</li><li>Buildpacks</li><li>Documentation</li><li>Custom configurations</li><li>Other platform resources</li></ul></td>
  -    <td><a href="https://github.com/">GitHub</a></td>
  +    <td>GitHub</td>
     </tr>
     <tr>
       <td><ul><li>Large binary files</li><li>Droplets</li></ul></td>
  
positive.code:   </tr>
  </table>
  
  ### <a id='communicate'></a>Component Communication
  
  This section describes how Cloud Foundry components communicate with one another.
  
  Cloud Foundry components communicate in the following ways:
  
  * By sending messages internally using HTTP and HTTPS protocols
  * By sending NATS messages to each other directly
  
negative.code:   </tr>
    <tr>
      <td>First UAA server</td>
      <td><ul><li>Grants access to BOSH</li><li>Holds accounts for <%= vars.platform_name %> operators who deploy runtimes, services, and other software onto the BOSH layer directly</li></ul></td>
    </tr>
    <tr>
      <td>Second UAA server</td>
      <td><ul><li>Controls access to the Cloud Controller</li><li>Defines user roles, such as admin, developer, or auditor, and grants them different sets of privileges to run <%= vars.platform_name %> commands</li><li>Scopes the roles to separate, compartmentalized orgs and spaces within an installation to manage and track use</li></ul></td>
    </tr>
  </table>
  
  For more information, see [Orgs, Spaces, Roles, and Permissions](./roles.html).
  
  ### <a id='resources'></a> Storing Resources
  
  The following table describes where <%= vars.app_runtime_abbr %> stores resources:
  
  <table>
    <tr>
  