anchor.diff:      <td> 
         A Garden-runC add-on deployed to every Diego cell that does the following:
         <ul>
  -        <li>Invokes the CNI Plugin component to set up the network for each app instance</li>
  -        <li>Forwards ports to support incoming connections from the CF HTTP Router, TCP Router, and Diego SSH Proxy. This keeps application instances externally reachable.</li>
  +        <li>Invokes the CNI Plugin component to set up the network for each app</li>
  +        <li>Forwards ports to support incoming connections from the CF HTTP Router, TCP Router, and Diego SSH Proxy. 
  +            This keeps apps externally reachable.</li>
           <li>Installs outbound whitelist rules to support CF Application Security Groups (ASGs). See the <a href="app-sec-groups.html">ASG documentation</a>.</li>
         </ul>
       </td>
  
positive.code:   </tr>
    <tr>
    <td>Flannel CNI plugin</td>
    <td>A plugin that provides IP address management and network connectivity to app instances.
    <ul>
    <li>Acquires IP address of container and relays to Garden</li>
    <li>Installs network interface in container using the the flannel VXLAN backend. This is a shared, flat L3 network.</li>
  
negative.code: Without container networking, all app to app traffic must go through the Gorouter. 
  With container networking, apps can communicate directly. 
  
  ###<a id="overview"></a> Overview
  
  You can enable container networking in CF by adding the container-networking BOSH release to your deployment. 
  
  