anchor.diff:  NoAppDetectedError
   </pre>
   
  -For a more detailed account of how <%= vars.app_runtime_abbr %> interacts with the buildpack, see [Sequence of Interactions](#interactions).
  +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.app_runtime_abbr %> platform and the buildpack. The sequence of interactions differs depending on whether the platform skips or performs buildpack detection.
  +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.app_runtime_abbr %> 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.app_runtime_abbr %> performs the following interactions:
  +<%= 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.
  
positive.code: java-buildpack=v3.0-https://github.com/cloudfoundry/java-buildpack.git#3bd15e1 open-jdk-jre=1.8.0_45 spring-auto-reconfiguration=1.7.0_RELEASE tomcat-access-logging-support=2.4.0_RELEASE tomcat-instance=8.0.21 tomcat-lifecycle-support=2.4.0_RELEASE ...
  ```
  
  <p class="note"><strong>Note:</strong> <%= vars.app_runtime_abbr %> detects only one buildpack by default. When multiple buildpacks are desired, you must explicitly specify them.</p>
  
  For more information, see [Buildpack Detection](#buildpack-detection).
  
  
negative.code: 
  ## <a id='buildpack-detection'></a> Buildpack Detection
  
  When you push an app, <%= vars.product_short %> uses a detection process to determine a single buildpack to use. For general information about this process, see the [How Diego Stages Buildpack Apps](../concepts/how-applications-are-staged.html#stage-buildpack) section of the _How Apps Are Staged_ topic.
  
  During staging, each buildpack has a position in a priority list. You can retrieve this position by running `cf buildpacks`.
  
  <%= vars.product_short %> checks if the buildpack in position 1 is a compatible buildpack. If the position 1 buildpack is not compatible, <%= vars.product_short %> moves on to the buildpack in position 2. <%= vars.product_short %> continues this process until the correct buildpack is found. 
  
  If no buildpack is compatible, the `cf push` command fails with the following error:
  
  