anchor.diff:      <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>scim</code> > <code>users</code> > <code>name: admin</code> > <code>groups</code>, add a new group called <code>network.admin</code>.
  +        <pre>
  +scim:
  +  users:
  +  - name: admin
  +    password: <admin-password>
  +    groups:
  +      - scim.write
  +      - scim.read
  +      ...
  +      - routing.router_groups.write
  +      <b>- network.admin</b>
  +        </pre></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>
  
positive.code: 
  ##<a id="about"></a>About Container Networking
  
  See the following sections to understand how container networking works in CF. 
  The Diego cells that host apps in CF run each app instance in a container. 
  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. 
  
  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 
  
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. 
  