anchor.diff:  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 %>).
  +<% current_page.data.title = "How Buildpacks Work in " + vars.product_short %>
  +
  +This topic describes how buildpacks are structured and detected in <%= vars.product_runtime %> (<%= vars.product_short %>).
   
   
   ## <a id='buildpack-scripts'></a> Buildpack Scripts
  
positive.code: * `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: 
  ### <a id='detection'></a> Buildpack Detection
  
  <%= 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:
  
  