anchor.diff:  Here nothing new to explain, if you have a function that return some kind of publisher, you can return
   it as response or send it as body like as usual.
   
  -The adaptations and coerciones are done thanks to the link:http://ffff[futura library] that has more
  -adaptations supported out of the box that which are comming with _catacumba_.
  +The adaptations and coerciones are done thanks to the
  +link:https://github.com/funcool/futura[futura library] that has more adaptations supported out of the
  +box that which are comming with _catacumba_.
   
   Let see an example:
   
  
positive.code: addopts a flexible and extensible way for make easy for the user adapt it to hes needs and hes
  abstractions.
  
  The main abstraction are defined in the link:http://ffff.com[futura library], that provides basic
  building blocks for promise like abstractions and stream abstraction.
  
  The link:http://ffff.com[futura library] instead of reinvent the wheel, is build up on existing
  implementations such as:
  
  * _JDK8 CompletableFuture_ for *promise* abstraction.
  * _Reactive Streams_ for the *stream* abstraction.
  
negative.code: === Promises
  
  Promises is an other abstraction supported out of the box in _catacumba_. It comes from the
  link:https://github.com/funcool/futura[futura library] and is build on top of JDK8 _CompletableFuture_.
  
  Sometimes, yo do not need send a chunked stream to the clien, but your "bussines logic" is defined
  with asynchronous friendly api using promises (or something similar). In this case, with _catacumba_
  