anchor.diff:  == The `PersistentCacheManager`
   
   The `PersistentCacheManager` interface adds lifecycle methods to the `CacheManager` type. Those lifecycle methods enable
  -the user to completely destroy `Cache` instances a given `CacheManager` (e.g. destroy the clustered state of a `Cache` entirely,
  +the user to completely destroy `Cache` instances from a given `CacheManager` (e.g. destroy the clustered state of a `Cache` entirely,
   or remove all the data of a `Cache` from disk); as well as go into _maintenance mode_ (see <<state-transitions>> section).
   
   === `CacheManagerBuilder.with()` 's extension point
  
positive.code:  .. If it doesn't, it looks up all `ServiceFactory` it has for one that creates instances of that `Service` type.
   ... If one is found in that `ServiceFactory` repository, it uses that to create the instance
   ... If none is found, it uses the JDK's `java.util.ServiceLoader` service to load `ServiceFactory` and recheck
   .. If nothing could be found, it an Exception is thrown
  
  === Builder design guidelines
  
  
negative.code: 
  == State transitions
  
  A lifecycled instance, e.g. a `CacheManager` or a `UserManagedCache`, has three states represented by the
  `org.ehcache.Status` enum:
  
   . `UNINITIALIZED`: The instance can't be used, it probably just got instantiated or got `.close()` invoked on it;
  