anchor.diff:  
   To build the binary for a dependency, perform the following steps:
   
  -1. Change into the `public-buildpacks-ci-robots` directory and check that there are no uncommitted changes.
  -	<pre class='terminal'>
  -	$ cd ~/workspace/public-buildpacks-ci-robots
  -	$ git status
  -	</pre>
  -1. Pull the branch to make sure it is up to date.
  -	<pre class="terminal">
  -	$ git pull -r
  -	</pre>
  -1. Change to the `binary-builds` directory.
  -	<pre class="terminal">
  -	$ cd binary-builds
  -	</pre>
  -1. Locate the YAML file for the buildpack you want to build a binary for. The directory contains YAML files for all the packages and dependencies tracked by the CF buildpacks team. Each YAML file correlates to the build queue for one dependency or package and the naming format is `DEPENDENCY-NAME.yml`. For example, the YAML file tracking the build queue for Ruby is called `ruby-builds.yml` and contains the following contents:
  +1. Navigate to the `public-buildpacks-ci-robots` directory and verify no uncommitted changes exist.
  +  <pre class='terminal'>
  +  $ cd ~/workspace/public-buildpacks-ci-robots
  +  $ git status
  +  </pre>
  +1. Run the `git pull` command in the directory to ensure it contains most recent version of the contents.
  +  <pre class="terminal">
  +  $ git pull -r
  +  </pre>
  +1. Navigate to the `binary-builds` directory.
  +  <pre class="terminal">
  +  $ cd binary-builds
  +  </pre>
  +1. Locate the YAML file for the buildpack you want to build a binary for. The directory contains YAML files for all the packages and dependencies tracked by the CF buildpacks team. Each YAML file correlates to the build queue for one dependency or package, and uses the naming format `DEPENDENCY-NAME.yml`. For example, the YAML file tracking the build queue for Ruby is named `ruby-builds.yml` and contains the following contents:
   
       ```yaml
       ---
       ruby: []
       ```
   
  -1. Different buildpacks use different signatures for verification. Determine which signature your buildpack requires by consulting the [list](#buildpacks) below and follow the instructions to locate the SHA256, MD5, or GPG signature for the binary:
  -  * For the SHA256 of a file, run `shasum -a 256 FILE`.
  -  * For the MD5 of a file, run `md5 FILE`.
  +1. Different buildpacks use different signatures for verification. Determine which signature your buildpack requires by consulting the list in the [buildpacks](#buildpacks) section of this topic and run follow the instructions to locate the SHA256, MD5, or GPG signature for the binary:
  +  * For the SHA256 of a file, run `shasum -a 256 FILE-NAME`.
  +  * For the MD5 of a file, run `md5 FILE-NAME`.
     * For the GPG signature (for Nginx), see the [Nginx Downloads](http://nginx.org/en/download.html) page.
   
  -1. Add the version and verification for the new binary to the YAML file as attributes of an element under the dependency name. For example, to build the Ruby 2.3.0 binary verified with SHA256, add the following:
  +1. Add the version and verification for the new binary to the YAML file as attributes of an element under the dependency name. For example, to build the Ruby 2.3.0 binary verified with SHA256, add the following to the YAML file:
   
       ```yaml
       ---
  
positive.code: 
      <p class="note"><strong>Note</strong>: Do not preface the version number with the name of the binary or language. For example, specify <code>2.3.0</code> for <code>version</code> instead of <code>ruby-2.3.0</code>.</p>
  
      You can enqueue builds for multiple versions at once. For example, to build both the Ruby 2.3.0 binary and the Ruby 2.3.1 binary, add the following:
  
      ```yaml
      ---
  
negative.code:     $ git push
      </pre>
  
  1. Monitor the `LANGUAGE-buildpack` pipeline in Concourse. Once the test suite builds, the `specs-lts-develop` job and `specs-edge-develop` job, pass for the buildpack, you can deliver the Tracker story for the new Dependency release. Copy and paste links for the successful test suite builds into the Tracker story.
  
  ##<a id='buildpacks'></a>Buildpacks
  
  