anchor.diff:  ### <a id='PORT'></a>PORT ###
   
   The port on which the application should listen for requests.
  -The Cloud Foundry runtime allocates a port dynamically for each instance of the 
  -application, so code that obtains or uses the application port should refer to 
  +The Cloud Foundry runtime allocates a port dynamically for each instance of the
  +application, so code that obtains or uses the application port should refer to
   it using the `PORT` environment variable.
   
   `PORT=61857`
   
   ### <a id='PWD'></a>PWD ###
  -Identifies the present working directory, where the buildpack that processed 
  +Identifies the present working directory, where the buildpack that processed
   the application ran.
   
   `PWD=/home/vcap/app`
  
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 different from 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.
  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 are 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='VCAP-SERVICES'></a>VCAP\_SERVICES ###
  
  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
  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.
  