anchor.diff:  
   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
  +### <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.
  +For better security, Pivotal recommends configuring your deployment of nfs-volume-release to connect to an external LDAP server to resolve user credentials into UIDs. For more information, see [this note](https://github.com/cloudfoundry/nfs-volume-release/USING_LDAP.md).
  
positive.code: 
  This topic describes how Cloud Foundry (CF) operators can deploy volume services. 
  
  ##<a id="overview"></a> Overview
  
  A volume service gives apps access to a remote filesystem, such as NFS. To provide a volume service for CF developers to use with their apps, you must deploy a driver and broker pair.
  For current versions of CF that have been been deployed with cf-deployment, deploying brokers and drivers is typically accomplished using operations files as outlined below in [Example: Deploy NFS to CF](#example).
  
  ### Additional Information
  
  For more information about volume services and the drivers and brokers available to CF, see the following links:
  
  * [Volume Services Google Doc](https://docs.google.com/document/d/1YtPMY9EjxlgJPa4SVVwIinfid_fshCF48xRhzyoZhrQ/edit?usp=sharing)
  * [NFS volume release repository](https://github.com/cloudfoundry/nfs-volume-release)
  
negative.code: * [EFS volume release repository](https://github.com/cloudfoundry-incubator/efs-volume-release)
  * [CEPHFS release repository](https://github.com/cloudfoundry-incubator/cephfs-bosh-release)
  
  <p class="note"><strong>Note:</strong> For test purposes, you can deploy the <a href="https://github.com/cloudfoundry/local-volume-release.git">Local Volume Release</a> if running a single Diego Cell CF deployment. This is not intended for production deployments.</p>
  
  ### <a id='contact'></a> Contact
  
  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="example"></a> Example: 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="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 in [Deploying the NFS Test Server](#server).
  
  ### <a id="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">
    $ cd ~/workspace
    $ git clone https<span>:</span>//github.com/cloudfoundry/cf-deployment.git
    $ cd ~/workspace/cf-deployment</pre>
  
  1. Redeploy your cf-deployment while including the NFS ops file:
    <pre class="terminal">
    $ bosh -e my-env -d cf deploy cf.yml -v deployment-vars.yml \
  		-o operations/enable-nfs-volume-service.yml</pre>
  