anchor.diff:  For example, 
   <pre class="terminal">$ cf create-security-group my-asg ~/workspace/my-asg.json</pre>
   
  -After the ASG is created, it must be bound to an ASG set before it takes effect. 
  +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>
  +<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.
   
  
positive.code: Additionally, the payload returned from API `GET` calls to
  `/v2/spaces/` and `/v2/spaces/:guid` includes a link to the `staging_security_groups_url`.
  
      For more information on using these CC API commands, see the [Cloud Foundry API](https://apidocs.cloudfoundry.org/) documentation.
  
  ### <a id='updating-groups'></a>Update ASGs 
  
  
negative.code: ## Process for Administering ASGs
  
  The following table outlines the flow of tasks that the administrator carries out over the lifecycle of ASGs.
  Procedures for each of these tasks are given in the [Procedures for Working with ASGs](#procedures) section of this topic.
  <table>
    <tr>
      <th></th>
  