anchor.diff:    * 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): This volume service is implemented with libfuse. It does not support
  -`version` parameters and only mounts NFSv3. The service also has some performance constraints.
  +* `nfs-legacy` (deprecated): This volume service exists for historical reasons only as it is difficult to retire services at the moment.  If you use this service it will perform exactly the same mount as the `nfs` service.
   
   Both services offer a single plan called `Existing`.
   
  
positive.code: <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  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:
  
  
negative.code:         "provider": null,
          "syslog\_drain\_url": null,
          "tags": [
            "nfs"
          ],
          "volume\_mounts": [
            {
  