anchor.diff:  
   ###<a id='asg-individual'></a>Create ASGs
   
  -To create an ASG, perform the following steps: 
  -
  -1. Create a rules file: a JSON-formatted single array containing objects that describe the rules. 
  +To create an ASG, perform the following steps:
  +
  +1. Create a rules file: a JSON-formatted single array containing objects that describe the rules.
      See the following example, which allows ICMP traffic of code `1` and type `0` to all destinations,  and TCP traffic to `10.0.11.0/24` on ports `80` and `443`. Also see [The Structure and Attributes of ASGs](#creating-groups).
   
       <pre>
  
positive.code: 
  ### <a id="asg-sets"></a> ASG Sets
  
  ASG sets are sets of containers to which the ASGs are applied. 
  These sets of containers are differentiated by _scope_, platform-wide or 
  space-specific containers, and _function_, staging or running containers. 
  
  Currently, four ASG sets exist in Cloud Foundry:
  
  
negative.code: $ cf update-security-group my-asg ~/workspace/my-asg-v2.json
  </pre>
  
  <p class='note'><strong>Note</strong>: Updating 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>
  
  ### <a id='unbinding-groups'></a>Unbind ASGs
  
  <p class='note'><strong>Note</strong>: Unbinding 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 unbind an ASG from the platform-wide staging ASG set, run the following command:
  