anchor.diff:  
   	`ls -al micro-bosh.yml`
   
  -## <a id="set"></a> Set the Deployment  ##
  +## <a id="deploy"></a> Deploying MicroBOSH  ##
  +
  +Once preparation is complete, deploying MicroBOSH is
  +
  +### <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  ###
   
   Before you deploy, you must set the BOSH CLI to use the correct manifest.
   This is called "setting the deployment."
   
   1. cd into the _which?_ directory.
  -1. Generate the manifest:
  +1. Run the `deployment`:
   
       `bosh micro deployment micro/micro_bosh.yml`
   
  -## <a id="deploy"></a> Deploy MicroBOSH  ##
  +### <a id="deploy"></a> Deploy MicroBOSH  ###
   
   1. cd into the _which?_ directory.
   1. Deploy MicroBOSH:
   
     `bosh micro deploy <stemcell_URL>`
   
  +## <a id="verify"></a> Verifying your Deployment  ##
  +
  +_Mention that BATS is not needed here, provide a simple sanity check._
   
   
  +
  
positive.code: Pause when you get to the one that says:
  "Your 1 User(s) have been created successfully.
  This is the last time these User security credentials will be available for download."
  1. Copy the `Access Key ID`
  1. Copy the `Secret Access Key`
  
  ## <a id="enviro"></a> Set Up your Local Environment   ##
  
  At the command line on your local system:
  
  
negative.code: You do not need a release since MicroBOSH itself is included within the stemcell.
  
  The details of how you deploy MicroBOSH depend on which IaaS you use.
  This topic outlines a general procedure that applies for all IaaS's,
  and provides examples from a particular deployment which happens to use AWS.
  
  ## <a id="prep"></a> Preparing to Deploy  ##
  
  ### <a id="cloud"></a> Set Up your Deployment Area in the Cloud ###
  
  You need to collect or decide:
  
  