anchor.diff:  
   1. Create a deployment manifest YAML file. 
   
  -The following example is a MicroBOSH deployment manifest template. Copy and paste the template into a text editor and save the manifest to your deployment directory.
  -
  -You must replace the following properties, which we describe in [Step 2: Prepare an AWS Account](#prepare-aws).
  -
  -* ELASTIC-IP-ADDRESS
  -* MICROBOSH-SUBNET-ID
  -* ACCESS-KEY-ID
  -* SECRET-ACCESS-KEY
  -
  -<p class="note"><strong>Note</strong>: The example below has the file name <code>manifest.yml</code>, which we reference in other examples in this topic.</p>
  +    The following example is a MicroBOSH deployment manifest template. Copy and paste the template into a text editor and save the manifest to your deployment directory.
  +
  +    You must replace the ELASTIC-IP-ADDRESS, MICROBOSH-SUBNET-ID, ACCESS-KEY-ID, and SECRET-ACCESS-KEY properties, and we describe how to do this in [Step 2: Prepare an AWS Account](#prepare-aws).
  +
  +    <p class="note"><strong>Note</strong>: The example below has the file name <code>manifest.yml</code>, which we reference in other examples in this topic.</p>
  +
   
   <pre class='code'>
   ---
  
positive.code:     Deployment set to ~/my-micro-deployment/manifest.yml
      </pre>
  
      <p class="note"><strong>Note</strong>: Though the <code>WARNING!</code> message displays in red, it is not an error message. The message merely alerts you to a change in the targeted IP address. </p>
  
  1. Use `bosh micro deploy light-bosh-stemcell-2717-aws-xen-ubuntu-trusty-go_agent.tgz` to deploy MicroBOSH.
  
      <p class="note"><strong>Note</strong>: A red <code>No bosh-deployments.yml file found</code> warning is expected. If prompted to allow MicroBOSH to save state in the current directory, type <strong>yes</strong>.</p>
  
      <pre class='terminal'>
      $ bosh micro deploy light-bosh-stemcell-2717-aws-xen-ubuntu-trusty-go_agent.tgz
  
negative.code: 
  1. Add the following rules for access by MicroBOSH and BOSH.
  
      MicroBOSH needs ports 25555 (BOSH Director), 6868 (BOSH Agent), and 22 (SSH to
  debug) opened for inbound traffic, and VMs that BOSH deploys might need access to all TCP and UDP ports from within the same Security Group.
  
  
  