anchor.diff:  }
   --------------------------------------------
   
  +Finally since the creation if a +MutableConfiguration+ based on an empty configuration instance is so common, it is
  +possible to directlky create one:
  +
  +[source,java]
  +.Checking for mutability
  +--------------------------------------------
  +MutableConfiguration config = MutableConfigurationQuery.createMutableConfiguration("file:/home/etcd/backup-config.properties");
  +--------------------------------------------
  +
   === Configuration Changes
   
   This module does not handle detection of changes to the overall system's +Configuration+. This can be done in
  
positive.code: [source,java]
  .Checking for mutability
  --------------------------------------------
  MutableConfiguration config = ConfigChangeManager.getConfiguration().query(
      MutableConfigurationQuery.of("file:/home/etcd/backup-config.properties");
  
  if(config,isWritable("mycluster.shared.appKey")){
  
negative.code: +Mutableonfiguration+ based on a +Configuration+ and a set of target backend +URIs+. If not sure you can call
  +getSupportedURIInfo()+ to see, which kind of URI's are  currently supported.
  On top of this API you also must have the correponding implementations installed that provide the backend logic needed
  to write the changes back. This module by default supports writing back to properties and xml-properties files only.
  As an example how to write configuration entries back refer to the following snippets:
  
  [source,java]
  .Accessing and updating a mutable configuration backed by etcd
  --------------------------------------------
  MutableConfiguration config = Configuration.EMPTY.query(
      MutableConfigurationQuery.of("file:/home/etcd/backup-config.properties");
  
  config.set("newKey", "newValue")
  