anchor.diff:  include::{sourcedir31}/impl/src/test/java/org/ehcache/docs/UserManagedCaches.java[tag=persistentUserManagedCache]
   ----
   <1> Create the persistence service to be used by the cache for storing data on disk
  -<2> Pass the persistence service to the builder as well as an id for the cache - note that this will make the builder produce a more specific type: `PersistentUserManagedCache`
  +<2> Pass the persistence service to the builder as well as a name for the cache. Note that this will make the builder produce a more specific type: `PersistentUserManagedCache`
   <3> As usual, indicate here if the data should outlive the cache
  -<4> Closing the cache will not delete the data it saved on disk when marked as persistent.
  -<5> To delete the data, after closing the cache, destroy has to be explicitly invoked.
  -<6> It is also your responsibility to stop the persistence service once you are done with the cache.
  +<4> Closing the cache will not delete the data it saved on disk, since the cache is marked as persistent.
  +<5> To delete the data on disk after closing the cache, you need to invoke the `destroy` method explicitly.
  +<6> You need to stop the persistence service once you have finished using the cache.
   
   === Example with cache event listeners
   
   Cache event listeners require executor services to work.
   You will have to provide either a `CacheEventDispatcher` implementation
  -or make use of the default one by providing two executor services: one for ordered events and one for un-ordered ones.
  +or make use of the default one by providing two executor services: one for ordered events and one for unordered ones.
   
   NOTE: The ordered events executor must be single threaded to guarantee ordering.
   
  
positive.code: 
  === API extensions
  
  While a `UserManagedCache` extends `Cache`, it offers additional methods:
  
  [source,java,indent=0]
  ----
  include::{sourcedir31}/api/src/main/java/org/ehcache/UserManagedCache.java[lines=17..-1]
  ----
  
  As can be seen, these methods deal with the lifecycle of the cache and need to be called explicitly.
  
  There is also the following interface which comes into play when a user managed persistent cache is created:
  
  [source,java,indent=0]
  ----
  
negative.code: ----
  include::{sourcedir31}/impl/src/test/java/org/ehcache/docs/UserManagedCaches.java[tag=userManagedListenerCache]
  ----
  <1> Provide the `ExecutorService` for ordered and unordered event delivery.
  <2> Provide listener configuration using `CacheEventListenerConfigurationBuilder`.
  