anchor.diff:  
   The following sections describe how to configure the OGM using either a properties file or via Java Configuration.
   
  -==== Using the Http driver
  -
  -The HttpDriver connects to and communicates with a Neo4j server via Http. An Http driver (or a Bolt driver) must be used if your application is running in client-server mode.
  +=== Driver Configuration
  +
  +==== Configuring the Http Driver
  +
  +The Http Driver connects to and communicates with a Neo4j server via Http. An Http Driver (or a Bolt Driver) must be used if your application is running in client-server mode.
   
   .Properties file
   ```
  
positive.code: 
  _Note: Please see the section below describing the different ways you can pass credentials to the Http Driver_
  
  ==== Using the Embedded driver
  
  The embedded driver uses an in-process instance of Neo4j and connects directly to the Neo4j database engine. There is no server involved, therefore no network overhead between your application code and the database.
  You should use the Embedded driver if you don't want to use a client-server model, or if your application is running as a Neo4j Unmanaged Extension.
  You can specify a permanent data store location to provide durability of your data after your application shuts down, or you can use an impermanent data store, which will only exist while your application is running.
  
  
negative.code:              .setURI("bolt://user:password@localhost");
  ----
  
  ==== Credentials
  
  If you are using the Bolt or Http Driver you have a number of different ways to supply credentials to the Driver Configuration.
  
  .Properties file options:
  