anchor.diff:    </tr>
     <tr>
       <td>1.</td>
  -    <td>Review the existing ASGs. If this is a new deployment, probably these are only the <a href="#default">Default ASGs</a>.</td>
  +    <td>Review the existing ASGs. If this is a new deployment, probably these are the <a href="#default">Default ASGs</a> alone.</td>
       <td><a href="#viewing">View ASGs</a></td>
     </tr>
     <tr>
  
positive.code: |`cf security-groups`                |All ASGs
  |`cf staging-security-groups`        |All ASGs applied to the platform-wide staging ASG set
  |`cf running-security-groups`        |All ASGs applied to the platform-wide running ASG set
  |`cf security-group SECURITY-GROUP`         |All rules in the ASG named `SECURITY-GROUP`, for example, <code>cf security-group dns</code>.
  
  ###<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. 
     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:   </tr>
    <tr>
      <td>3.</td>
      <td>Bind the new ASGs to containers or update the existing ASGs.</td>
      <td><a href="#updating-groups">Update ASGs</a></td>
    </tr>
    <tr>
  