anchor.diff:  }
   ----
    
  -Methods such as `dataSource()` come in additional overloaded variants which let you specify configuration options (such as pooling parameters). See the relevant Javadocs for more information.
  +Methods such as `dataSource()` come in additional overloaded variants that let you specify configuration options (such as pooling parameters). See the relevant Javadocs for more information.
   
   ==== Connecting to Generic Services
   
  -The Java configuration supports access to generic services (services which don't have a directly mapped method; this is typical for a newly-introduced service or when connecting to a private service in a private PaaS) through the `service()` method. It follows the same pattern as `dataSource()` etc. except that it allows you to supply the connector type as an additional parameter.
  +The Java configuration supports access to generic services (services which don't have a directly mapped method; this is typical for a newly-introduced service or when connecting to a private service in a private PaaS) through the `service()` method. It follows the same pattern as `dataSource()` etc.,whico except that it allows you to supply the connector type as an additional parameter.
   
   ==== Scanning for Services
   
  
positive.code: 
  === Instance ID
  
  This connector will create a UUID for use as the instance ID, as Java does not provide any portable mechanism for reliably determining hostnames or PIDs.
  
negative.code: 
  This core library provides programmatic access to application and service information. This library has no Spring dependencies and may be used in non-Spring applications.
  
  **This library requires Java 6 or newer.** It is cloud-agnostic; using the Java SPI, it supports pluggable cloud and service connectors. Support for Cloud Foundry and Heroku is available out-of-the-box, in addition to locally-provided configuration for development and testing.
  
  === Connecting to a Cloud
  
  