anchor.diff:  
   ### <a id="enviro"></a> Set up your local environment   ###
   
  -In the directory that contains files for your MicroBOSH deployment (`deployments-aws/boshtest` in these examples),
  +In the directory that contains files for your MicroBOSH deployment (`openstack/boshtest/micro` in these examples),
   create a text file named `bosh_environment`.
   
   * For each item of information enumerated [above](#cloud),
  
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: 
  **Note**: While not required, the instructions in this section are highly recommended.
  
  Set up a directory structure with three levels:
  
  1. A top-level directory for each IaaS you plan to use.
  1. Inside the IaaS directory, directories for each cloud you intend to deploy on the IaaS.
  1. Inside each cloud directory, directories for each product you intend to deploy. In this context, MicroBOSH is a product.
  
  * For example, you might be planning to deploy MicroBOSH on a cloud named `boshtest`, that in turn is deployed to the OpenStack IaaS.
  You would create a directory for each, such that the path to your MicroBOSH deployment could be `openstack/boshtest/micro`.
  
  ### <a id="stemcell"></a> Obtain a stemcell  ###
  
  