anchor.diff:  1. Configure your WebDAV blobstores by performing the following steps:
         * Replace <code>WEBDAV\_BASIC\_AUTH\_USER</code> and <code>WEBDAV\_BASIC\_AUTH\_PASSWORD</code> with Basic AUTH credentials that Cloud Controller can use to talk your WebDAV installation.
         * Replace <code>WEBDAV\_SECRET</code> with a secret phrase used to sign URLs.
  -      * Replace <code>WEBDAV\_CERT</code>, <code>WEBDAV\_PRIVATE\_KEY</code>, and <code>WEBDAV\_CA\_CERT\_BUNDLE</code> with proper TLS configuration that will be used for the internal blobstore.
  -      * Replace <code>WEBDAV\_PUBLIC\_ENDPOINT</code> with the public URL (e.g. `https://blobstore.SYSTEM-DOMAIN.example.com`) that resolves to your WebDAV installation.
  -      * Replace <code>WEBDAV\_PRIVATE\_ENDPOINT</code> with a URL routable on your internal network. This defaults to `https://blobstore.service.cf.internal:4443` if not set.
  -      * Replace <code>WEBDAV\_BASIC\_AUTH\_USER</code> and <code>WEBDAV\_BASIC\_AUTH\_PASSWORD</code> with Basic AUTH credentials that Cloud Controller can use to talk your WebDAV installation.
  -1. To provide further configuration, create a <code>webnav\_config</code> hash.
  -
  +      * Replace <code>WEBDAV\_CERT</code>, <code>WEBDAV\_PRIVATE\_KEY</code>, and <code>WEBDAV\_CA\_CERT\_BUNDLE</code> with proper TLS configuration that are used for the internal blobstore.
  +      * Replace <code>WEBDAV\_PUBLIC\_ENDPOINT</code> with the public URL that resolves to your WebDAV installation. For example, `https://blobstore.SYSTEM-DOMAIN.example.com`.
  +      * Replace <code>WEBDAV\_PRIVATE\_ENDPOINT</code> with a routable URL on your internal network. If not set, this defaults to `https://blobstore.service.cf.internal:4443`.
  +      * Replace <code>WEBDAV\_BASIC\_AUTH\_USER</code> and <code>WEBDAV\_BASIC\_AUTH\_PASSWORD</code> with Basic AUTH credentials that Cloud Controller can use to communicate with your WebDAV installation.
  +
  +1. Create a <code>webnav\_config</code> hash to provide further configuration.
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes the various options for configuring a blobstore for the Cloud Controller.
  
  Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Fog Ruby gem, but can also use the WebDAV protocol.
  
  This document demonstrates five common blobstore configurations: 
  
  * [Fog with AWS Credentials](#fog-aws-creds)
  * [Fog with AWS Server Side Encryption](#fog-aws-sse)
  
negative.code:         resource_directory_key: YOUR-GCS-RESOURCE-BUCKET
      ```
  
  1. Create an Interoperability key using the GCP  [instructions](https://cloud.google.com/storage/docs/migrating#keys).
  
  1. Replace ` GCS_ACCESS_KEY` and `GCS_SECRET_ACCESS_KEY` with your Cloud Storage credentials.
  
  1. Replace `YOUR-GCS-BUILDPACK-BUCKET`, `YOUR-GCS-DROPLET-BUCKET`, `YOUR-GCS-PACKAGE-BUCKET`, and `YOUR-GCS-RESOURCE-BUCKET` with the names of your Cloud Storage buckets. Do not use periods (`.`) in your bucket names. 
  
  1. You can provide further configuration through the <code>fog_connection</code> hash, which is passed through to the Fog gem.
  
  ##<a id="fog-azure"></a>Fog with Azure Storage
  
  To configure your blobstores to use Azure Storage credentials, perform the steps below.
  
  1. Insert the following configuration into your manifest under `properties.cc`:
  
  