anchor.diff:  * Allow traffic from **App A** to **App B**
   * Allow traffic from **App A** to **App C**
   
  -If traffic and its direction is not explicitly allowed, it is denied. In this case, **App B** cannot send traffic to **App C**.
  +If traffic and its direction is not explicitly allowed, it is denied. For example, **App B** cannot send traffic to **App C**.
   
   ![Post Container Networking](./images/post-c2c.png)
   
  
positive.code:     <li>Open the CF properties stub that you created when <a href="http://docs.cloudfoundry.org/deploying/index.html">deploying Cloud Foundry</a>
          and do the following:
      <ol type="a">
          <li>Under <code>properties</code> > <code>uaa</code> > <code>scim</code> > <code>users</code> > <code>name: admin</code> > <code>groups</code>, add a new group called <code>network.admin</code>.</li>
          <li>Under <code>properties</code> > <code>uaa</code> > <code>clients</code> > <code>cf</code>, to the line beginning <code>scope: </code>
          add <code>network.admin</code>.</li>
          <pre>
  
negative.code: 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. 
  Container networking in CF supports UDP and TCP, and you can configure policies for multiple ports. 
  These policies are applied immediately without having to restart the app. For more information, see the [Create Policies for Container Networking](#create-policies) section.
  
  The container-networking BOSH release is composed of a pluggable network stack, which means you can swap several components. 
  For more information, see [Architecture](#architecture) below. 
  