anchor.diff:  
   ## <a id="prep"></a> Preparing to Deploy ##
   
  -Preparation consists of thinking through the deployment,
  -collecting the
  -To deploy software with BOSH, you need a release, a stemcell, and a manifest.
  +Preparation consists of thinking through how to orchestrate the environment you want to deploy,
  +and how to configure the network and instrument VMs.
  +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 ###
   
   For the sake of this example, let's assume that you have decided to deploy BOSH to an environment with two VMs.
  -Your reasoning might be that security architecture
  -The "thinking" parts of BOSH-Director, Health Monitor, Messaging (NATS), and PowerDNS—
  -and the other for the data-storing parts: Blobstore, Redis, and Postgres.
  -
  +One reason you might do this is to implement a security architecture where the data-storing parts of BOSH
  +(Blobstore, Redis, and Postgres) reside on one VM, while the "thinking" parts of BOSH
  +(Director, Health Monitor, NATS, and PowerDNS) reside on the other.
  +This would allow you to restrict access to data, while allowing deployment operators freer access to
  +the BOSH Director.
   
   ### <a id=""></a> Set up the IaaS ###
   
  -You collect all the information about your vSphere and vCenter that you need to configure the environment you plan to deploy.
  +You collect the information about your vSphere and vCenter that you need to configure the environment.
   
   This includes:
   
  
positive.code: Deployed `manifest.yml' to `embarcadero-microbosh'
  </pre>
  
  ### <a id="afterword"></a> Verify ###
  
  <pre class="terminal">
  $ bosh target 172.16.99.212
  Target set to `bosh2'
  Your username: admin
  Enter password: *****
  Logged in as `admin'
  </pre>
  
  
  ## <a id="example-manifest"></a> Example Manifest for Deploying multi-VM BOSH with MicroBOSH ##
  
  ~~~yaml
  ---
  
negative.code: 
  Create the manifest to reflect the desired orchestration of the environment along with the network configuration information
  for your IaaS.
  Refer to the [example manifest](#example-manifest) at the end of this topic.
  
  ### <a id=""></a> Download stemcell and release from public site ###
  
  