anchor.diff:    </tr>
   </table>
   
  -Typically, ASGs applied during the staging lifecycle are more permissive than the ASGs
  -applied during the running lifecycle.
  +Typically, ASGs applied during the staging lifecycle are more permissive than 
  +the ASGs applied during the running lifecycle.
   This is because staging often requires access to different resources, such as
   dependencies.
   
   You use different commands to apply an ASG to each of the four sets. For more information, see the [Procedures](#procedures) section of this topic.
   
  -<p class="note"><strong>Note</strong>: To apply a staging ASG to apps within a space, you must use the CC API. The cf CLI <code>cf bind-security-group</code> command supports space-scoped running ASGs, but not space-scoped staging ASGs.</p>
  +<p class="note"><strong>Note</strong>: To apply a staging ASG to apps within a space, you must use the Cloud Controller (CC) API. The cf CLI <code>cf bind-security-group</code> command supports space-scoped running ASGs, but not space-scoped staging ASGs.</p>
   
   ### <a id='creating-groups'></a>The Structure and Attributes of ASGs ##
   
  
positive.code: 
  ## <a id='introduction'></a>Introduction ##
  
  This topic provides an overview of Application Security Groups (ASGs), and describes how to manage and administer them. Many of the steps below require the Cloud Foundry Command Line Interface (cf CLI) tool. 
  
  <%= vars.asg_first_time %>
  
  ###<a id="defn"></a>Application Security Groups
  
negative.code:   </tr>
    <tr>
      <td>1.</td>
      <td>Review the existing ASGs. If this is a new deployment, these like consist of only the <a href="#default">Default ASGs</a>.</td>
      <td><a href="#viewing">View ASGs</a></td>
    </tr>
    <tr>
  