anchor.diff:    </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>
  +    <td><ul><li>Grants access to BOSH</li><li>Holds accounts for <%= vars.ops_manager %> 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>
  +    <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.app_runtime_abbr %> 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>
   
  
positive.code: 
  ### <a id='apps-anywhere'></a> Running Apps
  
  This section describes the VMs that run your apps in <%= vars.platform_name %> and how the platform packages your apps to run on these VMs.
  
  #### <a id='cf-vms'></a> VMs in <%= vars.platform_name %>
  
  <%= vars.platform_name %> designates the following types of VMs:
  
  - **Component VMs** make up the platform's infrastructure.
  - **Host VMs** host your apps for the outside world.
  
  Within <%= vars.platform_name %>, the Diego system distributes the hosted app load over all of the host VMs, and keeps it running and balanced through demand surges, outages, or other changes. Diego accomplishes this through an auction algorithm.
  
  For more information, see [Diego Components and Architecture](./diego/diego-architecture.html).
  
  
negative.code: See the following sections in this topic:
  
  <ul>
    <li><a href="#about">About <%= vars.app_runtime_abbr %></a></li>
    <li><a href="#how-it-works">How <%= vars.app_runtime_abbr %> Works</a></li>
    <%= vars.concepts_product_model_link %>
  </ul>
  
  
  ## <a id='about'></a> About <%= vars.app_runtime_abbr %>
  
  This section describes why <%= vars.app_runtime_abbr %> is an industry-standard cloud platform.
  
  Not all cloud platforms are created equal. Some have limited language and framework support, lack key app services, or restrict deployment to a single cloud.
  
  As an industry-standard cloud platform, <%= vars.app_runtime_abbr %> offers the following:
  
  * **Open source code**: The platform's openness and extensibility prevent its users from being locked into a single framework, set of app services, or cloud. For more information, see the [Cloud Foundry](https://github.com/cloudfoundry) project on GitHub.
  
  * **Deployment automation**: Developers can deploy their apps to <%= vars.app_runtime_abbr %> using their existing tools and with zero modification to their code.
  
  * **Flexible infrastructure**: You can deploy <%= vars.app_runtime_abbr %> to run your apps on your own computing infrastructure, or deploy on an IaaS like vSphere, AWS, Azure, GCP, or OpenStack.
  
  * **Commercial options**: You can also use a PaaS deployed by a commercial <%= vars.app_runtime_abbr %> cloud provider. For more information, see [Cloud Foundry Certified Platforms](https://www.cloudfoundry.org/certified-platforms/).
  
  * **Community support**: A broad community contributes to and supports <%= vars.app_runtime_abbr %>. See [Welcome to the Cloud Foundry Community](https://www.cloudfoundry.org/community/).
  
  <%= vars.app_runtime_abbr %> is ideal for anyone interested in removing the cost and complexity of configuring infrastructure for their apps.
  
  
  ## <a id='how-it-works'></a> How <%= vars.app_runtime_abbr %> Works
  
  To flexibly serve and scale apps online, <%= vars.app_runtime_abbr %> has subsystems that perform specialized functions. The sections below describe how some of these main subsystems work.
  
  ### <a id='balances'></a> Load Balancing
  
  This section describes how <%= vars.app_runtime_abbr %> handles load balancing.
  
  Clouds balance their processing loads over multiple machines, optimizing for efficiency and resilience against point failure. A <%= vars.app_runtime_abbr %> installation accomplishes this using the following components:
  
  - **BOSH** creates and deploys VMs on top of a physical computing infrastructure, and deploys and runs <%= vars.app_runtime_abbr %> on top of this cloud. To configure the deployment, BOSH follows a manifest document. For more information, see the [BOSH documentation](http://bosh.io).
  
  - **Cloud Controller** runs the apps and other processes on the cloud's VMs, balancing demand and managing app lifecycles. For more information, see [Cloud Controller](./architecture/cloud-controller.html).
  
  