anchor.diff:  
   In a Cloud Foundry deployment without Diego, the [Cloud Controller](../architecture/cloud-controller.html) schedules and manages applications on the [Droplet Execution Agent](../architecture/execution-agent.html) (DEA) nodes. Diego replaces the DEAs and the [Health Manager (HM9000)](./dea-vs-diego.html#hm9k), and assumes application scheduling and management responsibility from the Cloud Controller.
   
  -Refer to the diagram and descriptions below for information about the way Diego handles application requests.
  +Refer to the following diagram and descriptions for information about the way Diego handles application requests.
   
   <%= image_tag("../images/diego/diego-flow.png") %>
   
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  This topic provides an overview of the high-level structure of Diego, the next-generation container management system for Cloud Foundry (CF).
  
  <ul>
  <%=vars.diego_deploy %>
  
negative.code: 
  1. The BBS tracks desired LRPs, running LRP instances, and in-flight Tasks for the [Converger](./diego-components.html#converger), part of the [Diego Brain](./diego-components.html#brain-components). The Converger periodically analyzes this information and corrects discrepancies to ensure consistency between `ActualLRP` and `DesiredLRP` counts.
  
  1. The [Metron Agent](./diego-components.html#metron-agent), part of the Cell, forwards application logs, errors, and metrics to the Cloud Foundry Loggregator. For more information, see the [Application Logging in Cloud Foundry](../../devguide/deploy-apps/streaming-logs.html) topic.