anchor.diff:  
   If the deployment fails, run `bosh micro delete`, then deploy again.
   
  -If you see an error message that refers to your `access key signature`, check
  +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 you see other error messages:
  +If other error messages appear:
   
   * Check your `microbosh.yml` for errors.
   * Review your AWS configuration.
  
positive.code:     registry: {address: 10.0.0.6}
  </pre>
  
  ## <a id="prepare-aws"></a>Step 2: Prepare AWS Account ##
  
  If you do not have an AWS account, [create one](http://goo.gl/MaAybK).
  
  To configure AWS Account for MicroBOSH:
  
  * [Obtain AWS credentials](#credentials)
  * [Create a Key Pair](#create-key-pair)
  
negative.code:                     ... older stemcells ...
  </pre>
  
  1. Run `bosh download public stemcell STEMCELL-NAME`to download a stemcell.
  
  BOSH stemcell names include the type, BOSH build number, target IaaS and hypervisior, and underlying operating system.
  
      To download the latest light Ubuntu Trusty stemcell:
  
      <pre class='terminal'>
      $ bosh download public stemcell light-bosh-stemcell-2717-aws-xen-ubuntu-trusty-go_agent.tgz
  </pre>
  
  ## <a id="deploy"></a>Step 4: Deploy MicroBOSH ##
  
  