anchor.diff:  
   <% else %>
   
  -This topic describes <%= vars.app_runtime_first %> and how it works with <%= vars.platform_name %>.
  +This topic describes <%= vars.app_runtime_first %> and how it works with <%= vars.ops_manager %>.
   
   <% end %>
   
  
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:   </tr>
    <tr>
      <td>First UAA server</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.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>
  
  