anchor.diff:          ```
   
           Where:
  -        * `YOUR-APP` is the name of the <%= vars.product_name %> app for which you want to use the volume service.
  +        * `YOUR-APP` is the name of the 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. If you omit `username` and `password`, the driver skips `mapfs` mounting and performs just the normal kernel mount of the NFS file system without the overhead associated with FUSE mounts.
           * (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`.
  
positive.code: 
  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.
  
  
negative.code:     * `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 <%= vars.app_runtime %> 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) `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:
  
  