anchor.diff:  
   ### <a id='detect-script'></a>bin/detect ###
   
  -The `detect` script is used to determine whether or not to apply the buildpack to an application. The script is called with one argument, the `build` directory for the application. The build directory contains the files a user `cf push`ed. It returns an exit code of `0` if the buildpack is compatible with the application. In the case of System buildpacks, if the script does return `0`, it will also print the buildpack name, version and other helpful information to `STDOUT`. 
  +The `detect` script determines whether or not to apply the buildpack to an application. The script is called with one argument, the `build` directory for the application. The `build` directory contains the application files uploaded when a user performs a `cf push`. 
   
  -Shown below is an example `detect` script written in Ruby that checks for a Ruby application based on the existence of a `Gemfile`:
  +The `detect` script returns an exit code of `0` if the buildpack is compatible with the application. In the case of system buildpacks, the script also prints the buildpack name, version, and other helpful information to `STDOUT`. 
  +
  +The following is an example `detect` script written in Ruby that checks for a Ruby application based on the existence of a `Gemfile`:
   
   ~~~ruby
   
  
positive.code: 
  ~~~
  
  Optionally, the buildpack detect script can output additional details decided by the buildpack developer. Such as buildpack versioning information, a detailed list of configured frameworks and their associated versions. The following is an example of the detailed information returned by the Java buildpack:
  
  ~~~
  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 ...
  
negative.code: 
  #### Using buildpack-packager
  1. Create a manifest.yml in your buildpack.
  1. Run the packager in cached mode: 
    <pre class="terminal">$ buildpack-packager --cached</pre>
  
  The packager will add (almost) everything in your buildpack directory into a zip file. It will exclude anything marked for exclusion in your manifest.
  
  