anchor.diff:    </tr>
   </table>
   
  -###<a id='swap'></a> Swappable Components
  +### <a id='swap'></a> Swappable Components
   
   The Container-to-Container Networking BOSH release includes the following swappable components:
   
  
positive.code: 
  <% if vars.product_name.include? "CF" %>
  
  ##<a id='service-discovery'></a> App Service Discovery (Experimental)
  
  The <%= vars.product_full %> platform supports DNS-based service discovery that lets apps find each others' internal addresses. For example, a front-end app instance can use the service discovery mechanism to establish communications with a back-end app instance. See the [Developer Guide](../devguide/deploy-apps/cf-networking.html#discovery) for how to set up and use app service discovery.
  
  
negative.code:   </tr>
  </table> 
  
  
  ## <a id='app-comm'></a> App Instance Communication
  
  The diagram below illustrates how app instances communicate in a deployment with Container-to-Container Networking enabled. 
  In this example, the operator creates two policies to regulate the flow of traffic between **App A**, **App B**, and **App C**. 
  