anchor.diff:  
   ## <a id="relationships"></a> Manage Isolation Segment Relationships
   
  -These requests add and remove orgs and spaces from isolation segments. Only admins can perform these operations.
  +The `curl` requests listed in the sections below add and remove orgs and spaces from isolation segments. Only admins can perform these operations.
   
   ### <a id="add_is"></a> Add Orgs or Spaces to an Isolation Segment
   
   When you add an org or space to one isolation segment, it becomes the default isolation segment for that org or space unless another default is already set. In the data field of the `curl` command, specify one or more orgs by GUID to add to the isolation segment.
   
  -The following example adds one or more orgs to an isolation segment. To add spaces, send the same command to the `/relationships/spaces` endpoint:
  +The following example adds two orgs to an isolation segment:
   <pre class="terminal">
   curl "https\://api.example.org/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations" \
     -X POST \
  
positive.code: * Timestamps for the object's creation and most recent update
  * Links to API endpoints for isolation segment requests
  
  In the CCDB, an isolation segment object does not identify the orgs and spaces that it includes. The org and space objects define this relationship, by including the GUIDs of the isolation segments that they belong to.
  
  
  ## <a id="create_is"></a> Create an Isolation Segment
  
  An admin creates an isolation segment by sending a `curl` command to the CAPI with a name to identify it. Isolation segment names must be unique across the entire system and not case-sensitive. Only admins can create isolation segments.
  
  The following example uses a CAPI endpoint and authorization token to create an isolation segment named `my_segment`:
  <pre class="terminal">
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes how Cloud Foundry 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, the CCDB outputs a GUID for the new isolation segment object.
  
  To manage the isolation segment, an operator sends `curl` requests to the Cloud 
  Controller API (CAPI) endpoint with the GUID of the isolation segment and an 
  authorization token. <%= vars.api_endpoint_book %>
  
  Operators can perform the following operations on isolation segments:
  
  * [Create](#create_is) a new isolation segment
  * [Retrieve](#get_is) an isolation segment object
  * [List](#list_is) isolation segments
  * [List orgs](#list_orgs) or [spaces](#list_spaces) in an isolation segment
  * [Update](#update_is) an isolation segment
  * [Delete](#delete_is) an isolation segment
  * [Add orgs or spaces](#add_is) to isolation segments
  * [Remove orgs or spaces](#revoke_is) from isolation segments
  
  ## <a id="contents"></a> Isolation Segment Contents
  
  