anchor.diff:  ===== Associations
   
   An association, bidirectional or unidirectional, is always mapped using one relationship.
  -This is possible because in Neo4j relationships can be navigate in both directions.
  -
  -The type of the relationships depends from the type of association, but in general, it is the corresponding name of the table
  +This is possible because in Neo4j relationships can be navigated in both directions.
  +
  +The name of the relationships depends on the type of association, but in general, it is the corresponding name of the table
   containing the association.
   
   [WARNING]
   ====
  -Unidirectional many to one association are currently an exception to this rule.
  +Unidirectional many-to-one associations are currently an exception to this rule.
   At the moment, in this scenario, there won't be a relationship.
   ====
   
  -The id of the entities connected to the relationship are stored as properties.
  +The ids of the entities connected to the relationship are stored as properties.
   In the following examples we omitted the properties containing the id for simplicity and because we are planning to remove them
   in the future.
   
  
positive.code: 
  Neo4j operations can be executed only inside a transaction.
  Unless a different +org.hibernate.engine.transaction.jta.platform.spi.JtaPlatform+ is specified, OGM will use a default one to integrate with the Neo4j transaction mechanism.
  This means that you can start and commit transaction using the hibernate session.
  
  The drawback is that it is not possible to use Hibernate OGM and Neo4j inside a container.
  
  
  .Example of starting and committing transactions
  ====
  
negative.code: 
  ===== Auto Generated Values
  
  Hibernate OGM only supports the table generation strategy in Neo4j.
  A sequence is represented by a node like in the following example:
  
  .Example of a sequence using cypher
  