anchor.diff:    </div>
   </div>
   
  -This topic describes how <%= vars.product_name %> app developers can read and write to a mounted file system from their apps. In <%= vars.product_name %>, a volume service provides a volume so your app can read or write to a reliable, persistent file system.
  +This topic describes how app developers can read and write to a mounted file system from their apps.
  +In <%= vars.app_runtime_full %>, a volume service provides a volume so your app can read
  +or write to a reliable, persistent file system.
   
   <p class="note"><strong>Note:</strong> NFS and SMB volume services are available for Linux cells only. These services are not available for Windows cells.</p>
   
  
positive.code:         ```
  
          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.
          * (Optional) `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.
  
negative.code:     * `SERVICE-INSTANCE-NAME`: The name of the volume service instance you created previously.
      * `UID` and `GID`: The `UID` and `GID` to use when mounting the share to the app. The NFS driver uses these values in the following ways:
        * When sending traffic to the NFS server, the NFS driver translates the app user ID and group ID to the `UID` and `GID` values.
        * When returning attributes from the NFS server, the NFS driver translates the `UID` and `GID` back
          to the running user UID and default GID.
          This allows you to interact with your NFS server as a specific user
          while allowing <%= vars.app_runtime %> to run your app as an arbitrary user.
          `UID` and `GID` must be positive integer values.
  <p class="note"><strong>Note:</strong> In NFS v2.0.0 and later, `UID` and `GID` values of 0 are no longer permissible due to security reasons.</p>
      * (Optional) `mount`: Use this option to specify the path at which volumes mount to the app container. The default is an arbitrarily-named folder in `/var/vcap/data`. You may need to modify this value if your app has specific requirements. For example:
  
  