anchor.diff:  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).
  +   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`. For more information, see [The Structure and Attributes of ASGs](#creating-groups) above.
   
       <pre>
       [
  
positive.code: 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 cf CLI v6.28.0 or later.
  </p>
  
negative.code: Network connections that are commonly allowable in private networks include
  endpoints such as proxy servers, Docker registries, load balancers, databases,
  messaging servers, directory servers, and file servers. Configure appropriate
  private network ASGs as appropriate. You might find it helpful to use a naming
  convention with `private_networks` as part of the ASG name, such as `private_networks_databases`.
  
  <p class='note'><strong>Note</strong>: You should exclude any private networks and IP addresses that app and task instances should not have access to.
  