anchor.diff:  
   Your CF deployment now has a running service broker and volume drivers and is ready to mount NFS volumes.
   
  -####<a id="server"></a>Deploying the NFS Test Server
  +####<a id="nfs-server"></a>Deploying the NFS Test Server
   
   To deploy the NFS test server, you can fetch the operations file from the [persi-ci github repository](https://github.com/cloudfoundry/nfs-volume-release/blob/master/operations/enable-nfs-test-server.yml) and include that operation with a `-o` flag. This creates a separate VM with nfs exports you can use to experiment with volume mounts.
   
  -<p class="note"><strong>Note</strong>: By default, the nfs test server expects that your CF deployment is deployed to a 10.x.x.x subnet.  If you are deploying to a subnet that is not 10.x.x.x (e.g. 192.168.x.x) then you will need to override the "export_cidr" property.<br/>
  +<p class="note"><strong>Note</strong>: By default, the nfs test server expects that your CF deployment is deployed to a 10.x.x.x subnet.  If you are deploying to a subnet that is not 10.x.x.x (e.g. 192.168.x.x) then you will need to override the `export_cidr` property.<br/>
    Edit the operations file, and replace this line:<br/>
    <span style="font-family:monospace">  nfstestserver: {}</span><br/>
    with something like this:<br/>
   	<span style="font-family:monospace">  nfstestserver: {export_cidr: 192.168.0.0/16}</span>
   </p>
   
  -###<a id="broker"></a>Grant Access to the NFS Broker
  +###<a id="nfs-broker"></a>Grant Access to the NFS Broker
   
   Grant access to the services of the broker.
  -  
  +
   <pre class="terminal">
   $ cf enable-service-access nfs
   $ cf enable-service-access nfs-experimental
  
positive.code: 
  CF Developers can now create an NFS service and bind instances to their apps as outlined in the [Using an External File System (Volume Services)](../devguide/services/using-vol-services.html) topic.
  
  ###<a id="ldap"></a>(Optional) LDAP Support
  
    For better security, it is recommended to configure your deployment of nfs-volume-release to connect to an external LDAP server to resolve user credentials into uids.  See [this note](https://github.com/cloudfoundry/nfs-volume-release/USING_LDAP.md) for more details.
  
negative.code: 
  If you have any questions, you can contact the team that develops volume services for CF on the **#persi** channel in the [Cloud Foundry (Open Source)](https://cloudfoundry.slack.com) Slack organization.
  
  ##<a id="nfs-example"></a> Example 1: Deploy NFS Volume Service to CF
  
  The following procedure provides an example of how to deploy the NFS broker and corresponding driver to an existing CF deployment.
  
  ###<a id="nfs-pre"></a>Prerequisites
  
  This procedure requires the following:
  
  * A current version of Cloud Foundry deployed [as described here](/deploying/index.html).
  * A BOSH v2 CLI.
  * An NFS Server. If you require it, a test server can be deployed following the instructions [below](#nfs-server).
  
  ###<a id="nfs-redeploy"></a>Redeploy CF with NFS Enabled
  
  1. Clone the cf-deployment repository from git, if you do not already have it:
    <pre class="terminal">
  