anchor.diff:  	}
   }
   ----
  +====
   
   === Experimental API
   
  -Spring Content storage modules now also offer support for a newer 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`, essentially it is a generic
  -`org.springframework.core.io.ResourceLoader`.
  +All Spring Content storage modules also now offer support for a newer *experimental* Store API based on
  +`org.springframework.core.io.Resource`.
  +
  +The base interface in this API is `Store`, a generic `org.springframework.core.io.ResourceLoader`.  When called stores
  +return instances of `org.springframework.content.commons.io.DeletableResource` allowing the full lifecycle of resources to be
  +managed through this API.
   
   .Store interface
   ====
  
positive.code: ====
  The down-side of this approach is that it does not filter events based on Entity.
  
  ==== Writing an Annotated StoreEventHandler ====
  
  Another approach is to use an annotated handler, which does filter events based on Entity.
  
  
negative.code: 
  * AfterUnsetContent
  
  ==== Writing an ApplicationListener
  
  If you wish to extend Spring Content's functionality you can subclass the abstract class `AbstractStoreEventListener` and
  override the methods that you are interested in.  When events occur Spring Content will call the appropriate methods on
  all instances of `AbstractStoreEventListener`.
  
  .AbstractContentRepositoryEventListener
  