anchor.diff:  
   __Node__:
   
  -* Verified with: the SHA256 of the `node-vVERSION.tar.gz` file listed on `https://nodejs.org/dist/vVERSION/SHASUMS256.txt` For example, for Node version 4.4.6, the CF buildpacks team verifies with the SHA256 for `node-v4.4.6.tar.gz` on its [SHASUMS256](https://nodejs.org/dist/v4.4.6/SHASUMS256.txt) page.
  -* Example: [Enqueuing binary builds for Node 4.4.5 and 6.2.0](https://github.com/cloudfoundry/buildpacks-ci/commit/1747c697dc29db0180253c5d466804784cb3fcce)
  +* **Verified with**: The SHA256 of the `node-vVERSION.tar.gz` file listed on `https://nodejs.org/dist/vVERSION/SHASUMS256.txt` For example, for Node version 4.4.6, the CF buildpacks team verifies with the SHA256 for `node-v4.4.6.tar.gz` on its [SHASUMS256](https://nodejs.org/dist/v4.4.6/SHASUMS256.txt) page.
  +* **Example**: [Enqueuing binary builds for Node 4.4.5 and 6.2.0](https://github.com/cloudfoundry/buildpacks-ci/commit/1747c697dc29db0180253c5d466804784cb3fcce)
   
   ###<a id="build-python-buildpack"></a>Python Buildpack
   
   __Python__:
   
  -* Verified with: the MD5 of the `Gzipped source tarball`, listed on: `https://www.python.org/downloads/release/python-VERSION/` where `VERSION` has no periods. For example, for Python version `2.7.12`, use the MD5 for the `Gzipped source tarball` on its [Downloads](https://www.python.org/downloads/release/python-2712/) page.
  -* Example: [Enqueuing binary build for Python 2.7.12](https://github.com/cloudfoundry/buildpacks-ci/commit/79e4ce891281ce3ec376b00c967465fc8c7383f8)
  +* **Verified with**: The MD5 of the `Gzipped source tarball`, listed on  `https://www.python.org/downloads/release/python-VERSION/`, where `VERSION` has no periods. For example, for Python version `2.7.12`, use the MD5 for the `Gzipped source tarball` on its [downloads](https://www.python.org/downloads/release/python-2712/) page.
  +* **Example**: [Enqueuing binary build for Python 2.7.12](https://github.com/cloudfoundry/buildpacks-ci/commit/79e4ce891281ce3ec376b00c967465fc8c7383f8)
   
   ###<a id='build-java-buildpack'></a>Java Buildpack
   
   __OpenJDK__:
   
  -* Built from: the tarred [OpenJDK files](https://download.run.pivotal.io/openjdk/trusty/x86_64/index.yml) managed by the CF Java Buildpack team.
  -* Verified with: the MD5 of the tarred OpenJDK files.
  +* **Built from**: The tarred [OpenJDK files](https://download.run.pivotal.io/openjdk/trusty/x86_64/index.yml) managed by the CF Java Buildpack team
  +* **Verified with**: The MD5 of the tarred OpenJDK files
   
   ###<a id="build-ruby-buildpack"></a>Ruby Buildpack
   
   __JRuby__:
   
  -* Verified with: the MD5 of the Source `.tar.gz` file from the [JRuby Downloads](http://jruby.org/download) page.
  -* Example: [Enqueuing binary build for JRuby 9.1.2.0](https://github.com/cloudfoundry/buildpacks-ci/commit/1c90967bcb511e7657202a1308e530825e372158)
  +* **Verified with**: The MD5 of the Source `.tar.gz` file from the [JRuby Downloads](http://jruby.org/download) page
  +* **Example**: [Enqueuing binary build for JRuby 9.1.2.0](https://github.com/cloudfoundry/buildpacks-ci/commit/1c90967bcb511e7657202a1308e530825e372158)
   
   __Ruby__:
   
  -* Verified with: the SHA256 of the source from the [Ruby Downloads] (https://www.ruby-lang.org/en/downloads/) page
  -* Example: [Enqueuing binary builds for Ruby 2.2.5 and 2.3.1](https://github.com/cloudfoundry/buildpacks-ci/commit/8d06eaa6573146b9771de7f96cebf85e07719d79)
  +* **Verified with**: The SHA256 of the source from the [Ruby Downloads] (https://www.ruby-lang.org/en/downloads/) page
  +* **Example**: [Enqueuing binary builds for Ruby 2.2.5 and 2.3.1](https://github.com/cloudfoundry/buildpacks-ci/commit/8d06eaa6573146b9771de7f96cebf85e07719d79)
   
   __Bundler__:
   
  -* Verified with: the SHA256 of the `.gem` file from [Rubygems](https://rubygems.org/gems/bundler).
  -* Example: [Enqueuing binary build for Bundler 1.12.5](https://github.com/cloudfoundry/buildpacks-ci/commit/cd161594a564631dff13e8c101205f922beb5cf8)
  +* **Verified with**: The SHA256 of the `.gem` file from [Rubygems](https://rubygems.org/gems/bundler)
  +* **Example**: [Enqueuing binary build for Bundler 1.12.5](https://github.com/cloudfoundry/buildpacks-ci/commit/cd161594a564631dff13e8c101205f922beb5cf8)
   
   ###<a id="build-php-buildpack"></a>PHP Buildpack
   
   __PHP__:
   
  -* Verified with: the SHA256 of the `.tar.gz` file from the [PHP Downloads](http://php.net/downloads.php) page.
  +* **Verified with**: The SHA256 of the `.tar.gz` file from the [PHP Downloads](http://php.net/downloads.php) page.
   * For PHP5 versions, the CF buildpacks team enqueues builds in the `php-builds.yml` file in the `binary-builds` branch. For PHP7 versions, the CF buildpacks team enqueues builds in the `php7-builds.yml` file in the `binary-builds` branch.
  -* Example: [Enqueuing binary builds for PHP 5.5.37, 5.6.23, and 7.0.8](https://github.com/cloudfoundry/buildpacks-ci/commit/cfb02b7d590996d3727dea9192d2da1ae0aaa595)
  +* **Example**: [Enqueuing binary builds for PHP 5.5.37, 5.6.23, and 7.0.8](https://github.com/cloudfoundry/buildpacks-ci/commit/cfb02b7d590996d3727dea9192d2da1ae0aaa595)
   
   __Nginx__:
   
  -* Verified with: the `gpg-rsa-key-id` and `gpg-signature` of the version. The `gpg-rsa-key-id` is the same for each version/build, but the `gpg-signature` will be different. This information is located on the [Nginx Downloads](https://nginx.org/en/download.html) page.
  -* Example: [Enqueuing binary build for Nginx 1.11.0](https://github.com/cloudfoundry/buildpacks-ci/commit/b86a09a46eb071957adaecd3a16d1ebba9cd0973)
  +* **Verified with**: The `gpg-rsa-key-id` and `gpg-signature` of the version. The `gpg-rsa-key-id` is the same for each version/build, but the `gpg-signature` will be different. This information is located on the [Nginx Downloads](https://nginx.org/en/download.html) page.
  +* **Example**: [Enqueuing binary build for Nginx 1.11.0](https://github.com/cloudfoundry/buildpacks-ci/commit/b86a09a46eb071957adaecd3a16d1ebba9cd0973)
   
   __HTTPD__:
   
  -* Verified with: the MD5 of the `.tar.bz2` file from the [HTTPD Downloads](https://httpd.apache.org/download.cgi) page.
  -* Example: [Enqueuing binary build for HTTPD 2.4.20](https://github.com/cloudfoundry/buildpacks-ci/commit/cee826dc978f013840ef6a8193ec6ee75536778b)
  +* **Verified with**: The MD5 of the `.tar.bz2` file from the [HTTPD Downloads](https://httpd.apache.org/download.cgi) page
  +* **Example**: [Enqueuing binary build for HTTPD 2.4.20](https://github.com/cloudfoundry/buildpacks-ci/commit/cee826dc978f013840ef6a8193ec6ee75536778b)
   
   __Composer__:
   
  -* Verified with: the SHA256 of the `composer.phar` file from the [Composer Downloads](https://getcomposer.org/download/) page.
  -* For Composer, there is no build process as the `composer.phar` file is  the binary. In the manual process,
  -connect to the `pivotal-buildpacks` S3 bucket using the correct AWS credentials. Create a new directory with the name of the
  -composer version (ex. `1.0.2`) and put the appropriate `composer.phar` file into that directory. For Composer `v1.0.2`, connect and create the `php/binaries/trusty/composer/1.0.2` directory. Then place the `composer.phar` file into that directory so the binary
  -is available at `php/binaries/trusty/composer/1.0.2/composer.phar`.
  +* **Verified with**: The SHA256 of the `composer.phar` file from the [Composer Downloads](https://getcomposer.org/download/) page
  +* For Composer, there is no build process as the `composer.phar` file is the binary. In the manual process, connect to the `pivotal-buildpacks` S3 bucket using the correct AWS credentials. Create a new directory with the name of the
  +composer version, for example `1.0.2`, and put the appropriate `composer.phar` file into that directory. For Composer `v1.0.2`, connect and create the `php/binaries/trusty/composer/1.0.2` directory. Then place the `composer.phar` file into that directory so the binary is available at `php/binaries/trusty/composer/1.0.2/composer.phar`.
   
       <p class="note"><strong>Note</strong>: The <a href="https://github.com/cloudfoundry/buildpacks-ci">buildpacks-ci</a> <a href="https://github.com/cloudfoundry/buildpacks-ci/blob/master/pipelines/binary-builder.yml">binary-builder</a> pipeline automates the process of detecting, uploading, and updating Composer in the manifest.</p>
   
  -* Example: [Automated enqueuing of binary build for Composer 1.1.2](https://github.com/cloudfoundry/buildpacks-ci/commit/d51abbdb919ca51df86628b37366c55311b05f38)
  +* **Example**: [Automated enqueuing of binary build for Composer 1.1.2](https://github.com/cloudfoundry/buildpacks-ci/commit/d51abbdb919ca51df86628b37366c55311b05f38)
   
   
   ###<a id="build-staticfile-buildpack"></a>Staticfile Buildpack
   
   __Nginx__:
   
  -* Verified with: the `gpg-rsa-key-id` and `gpg-signature` of the version. The `gpg-rsa-key-id` is the same for each version/build, but the `gpg-signature` will be different. This information is located on the [Nginx Downloads](https://nginx.org/en/download.html) page.
  -* Example: [Enqueuing binary build for Nginx 1.11.0](https://github.com/cloudfoundry/buildpacks-ci/commit/b86a09a46eb071957adaecd3a16d1ebba9cd0973)
  +* **Verified with**: The `gpg-rsa-key-id` and `gpg-signature` of the version. The `gpg-rsa-key-id` is the same for each version/build, but the `gpg-signature` will be different. This information is located on the [Nginx Downloads](https://nginx.org/en/download.html) page.
  +* **Example**: [Enqueuing binary build for Nginx 1.11.0](https://github.com/cloudfoundry/buildpacks-ci/commit/b86a09a46eb071957adaecd3a16d1ebba9cd0973)
   
   ###<a id="build-binary-buildpack"></a>Binary Buildpack
   
  -The Binary buildpack does not have any dependencies.
  -
  +The Binary buildpack has no dependencies.
  
positive.code: 
  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:
  
      ```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`.
    * 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:
  
      ```yaml
      ---
  
negative.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 the same time. For example, to build both the Ruby 2.3.0 binary and the Ruby 2.3.1 binary, add the following to the YAML file:
  
      ```yaml
      ---
  