anchor.diff:  edit the ones you create in their project. There are also several other
   restrictions on where `EgressNetworkPolicy` can be created:
   
  -. The `default` project (and any other project that has been made global via
  +* The `default` project (and any other project that has been made global via
   `oadm pod-network make-projects-global`) cannot have egress policy.
   
  -. If you merge two projects together (via `oadm pod-network join-projects`),
  +* If you merge two projects together (via `oadm pod-network join-projects`),
   then you cannot use egress policy in _any_ of the joined projects.
   
  -. No project may have more than one egress policy object.
  -
  -Violating any of these restrictions will result in broken egress policy for the
  +* No project may have more than one egress policy object.
  +
  +Violating any of these restrictions results in broken egress policy for the
   project, and may cause all external network traffic to be dropped.
   
  -[[admin-guide-config-pod-access]]
  -==== Configuring Pod Access Limits
  -
  -To configure pod access limits, you must use the `oc` command or the REST API.
  -You can use `oc [create|replace|delete]` to manipulate `EgressNetworkPolicy`
  -objects. The *_api/swagger-spec/oapi-v1.json_* file has API-level details on how
  -the objects actually work.
  -
  -To configure pod access limits:
  +Use the `oc` command or the REST API to configure egress policy. You can use
  +`oc [create|replace|delete]` to manipulate `EgressNetworkPolicy` objects. The
  +*_api/swagger-spec/oapi-v1.json_* file has API-level details on how the objects
  +actually work.
  +
  +To configure egress policy:
   
   . Navigate to the project you want to affect.
  -. Create a JSON file for the pod limit policy:
  -+
  -----
  -# oc create -f <policy>.json
  -----
  -. Configure the JSON file with policy details. For example:
  +
  +. Create a JSON file with the desired policy details. For example:
   +
   ----
   {
  
positive.code: `20.21.22.23`. Then, {product-title} will take up to 30 minutes to adapt to
  these DNS updates.
  
  [[admin-guide-manage-pods-limit-bandwidth]]
  == Limiting the Bandwidth Available to Pods
  
  
negative.code: - A pod cannot reach specified internal subnets/hosts that it should have no
  reason to contact.
  
  You can configure projects to have different egress policies. For example,
  allowing `<project A>` access to a specified IP range, but denying the same
  access to `<project B>`. Or restrict application developers from updating from
  (Python) pip mirrors, and forcing updates to only come from desired sources.
  
  [CAUTION]
  ====
  