anchor.diff:  
   === Debugging with prone
   
  -link:https://github.com/magnars/prone[Prone] is really awesome middleware for ring that shows
  -a beautiful and human readable stack traces when a exception is raised in your application. It is not
  -directly compatible with _catacumba_ but it is relatively easy to adapt it.
  -
  -You can see the example code here: https://github.com/funcool/catacumba/tree/master/examples/debugging
  -
  -NOTE: Obviously, if you are using the ring type of handler, you can use Prone as is, without any
  -additional adaptation. This example shows how it can be used with _catacimba_'s default handler type.
  +link:https://github.com/magnars/prone[Prone] is really awesome middleware for ring that
  +shows a beautiful and human readable stack traces when a exception is raised in your
  +application. It is not directly compatible with _catacumba_ but it is relatively easy to
  +adapt it.
  +
  +You can see the example code here:
  +https://github.com/funcool/catacumba/tree/master/examples/debugging
  +
  +NOTE: Obviously, if you are using the ring type of handler, you can use Prone as is,
  +without any additional adaptation. This example shows how it can be used with
  +_catacumba_'s default handler type.
   
   
   === Instrumentation
   
  -_Catacumba_ comes with the ability to instrument your application for taking different kinds of diagnosis,
  -such as performance, latency, etc. This example shows how it can be done.
  -
  -You can see the example code here: https://github.com/funcool/catacumba/tree/master/examples/interceptor
  +_Catacumba_ comes with the ability to instrument your application for taking different
  +kinds of diagnosis, such as performance, latency, etc. This example shows how it can be
  +done.
  +
  +You can see the example code here:
  +https://github.com/funcool/catacumba/tree/master/examples/interceptor
   
   
   
  
positive.code: 
  The possible values for the `:policy` key are: `:deny` and `:sameorigin`.
  
  WARNING: The frame-ancestors directive from the CSP Level 2 specification
  officially replaces this non-standard header.
  
  
  ==== Strict Transport Security
  
  This is a security related chain handler that adds the `Strict-Transport-Security` header to the response.
  
  HTTP Strict Transport Security (often abbreviated as HSTS) is a security feature that lets a web
  site tell browsers that it should only be communicated with using HTTPS, instead of using HTTP.
  
  Usage example:
  
  
negative.code:                [:get your-handler]]]))
  ----
  
  You can read more about that header here:
  https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security
  
  
  ==== Content Type Options
  
  This is a security related chain handler that adds the `X-Content-Type-Options` header to
  the response. It prevents resources with invalid media types being loaded as stylesheets
  or scripts.
  
  This chain handler does not have any additional parameters. Let see an example on how you
  can use it:
  