anchor.diff:  Using low level api
   ^^^^^^^^^^^^^^^^^^^
   
  -_buddy's_ signing functions live in *`buddy.crypto.signing`* namespace and it consists on four
  -functions: `sign`, `unsign`, `loads` and `dumps`.
  -
  -`sign` and `unsign` functions represents a low level api and them works with
  -strings as primary data.
  +There are four signing functions in *`buddy.crypto.signing`*: `sign`,
  +`unsign`, `loads` and `dumps`.
  +
  +`sign` and `unsign` are low level and work primarily with strings.
   
   .Unsigning previously signed data
   [source,clojure]
  
positive.code:  :handler {:or [admin-access operator-access]}}
  ----
  
  Or, allow only when a user has both roles, operator and administrator:
  
  [source,clojure]
  ----
  
negative.code: Introduction
  ------------
  
  _buddy_ is an authentication, authorization and signing library for
  Clojure.  It's designed with simplicity in mind and only depends on
  ring.
  
  
  Features/Libraries:
  
  - Modular Authentication (implemented using protocols)
  - Modular Generic Authorization
  - Regular expression based access rules system
  - Signing library
  - Password hashing library
  
  link:api/index.html[API reference documentation.]
  
  
  Philosophy
  ~~~~~~~~~
  
  Five most important rules:
  
  - Beautiful is better than ugly
  - Explicit is better than implicit
  - Simple is better than complex
  - Readability counts
  
  Project Maturity
  ----------------
  
  Since _buddy_ is a young project there can be some API breakage.
  
  
  Install
  -------
  
  This section covers installing _buddy_.
  
  
  Leiningen
  ~~~~~~~~~
  
  The simplest way to use _buddy_ in a Clojure project is by including
  it as a dependency in your *_project.clj_*:
  
  ._in project.clj_
  [source,clojure]
  ----
  [buddy "0.1.0-beta4"]
  