anchor.diff:      Where:
       * `SERVICE-INSTANCE-NAME`: The name of the volume service instance you created previously.
       * `UID` and `GID`: The `gid` and `uid` to use when mounting the share to the app. The nfs driver uses these values in the following ways:
  -      * When sending traffic to the nfs server, the nfs driver translates the app user id and group id to the `UID` and `GID` values. 
  -      * When returning attributes from the nfs server, the nfs driver translates the `UID` and `GID` back to the running user uid and default gid. 
  -      
  +      * When sending traffic to the nfs server, the nfs driver translates the app user id and group id to the `UID` and `GID` values.
  +      * When returning attributes from the nfs server, the nfs driver translates the `UID` and `GID` back to the running user uid and default gid.
  +
           This allows you to interact with your nfs server as a specific user while allowing Cloud Foundry to run your application as an arbitrary user.
       * **Optional paramenters**:
  -      * `mount`: Use this option to specify the path at which volumes mount to the app container. The default is an arbitrarily-named folder in `/var/vcap/data`. You may need to modify this value if your app has specific requirements. For example: 
  -
  -            ``` 
  +      * `mount`: Use this option to specify the path at which volumes mount to the app container. The default is an arbitrarily-named folder in `/var/vcap/data`. You may need to modify this value if your app has specific requirements. For example:
  +
  +            ```
               cf bind-service pora myVolume -c '{"uid":"0","gid":"0","mount":"/var/path"}'
               ```
         * `readonly`: When you issue the `cf bind-service` command, Volume Services mounts a read-write file system by default. You can specify a read-only mount by adding `"readonly":true` to the bind configuration JSON string.
   
   1. Start the app:
  -    
  +
       ```
       $ cf start pora
       ```
   
   1. Use the following curl command to confirm the app is running. The command returns an instance index for your app.
  -    
  +
       ```
       $ curl http://pora.YOUR-CF-DOMAIN.com
       ```
  
positive.code: 
  ## <a id='nfs'></a> NFS Volume Service
  
  This section describes how to use the NFS volume service. 
  
  ### <a id='create-nfs'></a> Create an NFS Volume Service
  
  Cloud Foundry offers two plans for the NFS volume service: 
  
  * `Existing`: This volume service is implemented with libfuse. It only supports NFSv3 and has some performance constraints.
  * `nfs-experimental`: This volume service provides better performance:
    * It supports NFSv4 through a `version` parameter that determines which NFS protocol to use.
    * It is using the read-only mounts causing the driver to enable attribute caching for mounts. This results in fewer attribute RPCs and better performance.
    * Omitting 'uid' and 'gid' (or 'username' and 'password') in bind configuration causes the nfsdriver to skip mapfs mounting, resulting in a normal kernel mount of the nfs file system without the overhead associated with FUSE mounts.
  
  To create an NFS volume service, follow the procedure below that corresponds to your use case. 
  
  #### Create with Existing Plan
  
  You can create a NFS volume service with NFSv3 using the `Existing` service plan. Run the following command:
  
  ```
  $ cf create-service nfs Existing SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE"}'   
  ```
  
  Where: 
  
  * `SERVICE-INSTANCE-NAME` is a name you provide for this NFS volume service instance. 
  * `SERVER/SHARE` is the NFS address of your server and share. 
  
  <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  You can run the `cf services` command to confirm that your newly created NFS volume service displays in the output. 
  
  
  #### Create with Experimental Plan:
  
  You can create a NFS volume service with NFSv3 or NFSv4 using the `nfs-experimental` service plan. Run the following command:
  
  ```
  $ cf create-service nfs nfs-experimental SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "version":"NFS-PROTOCOL"}'   
  ```
  
  Where: 
  
  * `SERVICE-INSTANCE-NAME` is a name you provide for this NFS volume service instance. 
  * `SERVER/SHARE` is the NFS address of your server and share. 
  * `VERSION` is the NFS protocol you want to use. For example, if you want to use NFSv4, set the version to `4.1`. 
  
  <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  You can run the `cf services` command to confirm that your newly created NFS volume service displays in the output. 
  
  ### <a id='nfs-sample'></a> Deploy and Bind a Sample App
  
  This section includes a procedure for deploying a sample app and binding it to the NFS volume service. 
  
  1. Clone the github repo and push the pora test app:
    1. `cd ~/workspace`
  
negative.code: 
      ```
      $ curl http://pora.YOUR-CF-DOMAIN.com/write
      ```
  
  ### <a id="nfs-additional"></a> Additional Information
  
  This section provides additional information about using the NFS Volume Service.
  
  #### Binding with LDAP Credentials
  
  