anchor.diff:  
   ### <a name="enable_org_is"></a> Enable an Org to Use Isolation Segments
   
  -Only admins can enable orgs to use isolation segments. Run `cf enable-org-isolation ORG-NAME SEGMENT-NAME` to enable the use of an isolation segment. Replace `ORG-NAME` with the name of your org, and `SEGMENT-NAME` with the name of the isolation segment.
  -
  -For example:
  -
  -<pre class="terminal">
  -$ cf enable-org-isolation org2 my_segment
  -</pre>
  +Only admins can enable orgs to use isolation segments.
  +
  +To enable the use of an isolation segment:
  +
  +1. Log in to your deployment by running:
  +
  +    ```
  +    cf login
  +    ```
  +
  +1. Run:
  +
  +    ```
  +    cf enable-org-isolation ORG-NAME SEGMENT-NAME
  +    ```
  +    Where:
  +    * `ORG-NAME` is the name of your org.
  +    * `SEGMENT-NAME` is the name of the isolation segment you want your org to use.
   
   If an org is entitled to use only one isolation segment, that isolation segment does not automatically become the default isolation segment for the org. You must explicitly set the default isolation segment of an org. For more information, see [Set the Default Isolation Segment for an Org](#set_org_default_is).
   
  
positive.code: 
  <%= vars.isolation_segments_note %>
  
  The following command creates an isolation segment named `my_segment`:
  
  <pre class="terminal">
  $ cf create-isolation-segment my_segment
  </pre>
  
  If successful, the command returns an `OK` message:
  
  <pre class="terminal">
  Creating isolation segment my_segment as admin...
  OK
  </pre>
  
  
negative.code: 
  ## <a name='requirements'></a> Requirements
  
  You must have Cloud Foundry Command Line Interface (cf CLI) v.6.26.0 or later installed to manage isolation segments. To download the latest version of the cf CLI, see the [Releases](https://github.com/cloudfoundry/cli/releases) section of the Cloud Foundry CLI repository on GitHub. For more information about installing the cf CLI, see [Installing the cf CLI](../cf-cli/install-go-cli.html).
  
  Target the API endpoint of your deployment with `cf api` and log in with `cf login` before performing the procedures in this topic. <%= vars.api_endpoint_book %>
  
  