anchor.diff:  
   ### <a id="manifest"></a> Create the manifest  ###
   
  -If you are using an IaaS other than AWS, you need to use a text editor to create a deployment manifest, which is a YAML file named `micro-bosh.yml`.
  +If you are using an IaaS other than AWS, you need to use a text editor to create a deployment manifest.
   Refer to [Creating a BOSH Deployment Manifest](./create-manifest.html) for instructions.
   
   For AWS, there are BOSH CLI commands which generate the manifest for you.
  +
  +The MicroBOSH deployment manifest is a YAML file named `micro-bosh.yml` and should reside in the directory
  +named for the product it deploys (`openstack/boshtest/micro` in these examples).
   
   ## <a id="deploy"></a> Deploying MicroBOSH  ##
   
  
positive.code:     `export <BOSH_environment_variable>=<value>`
  
  Use the information you have [collected](#cloud) to identify values to assign.
  
  * For example, the file could look something like this:
  
  <pre class="terminal">
  export BOSH_DEPLOYMENT_NAME=boshtest
  export BOSH_VPC_DOMAIN=example.com
  export BOSH_VPC_SUBDOMAIN=myboshtest
  export BOSH_VPC_PRIMARY_AZ=us-east-1b
  export BOSH_VPC_ACCESS_KEY_ID=12345abcde12345abcde12345
  export BOSH_VPC_SECRET_ACCESS_KEY=12345abcde22345abcde32345abcde42345abcde
  </pre>
  
  * Now use the file to generate the BOSH environment variables:
  
  
negative.code: Before you deploy, you must set the BOSH CLI to use the correct manifest.
  This is called "setting the deployment."
  
  1. `cd` into the directory you created for MicroBOSH (`micro` in these examples).
  1. Set the deployment:
  
      `bosh micro deployment micro_bosh.yml`
  
  ### <a id="deploy"></a> Deploy MicroBOSH  ###
  
  1. `cd` into the directory you created for MicroBOSH (`micro` in these examples).
  1. Deploy MicroBOSH:
  
      `bosh micro deploy <stemcell_URL>`
  