anchor.diff:  
   * Install the BOSH CLI v2.
   For more information, see the <a href="https://bosh.io/docs/cli-v2.html#install">BOSH documentation</a>.
  -* Review the migration prerequisites in the [cf-deployment-transition](https://github.com/cloudfoundry/cf-deployment-transition/blob/master/README.md#migration-prerequisites) GitHub repo,
  +* Review the migration prerequisites in the [cf-deployment-transition](https://github.com/cloudfoundry/cf-deployment-transition/blob/master/README.md#migration-prerequisites) GitHub repository,
   with particular attention to the following:
     - You must enable all TLS features.
     - You must be using external databases.
  
positive.code: 
  For a list of all job name changes from `cf-release`,
  see the `cfr-to-cfd.yml` ops file
  in the [cf-deployment-transition](https://github.com/cloudfoundry/cf-deployment-transition/blob/master/cfr-to-cfd.yml) GitHub repo.
  This file does not list name changes from the Diego deployment.
  However, the only job from the Diego deployment that you must scale is `diego-cells`.
  
  
negative.code: 
  * You must apply the ops file for scaling your components that you created in the previous step.
  * You must apply the `cfr-to-cfd.yml` ops file.
    Download this ops file from the [cf-deployment-transition](https://github.com/cloudfoundry/cf-deployment-transition/blob/master/cfr-to-cfd.yml) GitHub repository.
    If you are disabling `cf-deployment` features to simplify the transition,
    you must also apply the appropriate ops files from the transition repository.
  * The `deployment-vars.yml` file you pass with the `--vars-store` flag must be the variables store file you created above.
  
  ## <a id='delete-diego'></a> Step 6: Delete Old Diego Deployment
  