anchor.diff:  You need to set up your IaaS instance and collect the networking information that goes in the manifest.
   Then you create the manifest and obtain a release and a stemcell.
   
  -### <a id=""></a> Plan how you want to orchestrate your environment ###
  +### <a id="plan"></a> Plan how you want to orchestrate your environment ###
   
   For the sake of this example, let's assume that you have decided to deploy BOSH to an environment with two VMs.
   One reason you might do this is to implement a security architecture where the data-storing parts of BOSH
  
positive.code: 
  Refer to the [example manifest](#example-manifest) at the end of this topic.
  
  ### <a id=""></a> Download stemcell and release from public site ###
  
  You [download](http://bosh-artifacts.cfapps.io/) the latest release of BOSH, and a stemcell suitable for your preferred combination of IaaS and VM type.
  In this example, these are:
  
negative.code: These, and the static IPs, are off-limits to BOSH when BOSH needs to dynamically use an IP address for tasks like compilation.
  Always reserve the IP of the MicroBOSH that deploys BOSH.
  
  ### <a id="create-manifest"></a> Create the manifest ###
  
  The manifest should incorporate the network configuration information for your IaaS.
  It should also reflect the way you want to orchestrate the deployment across the multiple VMs.
  