anchor.diff:      instance_type: c3.large
       iam_instance_profile: cloud-controller
            </pre></code>
  -       4. Assign all Cloud Controller jobs (api_z\*) and Cloud Controller Worker jobs (api_worker_z\*) to the `cloud-controller-resource-pool`
  +       4. Assign all Cloud Controller jobs (<code>api_z\*</code>) and Cloud Controller Worker jobs (<code>api_worker_z\*</code>) to the <code>cloud-controller-resource-pool</code>.
       </td>
     </tr>
   
  
positive.code:     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>
    </tr>
    <tr>
  
negative.code: }]
  }
            </pre></code>
         3. In your Cloud Foundry deployment manifest, configure a resource pool to use the <code>cloud-controller</code> IAM role:
           <pre><code>
  resource_pools:
  - name: cloud-controller-resource-pool
  