anchor.diff:          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.
  -        * `UID` and `GID` are the `uid` and `gid` to use when mounting the share to the app. The `gid` and `uid` must be positive integer values. Provide the `uid` and `gid` as a JSON string in-line or in a file.
  +        * `UID` and `GID` are the `uid` and `gid` to use when mounting the share to the app. The `gid` and `uid` must be positive integer values. Provide the `uid` and `gid` as a JSON string in-line or in a file. If you omit `uid` and `gid`, the driver skips `mapfs` mounting and performs just the normal kernel mount of the NFS file system without the overhead associated with FUSE mounts.
           <p class="note"><strong>Note:</strong> For security reasons, nfs-volume v2.0.0 and later does not support `uid` and `gid` values of `0`.</p>
  -        * **(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`.
  +        * (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.
  +        * (Optional) `"readonly":true` is an optional JSON string that creates a read-only mount. By default, Volume Services mounts a read-write file system. For read-only mounts, the driver enables attribute caching. This results in fewer attribute RPCs and better performance.
   
           The following example shows binding `my-app` to the `nfs_service_instance` and specifying a read-only volume to be mounted to `/var/volume1`, passing an in-line JSON string:
  -        <pre class="terminal">$ cf bind-service my-app nfs\_service\_instance -c '{"uid":"1000","gid":"1000","mount":"/var/volume1","readonly":true}'</pre>
  +        <pre class="terminal">cf bind-service my-app nfs\_service\_instance -c '{"uid":"1000","gid":"1000","mount":"/var/volume1","readonly":true}'</pre>
       * **LDAP-only**: Bind an LDAP service to an app. Run:
   
           ```
  
positive.code: 
  To use a volume service deployed by your <%= vars.admin %>, you must first create an instance of the specific volume service that you need.
  
  <p class="note">You can also bind volume services using an app manifest. However, app manifests do not support bind configuration. If you want to bind a volume service using an app manifest, you must specify bind configuration when you create the service instance. The releases that support this are <code>nfs-volume</code> v1.3.1 and later and <code>smb-volume</code> v1.0.0 and later. For more information, see <a href="../deploy-apps/manifest.html#services-block">Services</a> in <em>Deploying with App Manifests</em>.</p> 
  
  To create and bind an instance for the volume service:
  
  
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
  