anchor.diff:  
   1. Specify a mount volume in a location outside of the `/app` directory.
   
  -1. Create a symbolic link at app startup time, prior to launching the app. For example:
  -  <pre class="terminal">cf push YOUR-APP -c "ln -s /var/volume1 /app/volume1 && \$HOME/boot.sh"</pre>
  +1. Create a symbolic link at app startup time, prior to launching the app. For example, run:
  +
  +    ```
  +    cf push YOUR-APP -c "ln -s /var/volume1 /app/volume1 && \$HOME/boot.sh"
  +    ```
  +    Where `YOUR-APP` is the name of the app.
   
   
   ## <a id='nfs'></a> Create and Use NFS Volume Services
   
   This section describes how to use the NFS volume service.
   
  +<%= vars.product_name %> offers two NFS volume services:
  +
  +* `nfs`: This volume service provides support for NFS volumes using both v3 and v4.x protocols.
  +
  +* `nfs-legacy` (deprecated): Although it is deprecated, this volume service is still available due to the difficulty of retiring services. If you use this service, it performs exactly the same mount as the `nfs` service. For information about migrating to `nfs`, see [Migrate `nfs-legacy` Services to `nfs`](#migrate).
  +
  +Both services offer a single plan called `Existing`.
  +
   ### <a id='create-nfs'></a> Create an NFS Volume Service
   
  -Cloud Foundry offers two NFS volume services:
  -
  -* `nfs`: This volume service provides support for NFS volumes using both v3 and v4.x protocols.
  -  * If you do not specify a `version` parameter in the create configuration, the protocol version used is negotiated between client and server at mount time. This usually results in the latest available version being used.
  -  * If you want to request a specific protocol version, include a `version` parameter in the create configuration.
  -  * For read-only mounts, the driver enables attribute caching. This results in fewer attribute RPCs and better performance.
  -  * When you omit `uid` and `gid` or `username` and `password` in bind configuration, the driver skips `mapfs` mounting and performs just the normal kernel mount of the NFS file system without the overhead associated with FUSE mounts.
  -
  -* `nfs-legacy` (deprecated): Although it is deprecated, this volume service is still available due to the difficulty of retiring services. If you use this service, it performs exactly the same mount as the `nfs` service.
  -
  -Both services offer a single plan called `Existing`.
  -
  -To create an NFS volume service, follow the procedure below that corresponds to your use case.
  -
  -#### Create an `nfs` Service (Auto-Negotiated Version)
  -
  -You can create a NFS volume service using the `Existing` plan of the `nfs` service. 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 an `nfs` Service (Explicit Version)
  -
  -You can create a NFS volume service with a specific NFS protocol version using the `Existing` plan of the `nfs` service. Run the following command:
  -
  -```
  -$ cf create-service nfs Existing 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`. Valid values are `3.0`, `4.0`, `4.1` or `4.2`.
  -
  -<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.
  -
  -#### Existing `nfs-legacy` Services:
  -
  -With the release of NFS Volume Service v1.5.4, the original fuse-based NFS service has been deprecated in favor of the newer kernel mount-based NFS service. Existing NFS volume service bindings will now be listed as `nfs-legacy`. To switch over from `nfs-legacy` to the newer `nfs` service, Pivotal recommends you re-create and re-bind your `nfs` service instances.
  -
  -With the release of NFS Volume Service v2.0.0, the `nfs-legacy` service has been rewritten to use the `nfs` service. To avoid being affected when the `nfs-legacy` service is retired, re-create and re-bind your service instances using the `nfs` service.
  +To create an NFS volume service using the `Existing` plan of the `nfs` service: 
  +
  +
  +1. Create an NFS volume service. Run:
  +
  +    ```
  +    cf create-service nfs Existing 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.
  +    <p class="note"><strong>Note:</strong> Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  +    * (Optional) `NFS-PROTOCOL` is the NFS protocol you want to use. For example, if you want to use NFSv4, set the version to `4.1`. Valid values are `3.0`, `4.0`, `4.1` or `4.2`. If you do not specify a `version`, the protocol version used is negotiated between client and server at mount time. This usually results in the latest available version being used.
  +
  +1. Confirm that the NFS volume service appears in your list of services. Run: 
  +
  +    ```
  +    cf services
  +    ```
  +
  +### <a id='migrate'></a> Migrate `nfs-legacy` Services to `nfs`
  +
  +With the release of NFS Volume Service v1.5.4, the original fuse-based NFS service is deprecated in favor of the newer kernel mount-based NFS service. Existing NFS volume service bindings are listed as `nfs-legacy`. 
  +
  +To migrate from `nfs-legacy` to the newer `nfs` service, Pivotal recommends you re-create and re-bind your `nfs` service instances.
  +
  +With the release of NFS Volume Service v2.0.0, the `nfs-legacy` service uses the `nfs` service. To avoid being affected when the `nfs-legacy` service is retired, re-create and re-bind your service instances using the `nfs` service.
   
   ### <a id='nfs-sample'></a> Deploy and Bind a Sample App
   
   This section describes how to deploy a sample app and bind it to the NFS volume service.
   
  -1. Clone the GitHub repository and push the `pora` test app:
  +To deploy and bind a sample app:
  +
  +1. Clone the GitHub repository for the sample app into your workspace. Run:
  +
     1. `cd ~/workspace`
     1. `git clone https://github.com/cloudfoundry/persi-acceptance-tests.git`
  +
  +1. Push the `pora` test app. Run:
  +
     1. `cd ~/workspace/persi-acceptance-tests/assets/pora`
     1. `cf push pora --no-start`
   
  -1. Bind the service to your app:
  -
  -    ```
  -    $ cf bind-service pora SERVICE-INSTANCE-NAME -c '{"uid":"UID","gid":"GID"}'
  +1. Bind the service to your app. Run:
  +
  +    ```
  +    cf bind-service pora SERVICE-INSTANCE-NAME -c '{"uid":"UID","gid":"GID"}'
       ```
       Where:
       * `SERVICE-INSTANCE-NAME`: The name of the volume service instance you created previously.
       * `UID` and `GID`: The `UID` and `GID` 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. This allows you to interact with your NFS server as a specific user while allowing Cloud Foundry to run your app as an arbitrary user. `UID` and `GID` must be positive integer 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 <%= vars.product_name %> to run your app as an arbitrary user. `UID` and `GID` must be positive integer values.
   <p class="note"><strong>Note:</strong> In NFS v2.0.0 and later, `UID` and `GID` values of 0 are no longer permissible due to security reasons.</p>
  -    * **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:
  -
  -            ```
  -            cf bind-service pora myVolume -c '{"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
  -    ```
  -
  -1. Use the following `curl` command to confirm the app can access the shared volume. The command writes a file to the share and then reads it back out again.
  -
  -    ```
  -    $ 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.
  +    * (Optional) `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 '{"mount":"/var/path"}'
  +          ```
  +    * (Optional) `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. Run:
  +
  +    ```
  +    cf start pora
  +    ```
  +
  +1. Confirm the app is running. Run:
  +
  +    ```
  +    curl http://pora.YOUR-CF-DOMAIN.com
  +    ```
  +
  +    The command returns an instance index for your app.
  +
  +1. Confirm the app can access the shared volume. Run:
  +
  +    ```
  +    curl http://pora.YOUR-CF-DOMAIN.com/write
  +    ```
  +
  +    The command writes a file to the share and then reads it back out again.
  +
  +### <a id="nfs-additional"></a> Use NFS Volume Services
  +
  +This section describes using the NFS Volume Service.
   
   #### <a id='ldap'></a> Configure LDAP Credentials with Service Instance Creation
   
  -If your Cloud Foundry deployment has LDAP enabled, you can configure LDAP credentials for your NFS Volume Service instance.
  +If your <%= vars.product_name %> deployment has LDAP enabled, you can configure LDAP credentials for your NFS Volume Service instance.
   
   To configure LDAP credentials while creating your NFS Volume Service instance:
   
   1. Specify values for `username` and `password` in the JSON string for your `cf create-service` command:
  -    ```
  -    $ cf create-service nfs PLAN SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "username":"USERNAME", "password":"PASSWORD"}'
  +
  +    ```
  +    cf create-service nfs PLAN SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "username":"USERNAME", "password":"PASSWORD"}'
       ```
       Where:
       * `PLAN` is the name of the service plan.
  
positive.code:         Where:
          * `YOUR-APP` is the name of the <%= vars.product_name %> app for which you want to use the volume service.
          * `SERVICE-NAME` is the name of the volume service instance you created in the previous step.
          * `USERNAME` and `PASSWORD` are the username and password for the LDAP server.
          * **(Optional)** `OPTIONAL-MOUNT-PATH` is a JSON string that indicates the volume should be mounted to a particular path within your app rather than the default path. Choose a path with a root-level folder that already exists in the container, such as `/home`, `/usr`, or `/var`.
            <p class="note"><strong>Note</strong>: Do not specify a `MOUNT-PATH` within the `/app` directory, which is where <%= vars.product_short %> unpacks the droplet. For more information, see <a href="#mount-path">Mount a Shared Volume in the /app Directory</a>.</p>
          * **(Optional)** `"readonly":true` is an optional JSON string that creates a read-only mount. By default, Volume Services mounts a read-write file system.
  
  1. Restage your app. Run:
  
  
negative.code:     }
      </pre>
  
  2. Use the properties under `volume_mounts` for any information your app needs. See the following table:
    <table>
      <tr>
        <th width="30%">
  