anchor.diff:  * Build upon abstractions with simplicity and extensibility in mind.
   * Provide built in declarative style routing.
   * Remain unopinionated and versatile.
  -* Come with backpressure support out of the box.
  +* Come with back pressure support out of the box.
   
   _catacumba_ is not designed:
   
   * To be a fully integrated full stack solution like Immutant or Pedestal.
  -* To provide an opinionated way to structure your "bussines logic"
  +* To provide an opinionated way to structure your "business logic"
   * To provide all possible features that you might need.
   * To be a low level, ring based library.
   
  -The result of this research project is a powerfull, lightweight, and fully
  +The result of this research project is a powerful, lightweight, and fully
   extensible asynchronous web toolkit built on top of existing and well designed
   components such as Ratpack and Netty.
   
  
positive.code: _Catacumba_ server can be configured to use TLS (commonly known as SSL). The process
  is pretty simple but it requires to have a proper key and certificate.
  
  The first thinkg that you should care about is that _catacumba_ is built on jvm
  that the default ssl certificate/key format used by nginx/apache it isn't compatible
  but is very easy create a compatible file using the `openssl` commandline.
  
  Having a key and the certificate, just execute this command:
  
  
negative.code: 
  Is a low level handler type that works in a cps style (in other words, they works
  with callbacks). This is not general purpose handler type but you maybe found it
  useful for integrate catacumba with other scenarios that it is not initially
  designed to work.
  
  This is the aspect ot the cps style handler:
  