anchor.diff:  
   ==== Configuration via YAML Files
   
  -Format of configuration file can be either JSON or YAML. For simplicity we'll focus on YAML format, but the two are interchnageable. Here is an example config file:
  +Format of configuration file can be either JSON or YAML. For simplicity we'll focus on YAML format, but the two are interchangeable. Here is an example config file:
   
   [source,yaml]
   ----
  
positive.code: 
          return configFactory
                   .config(MyFactory.class, configPrefix)
                   .createMySerice(soService);
      }
  }
  ----
  
negative.code: 
  While not strictly required, as a rule the top-level keys in the file belong to configuration objects of individual modules. In the example above "log" subtree configures `bootique-logback` module, while "jetty" subtree configures `bootique-jetty`. For standard modules refer to module-specific documentation on the structure of the supported configuration (or run your app `-H` flag to print supported config to the console). Here we'll discuss how to build your own configuration-aware module.
  
  Bootique allows each Module to read its specific configuration subtree as an object of the type defined in the Module. Very often such an object is written as a factory that contains a bunch of setters for configuration properties, and a factory method to produce some "service" that a Module is interested in. Here is an example factory:
  
  [source,java]
  ----
  