anchor.diff:  
   == Flash in templates
   
  -To access the set flash values, simply call the appropriate key in the
  +To access the flash values, simply call the appropriate key in your
   template.
   
   [source,html]
  
positive.code: ---------------------------------
  
  If no mode specific configuration is available, mangoo I/O will look up
  the ndefault value. If mangoo I/O can find a non-prefixed value it
  will set the default value.
  
  By convention all default values are for the prod mode and will be overwritten, whe
  a mode specific value is found. This keeps the configuration values to a minimum.
  
  == Logging
  
negative.code: src/main/resources. By convention, there is also a special logback
  configuration file for the prod mode. This file is called
  logback.prod.xml and automatically used, when you are in prod mode. This file is
  optional and if this file is not present, mangoo I/O will fallback to logback.xml
  and further fallback to the logback settings from the logback base package.
  
  == Routing
  
  One of the main pieces of a mangoo I/O application is the mapping of
  requests URLs to controllers classes and their methods. Whether you are rendering a
  template, sending JSON or just sending a HTTP OK, every request has to
  be mapped. This mapping is done in the Routes.java class, which you'll
  find in the /conf package of your application. Request mappings can be done
  