anchor.diff:  1. To build a cached buildpack artifact, run the following command:
   
       ```
  -    buildpack-packager build -cached -stack windows2016
  +    buildpack-packager build -cached -stack STEMCELL-NAME
       ```
  +
  +    Where:  
  +    * `STEMCELL-NAME` is the name of your stemcell, typically 'windows2016'.  
  +
       <p class='note'><strong>Note:</strong> If the buildpack code contains a mistake,
       <code>buildpack-packager</code> throws an error. Once all local errors are corrected, you must
  -    push your app to with the new extension buildpack to determine whether the new buildpack
  +    push your app, with the new extension <code>buildpack</code>, to determine whether the new buildpack
       functions as intended.</p>
   
  -1. Upload the buildpack to a private web server accessible to Cloud Foundry. You can also use an S3
  -bucket or Azure Storage. You can upload the finished buildpack to the same web server as your
  -dependencies. 
  +1. Upload the buildpack to a private web server accessible to Cloud Foundry. 
  +You can upload the finished buildpack to the same web server as your dependencies. 
  +You can also use an S3 bucket or Azure Storage.  
   
   1. To deploy your app with the extension buildpack, run the following command:
   
       ```
  -    cf push my-app -s windows2016 -b BUILDPACK-URL -b hwc_buildpack
  +    cf push my-app -s STEMCELL-NAME -b BUILDPACK-URL -b hwc_buildpack
       ```
  -    Where `BUILDPACK-URL` is the URL where you uploaded the buildpack.
  +    Where:
  +    * `STEMCELL-NAME` is the name of your stemcell.
  +    * `BUILDPACK-URL` is the URL where you uploaded the buildpack.  
  +
       For example:
       <pre class='terminal'>
       $ cf push my-app -s windows2016 -b http<span>:</span>//s3.amazon.com/my-bucket/my-example-buildpack.zip -b hwc_buildpack
  
positive.code:     ```
      Where:
      * `DLL-ZIP-FILE` is the name of your DLL zip file.
      * `GENERATED-SHA-256` is a SHA generated by running the following command:
  
          ```
          shasum -a256 DLL-ZIP-FILE
          ```
          Where `DLL-ZIP-FILE` is the name of your DLL zip file.
  
  1. Ensure the `include_files` section of the manifest contains `bin/supply.exe`.
  
  
negative.code: 
  1. Copy the DLLs for the dependencies into a zip file.
  
  1. On the command line, browse to the directory containing the new zip file.
  
  1. To generate a SHA for your zip file, run the following command:
  ```
  shasum -a256 DLL-ZIP-FILE
  ```
  
  Where `DLL-ZIP-FILE` is the name of your DLL zip file. 
  
  1. Upload the zip file containing your dependencies to a private web server that is accessible by
  Cloud Foundry. You can also use an S3 bucket or Azure Storage.
  
  