anchor.diff:  
   ### <a id=""></a> Target and log into MicroBOSH ###
   
  -Use the `bosh target` command so that the BOSH CLI runs on the MicroBOSH you want to use to deploy software.
  +Ensure that the BOSH CLI runs on the MicroBOSH you want to use to deploy software.
  +(In some environments there might be more than one BOSH or MicroBOSH.)
  +You do this by passing the IP address of the MicroBOSH to the `bosh target` command.
  +
  +<pre class="terminal">
  +$ bosh target 172.16.99.11
  +Target set to `embarcadero-microbosh'
  +</pre>
  +
   Then log in on the MicroBOSH.
   Run the `bosh vms` command which shows VMs that the (Micro)BOSH has deployed.
   For now, `bosh vms` shows no VMs deployed.
   
   <pre class="terminal">
  -$ bosh target 172.16.99.11
  -Target set to `embarcadero-microbosh'
  -
  - |1.9.3-p484| embarcadero in ~/bosh
   $ bosh login admin ********
   Logged in as `admin'
   
  - |1.9.3-p484| embarcadero in ~/bosh
   $ bosh vms
   No deployments
   </pre>
   
   ## <a id="deploying"></a> Deploying ##
   
  -
  +Enact the [familiar pattern](./workflow.html#deploying) _upload stemcell, upload release, set deployment, deploy_.
   
   ### <a id="stemcell"></a> Upload the Stemcell ###
   
  
positive.code: $ bosh stemcells
  No stemcells
  </pre>
  
  
  ### <a id="release"></a> Upload the Release ###
  
  
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 ###
  
  