anchor.diff:  
   <strong><%= modified_date %></strong>
   
  -Buildpacks are a convenient way of packaging framework and/or runtime support
  -for your application.
  -
  -For example, by default Cloud Foundry does not support Haskell. Using a buildpack for Haskell allows you to add support for it at the deployment stage. When you push an application written using Haskell, the required buildpack is automatically installed on the Cloud Foundry Droplet Execution Agent (DEA) where the application will run.
  -
  -<%= vars.disable_custom_buildpacks_note %>
  -
  - <p class="note"><strong>Note</strong>: A common development practice for custom buildpacks is to fork existing buildpacks and sync subsequent patches from upstream. To merge upstream patches to your custom buildpack, use the approach that Github recommends for <a href="https://help.github.com/articles/syncing-a-fork">syncing a fork</a>.</p>
  +Buildpacks are a convenient way of packaging frameworks and/or runtime support for your application. Cloud Foundry comes with system buildpacks out of the box and provides an interface for developers to create custom buildpacks.
   
   ## <a id='custom-buildpacks'></a>Custom Buildpacks ##
   
  -The structure of a buildpack is straightforward. A buildpack repository contains three main scripts, situated in a folder named `bin`.
  +A buildpack repository contains three main scripts, situated in a folder named `bin`.
   
   ### <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. It returns an exit code of `0` if the application can be supported by the buildpack. If the script does return `0`, it should also print a framework name to STDOUT.
  +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 `buildw directory for the application. It returns an exit code of `0` if the buildpack is compatible with the application. If the script does return `0`, it should print a framework name to STDOUT.
   
   Shown below is an example `detect` script written in Ruby that checks for a Ruby application based on the existence of a `Gemfile`:
   
  
positive.code: </pre>
  
  The application will then be deployed to Cloud Foundry, and the buildpack will be cloned from the repository and applied to the application (provided that the `detect` script returns `0`).
  
negative.code: 
  ### <a id='compile-script'></a>bin/compile ###
  
  The `compile` script builds a droplet by packaging the application's dependencies, assuring that the application has all the necessary components needed to run.
  
  The script is run with two arguments, the build directory for the application and the cache directory, which is a location the buildpack can use to store assets during the build process.
  
  