anchor.diff:      </pre>
       <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 an app to determine whether the new buildpack functions as intended and contains the
  -    correct dependencies.</p>
  +    push your app to with the new extension buildpack 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
  
positive.code:     ```
      Where:
      * `DLL-ZIP-FILE` is the name of your DLL zip file.
      * `GENERATED-SHA-256` is a SHA generated by running `shasum -a256 DLL-ZIP-FILE`.
  
  1. Ensure the `include_files` section of the manifest contains `bin/supply.exe`.
  
  
negative.code: ## <a id='combine'></a>Combine Extension Buildpack with Other Features
  
  If your extension buildpack has executables or scripts that need to be run, you can reference them
  either in the start command or in profile scripts.
  
  * For more information about the start command, see
  [command](../../devguide/deploy-apps/manifest.html#start-commands) in <em>Deploying with Application Manifests</em>.
  