anchor.diff:    * `SERVICE`: The name of the volume service that you want to use.
     * `PLAN`: The name of the service plan. Service plans are a way for providers to offer varying levels of resources or features for the same service.
     * `SERVICE-INSTANCE`:  A name you provide for your service instance. Use any series of alpha-numeric characters, hyphens, and underscores. You can rename the instance at any time.
  -  * `SHARE-JSON` (NFS Only): If you create an instance of the NFS volume service, you must supply an extra parameter, `share`, by using the `-c` flag with a JSON string, in-line or in a file. This parameter forwards information to the broker about the NFS server and share required for the service. 
  -  
  -    The following example shows creating an instance of the "Existing" NFS 
  -    service plan, passing an in-line JSON string: 
  +  * `SHARE-JSON` (NFS Only): If you create an instance of the NFS volume service, you must supply an extra parameter, `share`, by using the `-c` flag with a JSON string, in-line or in a file. This parameter forwards information to the broker about the NFS server and share required for the service.
  +
  +    The following example shows creating an instance of the "Existing" NFS
  +    service plan, passing an in-line JSON string:
       <pre class="terminal">$ cf create-service nfs Existing nfs\_service\_instance -c '{"share": "10.10.10.10/export/myshare"}'</pre>
   
   1. Run `cf bind-service YOUR-APP SERVICE-NAME -c GID-AND-UID-JSON MOUNT-PATH READ-ONLY-TRUE` to bind your service instance to an app. Replace the following with the specified values:
  -  * `YOUR-APP`: The name of the <%= vars.product_name %> app for which you want to use the volume service. 
  +  * `YOUR-APP`: The name of the <%= vars.product_name %> app for which you want to use the volume service.
     * `SERVICE-NAME`: The name of the volume service instance you created in the previous step.
     * `GID-AND-UID-JSON` (NFS only): If you bind an instance of the NFS volume service, you must supply two extra parameters, `gid` and `uid`. You can specify these parameters with the `-c` flag and a JSON string, in-line or from a file. This parameter specifies the `gid` and `uid` to use when mounting the share to the app.
     * `MOUNT-PATH` (Optional): To mount the volume to a particular path within your app rather than the default path, you supply the `mount` parameter. Choose a path with a root-level folder that already exists in the container, such as `/home`, `/usr`, or `/var`.
  -  * `READ-ONLY-TRUE` (Optional): 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. 
  +  * `READ-ONLY-TRUE` (Optional): 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.
   
       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:
  
positive.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
  
  
negative.code: 
  #### File Locking with `flock()` and `lockf()`/`fcntl()`
  
  For apps that use file locking through unix system calls such as `flock()` and `fcntl()` or script commands such as `flock`, NFS volume service does not enforce the locking across Diego cells. This is because the file locking capability of the underlying `fuse-nfs` executable is not implemented. Locking is therefore limited to local locks between precesses on the same VM.
  
  If you have a requirement for file locking, describe your use case in the following Github issue for consideration by the Diego Persistence team: [lock not propagated between instances](https://github.com/cloudfoundry-incubator/nfs-volume-release/issues/13).
  