anchor.diff:  <3> Deletes content and unassociates it from `entity`
   ====
   
  -For example, given an Entity `User`, a `UserRepository` and a `ProfilePictureStore` it
  -is possible to associate and store a profile picture for each user.
  +For example, given an Entity `User`, a `UserRepository` and a `ProfilePictureStore` it is possible to associate and
  +store a profile picture for each user.
   
   .ContentStore interface
   ====
   [source, java]
   ----
   @Entity
  +@Data
   public class User {
   	@Id
   	@GeneratedValue(strategy=GenerationType.AUTO)
  
positive.code: 
  [[content-repositories.core-concepts]]
  == Core concepts
  The central interface in the Spring Content is the `ContentStore`.  This interface provides CRUD functionality and entity association for content.  As such a ContentStore is typed to the Spring Data Entity to which content is associated, and to the type of a `@ContentId` field on that domain class.
  
  [[content-repositories.repository]]
  
  .ContentStore interface
  ====
  [source, java]
  
negative.code: ----
  ====
  
  [[content-repositories.multimodule]]
  === Using Stores with Multiple Spring Content Modules
  
  Using a unique Spring Content module in your application keeps things simple, because all Store interfaces are bound to
  the one Spring Content module.  Sometimes, applications require using more than one Spring Content
  module.  In such cases, a store definition must distinguish between storage technologies by extending one of the
  module-specific ContentStore interfaces.
  
  [[content-repositories.events]]
  === Events
  