anchor.diff:  
   == Introduction
   
  -_Catacumba_ is an asynchronous and non-blocking web toolkit for Clojure built on top
  -of ratpack and netty and with design influenced by ring, pedestal and ratpack.
  +_Catacumba_ is an asynchronous or non-blocking web toolkit for Clojure built on top
  +of ratpack and netty drawing inspiration from ring, pedestal and ratpack.
   
   
   === Rationale
   
  -I start writting this library as a research project to provide a simple, non
  -obstructive (a la ring) but without constrains of the existing spec (ring spec),
  -web toolkit for build asynchronous and non-blocking web services.
  -
  -Here a incomplete list of things that _catacumba_ aims to archieve:
  -
  -* Have a flexible and extensible way to setup different kind of handlers
  +I started writting this library as a research project to provide a simple, non
  +obstructive (a la ring) without the constraints of the existing ring spec.
  +The aim is to create a web toolkit for building asynchronous web services.
  +
  +Here is an incomplete list of things that _catacumba_ aims to achieve:
  +
  +* Allow different types of handlers by being flexible and extensible 
   * Provide a simple and lightweight approach for defining asynchronous web services
  -  with support for different abstractions, such as promises, futures, core.async,
  -  manifold, reactive-streams, ...
  -* Build almost everything up on abstractions for simple and easy extensibility.
  -* Provide a built-in, data-based routing.
  -* To be flexible and not very opinionated.
  -* Have backpressure support out of the box.
  -
  -And _catacumba_ goals are not:
  -
  -* To be a fully integrated full stack solution like immutant or pedestal.
  +  with support for different abstractions such as promises, futures, core.async,
  +  manifold, reactive-streams, etc...
  +* 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.
  +
  +_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 all possible features that you might need.
   * To be a low level, ring based library.
   
  -The result of this research project is an powerfull, lightweight, and fully
  +The result of this research project is a powerfull, lightweight, and fully
   extensible asynchronous web toolkit built on top of existing and well designed
  -components such as Ratpack, Netty.
  +components such as Ratpack and Netty.
   
   
   === Project Maturity
   
  -Since _catacumba_ is a young project there can be some API breakage.
  +Since _catacumba_ is a young project there may be some API breakage.
   
   
   === Install
   
  -The simplest way to use _catacumba_ in a clojure project, is by including it in the
  +The simplest way to use _catacumba_ in a clojure project is by including it in the
   dependency vector on your *_project.clj_* file:
   
   [source,clojure]
  
positive.code: 
  === Running the server
  
  Now having defined the simple, hello world handler, it is time to run it. To do it,
  import the `run-server` function from `catacumba.core` ns and execute it with
  handler as first parameter:
  
  [source, clojure]
  ----
  
negative.code:   (http/ok "Hello World"))
  ----
  
  The response types exposed under the `catacumba.http` namespace also accept
  additional parameters such as response headers:
  
  [source, clojure]
  ----
  