anchor.diff:  
   <%=vars.pcf_pools%>
   
  -<%=vars.om_resurrector_header%>
  -<%=vars.om_resurrector_text%>
  +#### <a id='databases'></a>Databases ####
   
  +For database services deployed outside Cloud Foundry, plan to leverage your infrastructure's high availability features and to configure backup and restore where possible. <%= vars.scaling_ert_db %>
   
  -### <a id='databases'></a>Databases ###
  -
  -For scaling internal database components, <%= vars.scaling_ert %>. For database services deployed outside Cloud Foundry, plan to leverage your infrastructure's high availability features and to configure backup and restore where possible.
  +<p class="note"><strong>Note</strong>: Data services may have single points of failure depending on their configuration.</p>
   
   <%= vars.contact_support %>
   
  
positive.code: 
  ### Supporting Component Scaling
  
  ####Space####
  
  Ensure that you allocate and maintain enough of the following:
  
  * Free space on Diego Cells so that apps expected to deploy can successfully be staged and run.
  * Disk space and memory in your deployment such that if one Diego Cell is down, all instances of apps can be placed on the remaining Diego Cells.
  * Free space to handle one AZ going down if deploying in multiple AZs.
  
  ####Resource pools####
  
negative.code: 
  <%= image_tag("scale_cf.png", :height => "450px", :width => "475px") %>
  
  Scaling up the following components increases your capacity to host applications. The nature of the applications you host on Cloud Foundry should determine whether you scale vertically or horizontally.
  
  * **Diego cells**: The optimal balance between CPU/memory sizing and instance count depends on the performance characteristics of the apps that run on Diego cells. Scaling vertically with larger Diego cells makes for larger points of failure, and more apps go down when a cell fails. On the other hand, scaling horizontally decreases the speed at which the system rebalances apps. Rebalancing 100 cells takes longer and demands more processing overhead than rebalancing 20 cells.
  * **Router**: Scale the router to accommodate the number of incoming requests. In general, this load is much less than the load on Diego cells.
  * **Cloud Controller**: Scale the Cloud Controller to accommodate the number of requests to the API and the number of apps in the system.
  
  
  ## <a id='zero-downtime'></a>High Availability and Zero Downtime ##
  