anchor.diff:  
   You can run the `cf services` command to confirm that your newly-created NFS volume service displays in the output.
   
  -#### Create an NFSv4 volume with `nfs` Service:
  -
  -You can create a NFS volume service with NFSv4.x using the `Existing` plan of the `nfs` service. Run the following command:
  +#### 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"}'
  
positive.code: 
  Cloud Foundry offers two NFS volume services:
  
  * `nfs`: This volume service provides support for both NFSv3 (default) and NFSv4 volumes.
    * For NFSv4,  specify 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.
  
negative.code: * `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>
  
  