anchor.diff:  
   === Driver Configuration
   
  -==== Configuring the Http Driver
  -
  -The Http Driver connects to and communicates with a Neo4j server via Http. If your application is running in client-server mode, you must use either the Http or Bolt driver.
  +==== Configuring the HTTP Driver
  +
  +The HTTP Driver connects to and communicates with a Neo4j server via HTTP. If your application is running in client-server mode, you must use either the HTTP or Bolt driver.
   
   .ogm.properties
   [source, properties]
  
positive.code: In 2.0, the `Neo4jIntegrationTestRule` class has been removed from the test-jar.
  
  In previous versions this class provided access to an underlying `GraphDatabaseService` instance, allowing you to independently verify your code was working correctly.
  However it is incompatible with the Driver interfaces in 2.0, as it always requires you to connect using Http.
  
  The recommended approach is to configure an Embedded Driver for testing as described above, although you can still use an in-process Http server if you wish (see below).
  Please note that if you're just using the Embedded Driver for your tests you do not need to include any additional test jars in your pom.
  
  === Log levels
  
negative.code: new SessionFactory(configuration, packages...);
  ----
  
  _Note: Please see the section below describing the different ways you can pass credentials to the HTTP/Bolt Drivers_
  
  ==== Configuring the Embedded Driver
  
  