anchor.diff:  Without it, you would likely need to perform a larger number of tasks, many of them difficult to replicate from deployment to deployment.
   Because deploying software is an iterative process, the amount of labor that this pattern saves is significant.
   
  +### <a id="other"></a> Other Activities    ###
  +
   Other activities typical of the care and feeding of distributed software deployments include:
   
   * Creating and editing users.
   * Inspecting the state of VMs.
   * Getting (viewing) and cancelling Director tasks.
   
  -You perform these activities before or after deployment, or both.
  +You perform these activities before, during, or after deployment.
  
positive.code: * A **manifest** that accounts for environmental constraints and specifies how you want to orchestrate your deployment.
  You can modify an example manifest to suit your purposes, or use a tool like spiff to create a manifest.
  
  Deployments that use multiple releases and multiple stemcells are supported.
  
  ## <a id="deploying"></a> Deploying Software with BOSH  ##
  
  To deploy software with BOSH, you perform four steps:
  
  
negative.code: 
  While the distributed software you use BOSH to deploy can be complex, the basic patterns for working with BOSH are straightforward.
  
  You begin by verifying that your IaaS is set up correctly to support BOSH, and then deploying a single-VM BOSH.
  How you proceed from there depends on two questions:
  
  1. Whether you want to deploy a Cloud Foundry PaaS, deploy other distributed software, or do both.
  1. Whether the single-VM BOSH suits your needs, or a multi-VM BOSH is preferable.
  
  The illustration below shows the paths to these outcomes and the choices along the way.
  
  <%= image_tag("bosh-outcomes.png") %>
  
  ## <a id="single-vm"></a> Deploying Single-VM BOSH  ##
  
  Before you use BOSH to deploy software, you must first deploy BOSH itself.
  You can choose either of the two supported single-VM BOSHes described below, or experimental, community-based methods not documented here.
  
  ### <a id="micro"></a> MicroBOSH  ###
  
  MicroBOSH runs within a single VM on any cloud infrastructure that is supported for deploying software with BOSH.
  To deploy MicroBOSH you need a stemcell and a manifest, but you do not need a release.
  MicroBOSH is suited to deploying software (as an alternative to multi-VM BOSH), and is the only supported way to deploy BOSH for production.
  MicroBOSH is included within the stemcell.
  
  ### <a id="lite"></a> BOSH Lite  ###
  
  [BOSH Lite] (https://github.com/cloudfoundry/bosh-lite) runs within a single VM created with [Vagrant] (http://www.vagrantup.com/).
  Scripts packaged with BOSH Lite make it simple to deploy on a laptop or other local environment.
  BOSH Lite is essentially a low-cost, low-risk development environment to test and experiment with BOSH.
  To deploy BOSH Lite, you do not need a release, a stemcell, or a manifest, only Vagrant and related files.
  
  ## <a id="multi-vm"></a> Deploying Multi-VM BOSH  ##
  
  Once you have MicroBOSH running, you can use it to deploy multi-VM BOSH or any other software that BOSH can deploy.
  
  **Note**: As shown in the illustration, deploying Multi-VM BOSH is optional.
  
  To deploy BOSH using MicroBOSH you must:
  
  * [Download](http://bosh-artifacts.cfapps.io) a **release** of BOSH, and a **stemcell** appropriate to the cloud infrastructure and OS where you plan to deploy.
  
  * [Create](./create-manifest.html) a **manifest** that accounts for environmental constraints and specifies how you want to orchestrate your deployment.
  
  ## <a id="deploying"></a> Deploying Software with BOSH  ##
  
  ### <a id="before"></a> Before you Deploy  ###
  
  Before you deploy, you must have:
  
  