anchor.diff:      skip_cert_verify: false
   </pre>
   
  -Replace placeholders with the approriate data:
  +Replace placeholders with the appropriate data:
   
   - `PLACEHOLDER-DIRECTOR-UUID` - the BOSH director UUID. You can get it by running `bundle exec bosh status`.
   
   - `PLACEHOLDER-ACCESS-KEY-ID` and `PLACEHOLDER-SECRET-KEY` - AWS access key id and secret key. You can use the same ones as you used in the `bosh_environment` file above, or generate new ones.
   
   - `PLACEHOLDER-AWS-AVAILABILITY-ZONE` and `PLACEHOLDER-AWS-AVAILABILITY-ZONE2` - `BOSH_VPC_PRIMARY_AZ` and `BOSH_VPC_SECONDARY_AZ` from the `bosh_environment` file above.
  ->>>>>>> 592814033f718e4ee4f2cf7113dad13d932b7159
   
   - `PLACEHOLDER-SUBNET-FOR-AZ1` and `PLACEHOLDER-SUBNET-FOR-AZ2` - Look in `~/deployments/cf-example/aws_vpc_receipt.yml` (this file was generated when you ran `bosh aws create`).  They are under 'subnets' 'cf1' and 'cf2'.
   
  
positive.code: 1. Use `bosh aws destroy` to destroy your AWS environment.
  
      <table style="width: 60%;"><tr><td>
      <strong>WARNING</strong>: The command `bosh aws destroy` destroys everything in your AWS account, including all S3 buckets and all instances. Do not use this command unless you want to lose **everything** in your AWS account, including objects and files unrelated to your Cloud Foundry deployment.
      </td></tr></table>
  
  	<pre class="terminal">
  
negative.code: deployment.
  
  Example stub file:
  
  <pre class="terminal">
  ---
  