anchor.diff:  This backend is almost identical to the previous one (JWS).
   
   The main difference is that the backend uses JWE (Json Web Encryption) instead of JWS
  -(Json Web Signature) and it has the advantage that the content of token is encrypted
  +(Json Web Signature) and it has the advantage that the content of the token is encrypted
   instead of simply signed. This is useful when token may contain some additional user
  -information that can not be public.
  -
  -It will look similar to the previous (jws) example but instead using jwe with asymetric
  +information that should not be public.
  +
  +It will look similar to the previous (jws) example but instead using jwe with asymmetric
   key encryption algorithm:
   
   [source, clojure]
  
positive.code: The access rules system is another part of authorization. It consists of matching
  an url to specific access rules logic.
  
  The access rules consists of an ordered list. This contains mappings between urls
  and rule handlers using link:https://github.com/weavejester/clout[clout] url
  matching syntax or regular expressions.
  
  
negative.code: ----
  
  The `authenticated?` is a predicate function that receives a request and returns
  `true` if it has been authenticated by one of the _buddy-auth_ backends or `false`
  otherwise
  
  Later, http-basic authentication backend requires a function with the
  responsibility of authenticating the incoming request. Let's see how we can do it:
  
  [source, clojure]
  ----
  