anchor.diff:  
   ## <a id='bosh_trusted_cert'></a>BOSH Configured Custom Trusted Certificate Support ##
   
  -Certificates deployed through [BOSH configured custom trusted certificates](http://bosh.io/docs/trusted-certs.html) will exist in the `/etc/ssl/certs` directory and as such can be used by a binary application.
  +Certificates deployed through [BOSH configured custom trusted certificates](http://bosh.io/docs/trusted-certs.html) exist in the 
  +`/etc/ssl/certs` directory and can be used by binary applications.
   
   ## <a id='help_support'></a>Help and Support ##
   
  -Join the #buildpacks channel in our [Slack community] (http://slack.cloudfoundry.org/) if you need any further assistance.
  +Join the #buildpacks channel in our [Slack community](http://slack.cloudfoundry.org/) if you need any further assistance.
   
  -For more information about using and extending the binary buildpack in Cloud Foundry, see
  -the [binary-buildpack GitHub repo](https://github.com/cloudfoundry/binary-buildpack).
  +For more information about using and extending the binary buildpack in Cloud 
  +Foundry, see the [binary-buildpack GitHub repo](https://github.com/cloudfoundry/binary-buildpack).
   
   You can find current information about this buildpack on the binary buildpack
  -[release page](https://github.com/cloudfoundry/binary-buildpack/releases) in GitHub.
  +[release page](https://github.com/cloudfoundry/binary-buildpack/releases) in 
  +GitHub.
  
positive.code: Cloud Foundry expects your binary to bind to the port specified by the `PORT`
  environment variable.
  
  The following example in [Go](https://golang.org/) binds a binary to the PORT environment variable:
  
  ```go
  package main
  
negative.code: }
  ```
  
  Your binary should run without any additional runtime dependencies on the 
  cflinuxfs2 or lucid64 root filesystem (rootfs).
  Any such dependencies should be statically linked to the binary.
  
  To boot a docker container running the cflinuxfs2 filesystem, run the following
  