anchor.diff:  
   ## <a id="org-entitle"></a> Entitle an Org for an Isolation Segment
   
  -Entitle an org for an isolation segment (cf admin only)
  -<pre class="terminal">	
  -	$ cf enable-org-isolation-segment org_name segment_name
  +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
  +## <a id="space-set"></a> Set the Isolation Segment for a Space
   
  -Assign segment to an existing space (org manager only)
  +Create a space where apps will be deployed:
   <pre class="terminal">
  -	$ cf set-space-isolation-segment space_name segment_name
  +	$ cf create-space space_name
   </pre>
   
  -NOTE: Use `cf create-space space_name` to create a new space.
  +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 Space Developer can push to the isolation segment using `cf push`.
  -NOTE: There is no difference in the user experience for space developers.
  -
  +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:
  
positive.code: 	$ cf unset-space-isolation-segment operations
  </pre>
  
  NOTE: When a space contains apps, this relationship cannot be changed.
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes how CF operators can isolate app deployments to dedicated pools of resources.
  
  ## <a id="associate_cells"></a> Associate Cells with an Isolation Segment
  
  In the BOSH deployment manifest, add the `placement_tags` attribute to each Diego cell to be included in a given isolation segment. Add the name of the segment as one of the values.
  
  For example, in `releases/diego.yml`:
  <pre class="terminal">
  	- instances: 1
  	  name: cell\_z2
  	  networks:
  	  - name: diego2
    	properties:
    	  diego:
    	    rep:
    	      [...]
    	      placement\_tags:
    	      - segment_name
  </pre>
  
  Apply the changes by deploying BOSH. This step requires BOSH deployment permissions:
  <pre class="terminal">
  	$ bosh deploy
  </pre>
  
  ## <a id="segment-create"></a> Create an Isolation Segment with the cf CLI
  
  Create an isolation segment using a name that matches the placement tag. See [Associate Cells with an Isolation Segment](#associate_cells) above. This step requires CF admin permissions.
  <pre class="terminal">
  	$ cf create-isolation-segment segment_name
  </pre>
   
  List isolation segments:
  <pre class="terminal">
  	$ cf isolation-segments
  	name           orgs
  