anchor.diff:      droplet_directory_key: cc-resources
       webdav_config: \*webdav_config
       </code></pre></td>
  -    <td>
  -      When using "webdav" for a particular blobstore, it can be configured with a <code>webdav_config</code> hash.
  -      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) that resolves to your WebDAV installation.
  -      Replace <code>WEBDAV_PRIVATE_ENDPOINT</code> with a URL routable on your internal network. This will default to "https://blobstore.service.cf.internal" 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.
  +    <td>When using WebDAV for a particular blobstore, it can be configured with a <code>webdav_config</code> hash. Perform the following steps:<br/><br/>
  +      1. 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.<br/><br/>
  +      2. Replace <code>WEBDAV_SECRET</code> with a secret phrase used to sign URLs.<br/><br/>
  +      3. 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.<br/><br/>
  +      4. Replace <code>WEBDAV_PUBLIC_ENDPOINT</code> with the public URL (e.g. `https://blobstore.SYSTEM_DOMAIN`) that resolves to your WebDAV installation.<br/><br/>
  +      5. Replace <code>WEBDAV_PRIVATE_ENDPOINT</code> with a URL routable on your internal network. This will default to `https://blobstore.service.cf.internal` if not set.<br/><br/>
  +      6. 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.
       </td>
     </tr>
     <tr>
  
positive.code:     fog_connection: \*fog_connection
      </code></pre></td>
      <td>
        Fog can be configured to use an `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY`. These credentials should be assigned an IAM policy that allows all S3 actions on each of the buckets in the example.
      </td>
    </tr>
  
  
negative.code:     fog_connection: \*fog_connection
      </code></pre></td>
      <td>
         To configure fog to use <a href="http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2.html">AWS IAM Instance Profiles</a>, perform the following steps:
         <br/><br/>
         1. Complete the steps documented in the <a href="http://bosh.io/docs/aws-iam-instance-profiles.html#director-with-s3-blobstore">AWS CPI and Director configured with an S3 blobstore instructions</a> section of the BOSH documentation.
         <br/><br/>
         2. In the AWS console, configure an additional <code>cloud-controller</code> IAM role that gives access to both the BOSH S3 buckets and the Cloud Controller S3 buckets:
            <pre><code>
  {
  "Version": "2012-10-17",
  