anchor.diff:  
   ### <a id="list_spaces"></a> List Spaces for an Isolation Segment
   
  -The following example request returns a list of spaces in the IS with the given GUID. The request only returns spaces that you can access::
  +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">
   curl "https\://api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces" \
     -X GET \
  
positive.code: 
  ## <a id="lists"></a> List Isolation Segment Information
  
  These `curl` requests retrieve information for the isolation segments that you have access to, filtered by [parameters](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#list-isolation-segments) that you can include. What isolation segments you see information for depends on your role, as follows:
  
  * **Admins** see all isolation segments in the system.
  * **Org managers** see isolation segments containing orgs that they belong to.
  
negative.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">
  