anchor.diff:  $ cf disable-org-isolation org1 my_segment
   </pre>
   
  -If succesful, the command outputs the following:
  +If successful, the command outputs the following:
   <pre class="terminal">
   Removing entitlement to isolation segment segment1 from org org1 as admin...
   OK
   </pre>
   
  -<p class='note'><strong>Note</strong>: You cannot remove an org from an isolation segment if the isolation segment contains a space within that org or if it is the default isolation segment for that org.</p>
  -
  -### <a id="set_org_default_is"></a> Set a Default Isolation Segment for an Org
  -
  -Only admins and org managers can set the default isolation segment of an org.
  -
  -When an org has a default isolation segment, new spaces created within the org will be in this default isolation segment unless specified otherwise.
  -
  -You set the default isolation segment for an org by sending a request to the endpoint for the organization, setting its `default_isolation_segment_guid` data property to the GUID of the new default isolation segment. For example:
  +### <a id="set_org_default_is"></a> Set the Default Isolation Segment for an Org
  +
  +Only admins and org managers can set the default isolation segment for an org.
  +
  +When an org has a default isolation segment, new spaces created within the org are assigned to the default isolation segment unless specified otherwise.
  +
  +You set the default isolation segment for an org by sending a request to the endpoint for the organization, and setting its `default_isolation_segment_guid` data property to the GUID of the new default isolation segment. For example:
   
   <pre class="terminal">
   $ cf curl "/v2/organizations/45a66ed9-cb76-46c3-92dd-b29187b50bfb" \
  
positive.code: my_segment     org1, org2
  </pre>
  
  ### <a id="list_orgs"></a> List Orgs for an Isolation Segment
  
  The following example request returns a list of orgs in the isolation segment with the given GUID. The request only returns orgs that you can access:
  
  <pre class="terminal">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations"
  </pre>
  
  The request returns a list of orgs in the following format:
  <pre class="terminal">
  HTTP/1.1 200 OK<br>
  {
    "data": [
      {
        "name": "my\_org",
        "guid": "45a66ed9-cb76-46c3-92dd-b29187b50bfb",
        "link": "/v2/organizations/45a66ed9-cb76-46c3-92dd-b29187b50bfb"
      },
      {
        "name": "my\_other\_org",
        "guid": "d0540a63-3bec-42ff-abd9-8a30328ba296",
        "link": "/v2/organizations/d0540a63-3bec-42ff-abd9-8a30328ba296"
      }
    ]
  }
  </pre>
  
  ### <a id="list_spaces"></a> List Spaces for an Isolation Segment
  
  The following example request returns a list of spaces in the isolation segment with the given GUID. The request only returns spaces that you can access:
  <pre class="terminal">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces" 
  </pre>
  
  The request returns a list of spaces in the following format:
  <pre class="terminal">
  HTTP/1.1 200 OK<br>
  {
    "data": [
      {
        "name": "my\_space",
        "guid": "68d54d31-9b3a-463b-ba94-e8e4c32edbac",
        "link": "/v2/spaces/68d54d31-9b3a-463b-ba94-e8e4c32edbac"
      },
      {
        "name": "my\_other\_space",
        "guid": "b19f6525-cbd3-4155-b156-dc0c2a431b4c",
        "link": "/v2/spaces/b19f6525-cbd3-4155-b156-dc0c2a431b4c"
      }
    ]
  }
  </pre>
  
  ## <a id="get_is"></a> Retrieve an Isolation Segment
  
  To retrieve an isolation segment by its GUID, send a `cf curl` command like the following to the `isolation_segments/GUID` endpoint of your CAPI:
  <pre class="terminal">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913" 
  </pre>
  
  This example request returns the [contents](#contents) of the isolation segment:
  <pre class="terminal">
  HTTP/1.1 200 OK<br>
  {
     "guid": "323f211e-fea3-4161-9bd1-615392327913",
     "name": "my\_segment",
     "created\_at": "2016-10-19T20:25:04Z",
     "updated\_at": "2016-11-08T16:41:26Z",
     "links": {
        "self": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913"
        },
        "spaces": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces"
        },
        "organizations": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations"
        }
     }
  }
  </pre>
  
  ## <a id="manage_is"></a> Manage an Isolation Segment
  
  The `cf curl` requests and `cf CLI` commands listed in the sections below make changes to isolation segment objects in the CCDB. Only admins can make these changes.
  
  ### <a id="update_is"></a> Update an Isolation Segment
  
  The following example renames the isolation segment with the given GUID to `my_isolation_segment`:
  <pre class="terminal">
  $ cf curl "/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913" \
    -X PATCH \
    -d '{
      "name": "my\_isolation\_segment"
    }'
  </pre>
  
  The request returns the following output:
  <pre class="terminal">
  HTTP/1.1 200 OK<br>
  {
     "guid": "323f211e-fea3-4161-9bd1-615392327913",
     "name": "my\_isolation\_segment",
     "created\_at": "2016-10-19T20:25:04Z",
     "updated\_at": "2016-11-08T16:41:26Z",
     "links": {
        "self": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913"
        },
        "spaces": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces"
        },
        "organizations": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations"
        }
     }
  }
  </pre>
  
  ### <a id="delete_is"></a> Delete an Isolation Segment
  
  The following command deletes an isolation segment:
  <pre class="terminal">
  $ cf delete-isolation-segment
  
negative.code: 
  The command fails if another isolation segment with the same name exists.
  
  ## <a id="lists"></a> Retrieve Isolation Segment Information
  
  The `cf isolation-segments`, `cf org` and `cf space` commands retrieve information for the isolation segments that you have access to. The isolation segments you can see information for depends on your role, as follows:
  
  * **Admins** see all isolation segments in the system.
  * **Other users** see the isolation segments that their orgs have been added to.
  