anchor.diff:  
   <p class='note'><strong>Note</strong>: Binding an ASG does not affect started apps until you restart them. To restart all of the apps in an org or a space, use the <a href="https://github.com/cloudfoundry-incubator/app-restarter">app-restarter</a> cf CLI plugin.</p>
   
  -To apply an ASG to containers, you must first bind it to an ASG set.
  +To apply an ASG, you must first bind it to an ASG set.
   
   + To bind an ASG to the platform-wide staging ASG set, run the following command:
   <pre>
  
positive.code: 
  Application Security Groups (ASGs) are a collections of egress rules that
  specify the protocols, ports, and IP address ranges where app or task
  containers send traffic.
  Because ASGs define *allow* rules, their order of evaluation is unimportant
  when multiple ASGs apply to the same space or deployment.
  Containers use these rules to filter and log outbound network traffic.
  ASGs apply to both buildpack-based and Docker-based containers in both the app
  and task lifecycle phases.
  
  When apps or tasks begin staging, they need traffic rules permissive enough to
  allow them to pull resources from the network.
  
negative.code:   </tr>
    <tr>
      <td>2. </td>
      <td>Create new ASGs.</td>
      <td><a href="#asg-individual">Create ASGs</a></td>
    </tr>
    <tr>
      <td>3.</td>
      <td>Update the existing ASGs.</td>
      <td><a href="#updating-groups">Update ASGs</a></td>
    </tr>
    <tr>
      <td>4.</td>
      <td>Bind ASGs to an ASG set.</td>
      <td><a href="#binding-groups">Bind ASGs</a></td>
    </tr>
    <tr>
  