anchor.diff:        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/>
  +    <td>Generate a PEM-encoded RSA key pair, and replace <code>JWT_SIGNING_KEY</code> with the private key, and <code>JWT_VERIFICATION_KEY</code> with the corresponding public key.<br/>
       Paste in the full keys, including the "BEGIN" and "END" delimiter lines.
       </td>
     </tr>
  
positive.code:     user: NATS_USER
      password: NATS_PASSWORD
  	  </code></pre></td>
      <td>Replace <code>NATS_USER</code> and
  		<code>NATS_PASSWORD</code> with a secure username and password. Cloud Foundry components will use this to communicate with each other over the NATS message bus.
      <br/><br/>
      You can use any values for username and password depending on your security needs.
  	  </td>
    </tr>
    <tr>
  
negative.code:     address: UAADB_ADDRESS
      port: UAADB_PORT
  	  </code></pre></td>
      <td>
        This section of the stub defines how the UAA should connect to its database. The values you place here will depend on how the database has been set up.
        <br /><br />
        If you used <code>bosh aws create</code>, you can find the necessary values in the generated file <code>aws_rds_bosh_receipt.yml</code>. The database is an Amazon RDS instance, and the <code>UAADB_*</code> values in the stub must match the scheme, username, password, address, and port defined by AWS.
        <br /><br />
        If you deployed your database some other way -- for example, using the <code>postgres</code> job in cf-release -- the <code>UAADB_*</code> values must match the configuration of the database node.
  	  </td>
    </tr>
  </table>
  