anchor.diff:  
   ### <a id='create-smb'></a> Create an SMB Volume Service
   
  -Cloud Foundry offers one SMB volume service:
  -
  -* `smb`: This volume service provides support for existing SMB shares.
  +<%= vars.product_name %> offers an `smb` volume service. This volume service provides support for existing SMB shares.
   
   The service offers a single plan called `Existing`.
   
  -To create an SMB volume service, follow the procedure below.
  -
  -#### Create with `smb` Service
  -
  -You can create an SMB volume service using the `Existing` plan of the `smb` service. Run the following command:
  -
  -```
  -$ cf create-service smb Existing SERVICE-INSTANCE-NAME -c '{"share":"//SERVER/SHARE"}'
  -```
  -
  -Where:
  -
  -* `SERVICE-INSTANCE-NAME` is a name you provide for this SMB volume service instance.
  -* `//SERVER/SHARE` is the SMB address of your server and share.
  -
  -You can run the `cf services` command to confirm that your newly-created SMB volume service displays in the output.
  +To create an SMB volume service:
  +
  +1. Create the service. Run:
  +
  +    ```
  +    cf create-service smb Existing SERVICE-INSTANCE-NAME -c '{"share":"//SERVER/SHARE"}'
  +    ```
  +
  +    Where:
  +    * `SERVICE-INSTANCE-NAME` is a name you provide for this SMB volume service instance.
  +    * `//SERVER/SHARE` is the SMB address of your server and share.
  +
  +1. Confirm that the SMB volume service appears in your list of services. Run: 
  +
  +    ```
  +    cf services
  +    ```
   
   ### <a id='smb-sample'></a> Deploy and Bind a Sample App
   
   This section describes how to deploy a sample app and bind it to the SMB 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 '{"username":"USERNAME","password":"PASSWORD"}'
  +1. Bind the service to your app. Run:
  +
  +    ```
  +    cf bind-service pora SERVICE-INSTANCE-NAME -c '{"username":"USERNAME","password":"PASSWORD"}'
       ```
       Where:
       * `SERVICE-INSTANCE-NAME`: The name of the volume service instance you created previously.
  -    * `USERNAME` and `PASSWORD`: The username and password to use when mounting the share to the app. This allows you to interact with your SMB server as a specific user while allowing Cloud Foundry to run your app as an arbitrary user.
  -    * **Optional parameters**:
  -      * `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 '{"username":"some-user","password":"some-password","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.
  -      * `domain`: In case if your user is in windows domain you can specify `domain` parameter.
  -
  -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
  -    ```
  +    * `USERNAME` and `PASSWORD`: The username and password to use when mounting the share to the app. This allows you to interact with your SMB server as a specific user while allowing <%= vars.product_name %> to run your app as an arbitrary user.
  +    * (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, run:
  +
  +          ```
  +          cf bind-service pora myVolume -c '{"username":"some-user","password":"some-password","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.
  +    * (Optional) `domain`: If you use a Windows domain, you can specify a `domain` parameter.
  +
  +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.
  
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:     See the following example output of the NFS volume service:
  
      <pre class="terminal">
      cf marketplace
      service   plans      description
      nfs       Existing   Service for connecting to NFS volumes
      </pre>
  
  1. Do one of the following:
      * **If no NFS volume service exists**: If no volume service that fits your requirements exists, contact your <%= vars.admin %>. <%= vars.add_volumes_link %>
      * **If an NFS volume service exists**: Continue to [Mount an External File System](#mount-external-filesystem).
  
  
  ## <a id="mount-external-filesystem"></a> Mount an External Filesystem
  