anchor.diff:        <ul>
           <li><a href="#create">Create and Bind a Service Instance</a></li>
           <li><a href="#app">Access the Volume Service from your App</a></li>
  -        <li><a href="#manifest">Bind with an App Manifest</a></li>
  -        <li><a href="#mount-path">Mount Path Limitation</a></li>
  +        <li><a href="#mount-path">Mount a Shared Volume in the /app Directory</a></li>
         </ul>
  -      <li><a href="#nfs">NFS Volume Service</a></li>
  +      <li><a href="#nfs">Create and Use NFS Volume Services</a></li>
           <ul>
             <li><a href="#create-nfs">Create an NFS Volume Service</a></li>
             <li><a href="#nfs-sample">Deploy and Bind Sample App</a></li>
  
positive.code:   <pre class="terminal">cf push YOUR-APP -c "ln -s /var/volume1 /app/volume1 && \$HOME/boot.sh"</pre>
  
  
  ## <a id='nfs'></a> NFS Volume Service
  
  This section describes how to use the NFS volume service.
  
  
negative.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 `nfs-volume` v1.3.1 and later and `smb-volume` v1.0.0 and later. For more information, see [Services](../deploy-apps/manifest.html#services-block) in _Deploying with App Manifests_.</p> 
  
  To create and bind an instance for the volume service:
  
  