anchor.diff:  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:
  +The following example in [Go](https://golang.org/) binds a binary to the PORT 
  +environment variable:
   
   ```go
   package main
  
positive.code: 
  ## <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.
  
  ## <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.
  
  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.
  
negative.code: 
  ## <a id='pushing_apps'></a> Pushing Apps ##
  
  Unlike most other Cloud Foundry buildpacks, you must specify the binary 
  buildpack to use it when staging your binary file.
  On a command line, use `cf push APP-NAME` with the `-b` option to specify the 
  buildpack.
  
  For example:
  