anchor.diff:  To deploy MicroBOSH you need a stemcell and a manifest.
   You do not need a release since MicroBOSH itself is included within the stemcell.
   
  -The IaaS you use determines the details of how you deploy MicroBOSH.
  +The IaaS you use determines many details of how you deploy MicroBOSH.
   This topic starts with a general procedure that applies for all IaaS's,
  -and ends with an example which provides the specifics of deploying on AWS.
  +and ends with an example focused on AWS.
   
   ## <a id="prep"></a> Preparing to Deploy  ##
   
  
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: 
  ### <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.
  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  ##
  
  