anchor.diff:  @Configuration
   public class ContentStoreConfiguration {
   
  -  @Bean
  -  ExampeAnnotatedEventHandler exampleEventHandler() {
  -    return new ExampeAnnotatedEventHandler();
  -  }
  -}
  -----
  -====
  -
  -==== Experimental API ====
  -
  -Some Spring Content modules offer support for a new experimental Store API.  This API offers lower-level management of content that can be used to satisfy a wider set of content-related use cases.
  -
  -The base interface in this API is the `Store`, a generic version of a `org.springframework.core.io.ResourceLoader` that returns `org.springframework.content.commons.io.DeletableResource`s allowing them to be fully-managed.
  -
  -.Store interface
  -====
  -[source, java]
  -----
  -public interface Store<ID extends Serializable> {
  -
  -	Resource getResource(ID id);
  -	
  -}
  -----
  -====
  -
  -Derived from the `Store` is a second interface `AssociativeStore` allowing Resources returned by `Store`s to be associated with Spring Data Entity objects.
  -
  -.AssociativeStore interface
  -====
  -[source, java]
  -----
  -public interface AssociativeStore<S, SID extends Serializable> extends Store<SID> {
  -	
  -	void associate(S entity, SID id);
  -	void unassociate(S entity);
  -
  +	@Bean
  +	ExampeAnnotatedEventHandler exampleEventHandler() {
  +		return new ExampeAnnotatedEventHandler();
  +	}
   }
   ----
   ====
   
   [[content-repositories.search]]
   === Search
  -Applications that handle files and other media usually have search capabilities allowing content to be found by looking inside of it. 
  +Applications that handle files and other media usually have search capabilities allowing content to be found by looking inside of it.
   
   Content stores can therefore optionally be made searchable by extending the `Searchable<CID>` interface.
   
  
positive.code: ----
  public interface Renderable<E> {
  
  	InputStream getRendition(E entity, String mimeType); 
  }
  ----
  Returns a `mimeType` rendition of the content associated with `entity`.
  
negative.code: [[content-repositories]]
  = Working with Spring Stores
  
  The goal of the Spring Content is to make it easy to create applications that manage content such as documents, images and video by significantly reducing the amount of boilerplate code that the Developer must create for themselves.  The Developer just provides interfaces that declare the intent for content-related functionality.  Based on these and on class-path dependencies Spring Content is then able to inject storage-specific implementations.
  
  [IMPORTANT]
  ====
  This chapter explains the core concepts and interfaces for Spring Content. The examples in this chapter use Java configuration and code samples for the Spring Content S3 module.  Adapt the Java configuration and the types to be extended to the equivalents for the particular Spring Content module that you are using.
  ====
  
  [[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]]
  
  