anchor.diff:  
   ### <a id='VCAP-SERVICES'></a>VCAP\_SERVICES ###
   
  -For [bindable services](../services/) Cloud Foundry will add connection details
  -to the `VCAP_SERVICES` environment variable when you restart your application,
  +For [bindable services](../services/), Cloud Foundry adds connection details to 
  +the `VCAP_SERVICES` environment variable when you restart your application, 
   after binding a service instance to your application.
   
  -The results are returned as a JSON document that contains an object for each
  +The results are returned as a JSON document that contains an object for each 
   service for which one or more instances are bound to the application.
   The service object contains a child object for each service instance of that
   service that is bound to the application.
  
positive.code: 
  ### <a id='CF-INSTANCE-PORT'></a>CF\_INSTANCE\_PORT ###
  
  The external (host-side) port corresponding to the internal (container-side) port with value [PORT](#PORT). For instances on Diego, this value is generally **not** the same as the [PORT](#PORT) of the app instance.
  
  `CF_INSTANCE_PORT=61045`
  
  ### <a id='CF-INSTANCE-PORTS'></a>CF\_INSTANCE\_PORTS ###
  
  The list of mappings between internal (container-side) and external
  (host-side) ports allocated to the instance's container.
  Note that not all of the internal ports are necessarily available for the
  application to bind to, as some of them may be used by system-provided
  services that also run inside the container.
  On the DEAs, these internal and external values will be the same, but on Diego
  Cells, they may differ.
  
  `CF_INSTANCE_PORTS=[{external:61045,internal:5678},{external:61046,internal:2222}]`
  
  
  ### <a id='HOME'></a>HOME ###
  Root folder for the deployed application.
  
negative.code: 
  ## <a id='app-system-env'></a>Application-Specific System Variables ##
  
  The subsections that follow describe the environment variables that Cloud 
  Foundry makes available to your application container.
  Some of these variables are the same across instances of a single application, 
  and some vary from instance to instance.
  
  You can access environment variables programmatically, including variables 
  defined by the buildpack.
  For more inforation, refer to the buildpack documentation for 
  [Java](../../buildpacks/java/java-tips.html#env-var), 
  [Node.js](../../buildpacks/node/node-tips.html#env-var), and 
  [Ruby](../../buildpacks/ruby/ruby-tips.html#env-var).
  
  ### <a id='CF-INSTANCE-ADDR'></a>CF\_INSTANCE\_ADDR ###
  The [CF\_INSTANCE\_IP](#CF-INSTANCE-IP) and 
  [CF\_INSTANCE\_PORT](#CF-INSTANCE-PORT) of the app instance in the format 
  `IP:PORT`.
  
  `CF_INSTANCE_ADDR=1.2.3.4:5678`
  
  