anchor.diff:  
   ## <a id="get_is"></a> Retrieve an Isolation Segment
   
  -To retrieve an IS by its GUID, send a `curl` command like the following to the `isolation_segments/GUID` endpoint of your CAPI:
  +To retrieve an isolation segment by its GUID, send a `curl` command like the following to the `isolation_segments/GUID` endpoint of your CAPI:
   <pre class="terminal">
   curl "https\://api.example.org/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913" \
     -X GET \
     -H "Authorization: bearer 7h15154l0n64lph4num3r1c57r1n6"
   </pre>
   
  -This example request returns the [contents](#contents) of the IS:
  +This example request returns the [contents](#contents) of the isolation segment:
   <pre class="terminal">
   HTTP/1.1 200 OK<br>
   {
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes how CF operators can isolate deployment workloads to dedicated resource pools called _isolation segments_.
  
  The Cloud Controller database (CCDB) represents isolation segments with a name and a GUID. When an admin creates a new isolation segment (IS), the CCDB outputs a GUID for the new IS object.
  
  To manage the IS, a user can send `curl` requests to the Cloud Controller API (CAPI) endpoint with the GUID of the isolation segment and an authorization token. <%= vars.api_endpoint_book %>
  
  Basic operations on isolation segments include:
  
  
negative.code: 
  ### <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">
  curl "https\://api.example.org/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations" \
    -X GET \
  