anchor.diff:      Deployment set to ~/my-micro-deployment/manifest.yml
       </pre>
   
  -    **Note**: The `WARNING!` message alerts you to a change in the targeted
  -	  IP address, and is not an error message, despite being incredibly confusingly
  -    highlighted in red and for all appearances informing you that something bad has happened.
  +    <p class="note"><strong>Note</strong>: Though the <code>WARNING!</code> message displays in red, it is not an error message. The message merely alerts you to a change in the targeted IP address. </p>
   
   1. Use `bosh micro deploy light-bosh-stemcell-2717-aws-xen-ubuntu-trusty-go_agent.tgz` to deploy MicroBOSH.
   
  -    **Note**: A red `No bosh-deployments.yml file found` warning is expected.
  -    If prompted to allow MicroBOSH to "save state" in the current directory,
  -    type **yes**.
  +    <p class="note"><strong>Note</strong>: A red <code>No bosh-deployments.yml file found</code> warning is expected. If prompted to allow MicroBOSH to save state in the current directory, type <strong>yes</strong>.</p>
   
       <pre class='terminal'>
       $ bosh micro deploy light-bosh-stemcell-2717-aws-xen-ubuntu-trusty-go_agent.tgz
  
positive.code: 
  ### <a id="create-vpc"></a>Create a Virtual Private Cloud ###
  
  1. On the AWS Console, select **VPC**.
  
  1. Currently, light stemcells are only available from US East. If you would like to use
  a light stemcell, set the AWS Region to **US East (N. Virginia)**. We will assume US East
  for this tutorial.
  
  1. Click **Start VPC Wizard**.
  
  
negative.code: 
  If the deployment fails, run `bosh micro delete`, then deploy again.
  
  If an error message displays that refers to your `access key signature`, check
  the accuracy of the ACCESS-KEY-ID and SECRET-ACCESS-KEY in the deployment
  manifest.
  
  If other error messages appear:
  
  * Check your `microbosh.yml` for errors.
  * Review your AWS configuration.
  