anchor.diff:  
   ### <a id='detection'></a> Buildpack Detection
   
  -<%= vars.app_runtime_abbr %> performs buildpack detection if the developer does not specify one or more buildpacks in the app manifest or in the `cf push APP-NAME -b BUILDPACK-NAME` cf CLI command.
  -
  -<p class="note"><strong>Note:</strong> <%= vars.app_runtime_abbr %> detects only one buildpack to use with the app.</p>
  +<%= vars.product_short %> performs buildpack detection if the developer does not specify one or more buildpacks in the app manifest or in the `cf push APP-NAME -b BUILDPACK-NAME` cf CLI command.
  +
  +<p class="note"><strong>Note:</strong> <%= vars.product_short %> detects only one buildpack to use with the app.</p>
   
   If the platform performs detection, it:
   
  
positive.code: owner: Buildpacks
  ---
  
  <% current_page.data.title = "How Buildpacks Work in " + vars.app_runtime_abbr %>
  
  This topic describes how buildpacks are structured and detected in <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>).
  
  
  ## <a id='buildpack-scripts'></a> Buildpack Scripts ##
  
  A buildpack repository may contain the following five scripts in the `bin` directory:
  
  * `bin/detect` determines whether or not to apply the buildpack to an app.
  * `bin/supply` provides dependencies for an app.
  * `bin/finalize` prepares the app for launch.
  * `bin/release` provides feedback metadata to <%= vars.app_runtime_abbr %> indicating how the app should be executed.
  * `bin/compile` is a deprecated alternative to `bin/supply` and `bin/finalize`.
  
  The `bin/supply` and `bin/finalize` scripts replace the deprecated `bin/compile` script. Older buildpacks may still use `bin/compile` with the latest version of <%= vars.app_runtime_abbr %>. In this case, applying multiple buildpacks to a single app is not supported. Similarly, newer buildpacks may still provide `bin/compile` for compatibility with Heroku and older versions of <%= vars.app_runtime_abbr %>.
  
  The `bin/supply` script is required for non-final buildpacks. The `bin/finalize` (or `bin/compile`) script is required for final buildpacks.
  
  
negative.code: NoAppDetectedError
  </pre>
  
  For a more detailed account of how <%= vars.product_short %> interacts with the buildpack, see [Sequence of Interactions](#interactions).
  
  
  ## <a id='interactions'></a> Sequence of Interactions 
  
  This section describes the sequence of interactions between the <%= vars.product_short %> platform and the buildpack. The sequence of interactions differs depending on whether the platform skips or performs buildpack detection.
  
  ### <a id='no-detection'></a> No Buildpack Detection
  
  <%= vars.product_short %> skips buildpack detection if the developer specifies one or more buildpacks in the app manifest or in the `cf push APP-NAME -b BUILDPACK-NAME` cf CLI command.
  
  If you explicitly specify buildpacks, <%= vars.product_short %> performs the following interactions:
  
  1. For each buildpack except the last buildpack, the platform:
  	1. Creates the `deps`/`index` directory.
  