anchor.diff:          <li>Maintains a database of policies for traffic between apps. 
               The cf CLI plugin calls an API to create or update a record 
               in the policy database whenever you create or remove a policy.</li>
  -        <li>Exposes a JSON REST API used by the cf CLI plugin</li>
  +        <li>Exposes a <a href="https://github.com/cloudfoundry-incubator/netman-release/blob/develop/docs/API.md">JSON REST API</a> used by the cf CLI plugin</li>
         </ul></td>
     </tr>
     <tr>
  
positive.code: ###<a id="overview"></a> Overview
  
  Enabling container networking for your deployment allows you to create policies for communication between containers. 
  The container-networking feature also provides a unique IP address to each container that is accessible outside of the 
  Diego cell on which the container runs, allowing you to know which container traffic comes from. 
  
  The policies you create specify a source app, destination app, protocol, and port so that apps can communicate directly 
  without going through the Gorouter, a load balancer, or a firewall. 
  
negative.code:     <td> 
        A Garden-runC add-on deployed to every Diego cell that does the following:
        <ul>
          <li>Invokes the CNI plugin component to attach the container to the network</li>
          <li>Forwards ports to support incoming connections from the Gorouter, TCP Router, and Diego SSH Proxy. 
              This keeps apps externally reachable.</li>
          <li>Installs outbound whitelist rules to support CF Application Security Groups (ASGs). 
  