anchor.diff:        notifications:
           secret: NOTIFICATIONS_CLIENT_SECRET
       </code></pre></td>
  -    <td>Replace all the <code>*_SECRET</code>s with secure secrets.
  -    <br/><br/>
  -    You can use any values for secrets depending on your security needs.
  +    <td>Replace all the <code>*_SECRET</code>s with secure secrets that you generate.
   	  </td>
     </tr>
     <tr>
  
positive.code:       verification_key: JWT_VERIFICATION_KEY
        signing_key: JWT_SIGNING_KEY
      </code></pre></td>
      <td>Replace <code>JWT_SIGNING_KEY</code> with a PEM-encoded RSA private key, and <code>JWT_VERIFICATION_KEY</code> with the corresponding PEM-encoded RSA public key.<br/>
      Paste in the full keys, including the "BEGIN" and "END" delimiter lines.
      </td>
    </tr>
  
negative.code:   <tr>
      <td><pre><code>
    cc:
      staging_upload_user: STAGING_UPLOAD_USER
      staging_upload_password: STAGING_UPLOAD_PASSWORD
      bulk_api_password: BULK_API_PASSWORD
      db_encryption_key: CCDB_ENCRYPTION_KEY
  	  </code></pre></td>
      The Cloud Controller has an API endpoint used by stagers to upload staged droplets, and the endpoint requires basic authentication. Generate a username and password, and replace <code>STAGING_UPLOAD_USER</code> and <code>STAGING_UPLOAD_PASSWORD</code> with those values.
      <br /><br />
      Replace <code>BULK_API_PASSWORD</code> with a password of your choosing. The password used by Health Manager to access the Cloud Controller's bulk API.
      <br /><br />
      Replace <code>CCDB_ENCRYPTION_KEY</code>
      with a secure key that you generate to encrypt sensitive values in the
      Cloud Controller database.
      </td>
    </tr>
    <tr>
  