anchor.diff:  
   For AWS, there are BOSH CLI commands which generate the manifest for you.
   
  -For example:
  -
  -1. `cd` into the directory you created for manifests (`manifests` in these examples).
  -1. Generate the manifest:
  -
  -    `bosh aws generate micro_bosh aws_vpc_receipt.yml aws_route53_receipt.yml`
  -1. Verify that the manifest was generated:
  -
  -    `ls -al micro-bosh.yml`
  -
   ## <a id="deploy"></a> Deploying MicroBOSH  ##
   
   Once preparation is complete, you deploy MicroBOSH in three steps.
  -
  -### <a id="upload"></a> Upload the stemcell  ###
  -
  -**Note**: Skip this step if you are using AWS.
  -
  -* From the _which?_ directory, run the command:
  -    `foo`
   
   ### <a id="set"></a> Set the deployment  ###
   
  
positive.code: 
      `env | grep BOSH`
  
  ### <a id="bootstrap"></a> AWS-only: Add bootstrap capability  ###
  
  _What to say here? Is this the right place?_
  
  1. `cd` into the top-level directory you created (`deployments-aws` in these examples).
  1. Run this command to _how to phrase?_
  
      `aws create bootstrap`
  
  **Note**: This command may take between thirty minutes and an hour to complete.
  
  ### <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`.
  
negative.code: 1. Any IaaS-specific information about where your deployment should reside.
  1. The name and credentials of an admin user for your deployment.
  
  ### <a id="local"></a> Set up a local work area  ###
  
  **Note**: While not required, the instructions in this section are highly recommended.
  