anchor.diff:  
   Revoke the organization’s entitlement for an isolation segment:
   <pre class="terminal">
  -	$ cf disable-org-segment org_name segment_name
  +	$ cf disable-org-segment org\_name segment_name
   </pre>
   
  -NOTE: When spaces with an isolation segment assignment contain apps, this relationship cannot be changed.
  +<p class="note"><strong>Note</strong>: When spaces with an isolation segment assignment contain apps, this relationship cannot be changed.</p>
   
   Set the org isolation segment default:
   <pre class="terminal">
  
positive.code: 	$ cf unset-space-isolation-segment operations
  </pre>
  
  NOTE: When a space contains apps, this relationship cannot be changed.
  
negative.code: 
  ## <a id="org-entitle"></a> Entitle an Org for an Isolation Segment
  
  Entitle an org for an isolation segment. This step requires CF admin permissions.
  <pre class="terminal">
  	$ cf enable-org-isolation-segment org\_name segment_name
  </pre>
  
  ## <a id="space-set"></a> Set the Isolation Segment for a Space
  
  Create a space where apps will be deployed:
  <pre class="terminal">
  	$ cf create-space space_name
  </pre>
  
  Assign the segment to an existing space. This requires org manager permissions.
  <pre class="terminal">
  	$ cf set-space-isolation-segment space\_name segment_name
  </pre>
  
  ## <a id="push-app"></a> Push an App to a Segment
  
  After a space is assigned to a segment, a developer can push to the isolation segment using `cf push`.
  ## <a id="org-management"></a> Org Isolation Segment Management
  
  View isolation segments enabled for an org:
  