anchor.diff:  ### <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, there are four ASG sets in Cloud Foundry:
  +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:
   
   + Platform-wide staging ASG set (also called default-staging)
   + Platform-wide running ASG set (also called default-running)
  
positive.code: 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 example below, 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>
      [
  
negative.code: For example, 
  <pre class="terminal">$ cf create-security-group my-asg ~/workspace/my-asg.json</pre>
  
  After the ASG is created, you must bind it to an ASG set before it takes effect. 
  See <a href="#binding-groups">Bind ASGs</a> below.
  
  ### <a id='binding-groups'></a>Bind ASGs ##
  
  <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.
  
  