anchor.diff:  
   <% else %>
   
  -This topic describes <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>) and how it works with Cloud Foundry.
  +This topic describes <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>) and how it works with <%= vars.platform_name %>.
   
   <% end %>
   
  -## <a id='overview'></a>Overview
  +## <a id='overview'></a> Overview
   
   Cloud platforms let anyone deploy network apps or services and make them available to the world in a few minutes. When an app becomes popular, the cloud scales it to handle more traffic, replacing build-out and migration efforts that once took months with a few keystrokes. Cloud platforms enable you to focus exclusively on your apps and data without worrying about underlying infrastructure.
   
  
positive.code: 
  For more information, see <%= vars.loggregator_arch_link %>.
  
  ### <a id='services'></a>Using Services
  
  This section describes how you can use services with your apps on Cloud Foundry.
  
  Typical apps depend on free or metered services such as databases or third-party APIs. To incorporate these into an app:
  
  1. **Write a Service Broker**: This component manages the life cycle of the service. The Service Broker uses the Service Broker API to advertise a catalog of service offerings to Cloud Foundry apps.
  1. **Provision the Service Instance**: Create an instance of the service offering by sending a provision request to the Service Broker API.
  1. **Enable apps to access the Service Instance**: Configure the Cloud Foundry app to make calls to the Service Instance using the Service Broker API.
  
  For more information, see [Services](../services/index.html).
  
  
negative.code:   </tr>
  </table>
  
  ### <a id='communicate'></a> Component Communication
  
  This section describes how <%= vars.app_runtime_abbr %> components communicate with one another.
  
  <%= vars.app_runtime_abbr %> components communicate in the following ways:
  
  * By sending messages internally using HTTP and HTTPS protocols
  * By sending NATS messages to each other directly
  