anchor.diff:  ~/releases/cf-release$ bundle exec bosh target
   Current target is https://x.x.x.x:25555 (micro-xxxxxx)
   </pre>
  -If this does not match the name of your deployed micro BOSH, you can target the director using the IP from `~/deployments/micro/micro_bosh.yml`.
  +If this does not match the name of your deployed MicroBOSH, you can target the director using the IP from `~/deployments/micro/micro_bosh.yml`.
   
   Set your deployment to the generated manifest:
   <pre class="terminal">
  
positive.code: 
  Replace placeholders with the approriate data:
  
  - `PLACEHOLDER-DIRECTOR-UUID` - the bosh director UUID. You can get it by running `bundle exec bosh status`.
  
  - `PLACEHOLDER-ACCESS-KEY-ID` and `PLACEHOLDER-SECRET-KEY` - AWS access key id and secret key. You can use the same ones as you used in the `bosh_environment` file above, or generate new ones.
  
  
negative.code: </pre>
  
  The command prompts you for a username and password. Choose a
  username and password that you want to use later to access your MicroBOSH installation.
  
  After MicroBOSH has deployed successfully, you can check its status:
  
  <pre class="terminal">
  ~/deployments/cf-example$ bundle exec bosh status
  