anchor.diff:  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`.
  +You would create a directory for each, such that the path to your MicroBOSH deployment could be `deploy2openstack/boshtest/micro`.
   
   ### <a id="stemcell"></a> Obtain a stemcell  ###
   
  
positive.code: and properly set up environments both locally and in the cloud.
  
  **Note**: Along with the decision you have made to deploy MicroBOSH,
  you should have made a few more decisions:
  
  * What IaaS to use.
  * What to name the cloud you plan to deploy on that IaaS.
  
negative.code: 
  ### <a id="enviro"></a> Set up your local environment   ###
  
  In the directory that contains files for your MicroBOSH deployment (`deploy2openstack/boshtest/micro` in these examples),
  create a text file named `bosh_environment`.
  
  * For each item of information enumerated [above](#cloud),
  