anchor.diff:  SQL Execution
   -------------
   
  -This section intends to explain the usage of sql execution part of the library.
  +This section intends to explain the usage of a sql execution part of the library.
   
   
   Connecting to database
   ~~~~~~~~~~~~~~~~~~~~~~
   
  -_surricata_ uses the concept of **context** instead of **connection** unlike any other database
  -libraries. The **context** has the resposibility of connection resource management,
  -transaction isolation flags and sql rendering dialect.
  -
  -You can create one **context** from:
  +_suricatta_, unlike other database libraries, uses a concept of *context instead of *connection*.
  +A **context** has the resposibility of jdbc connection resource management, transaction isolation
  +flags and sql rendering dialect.
  +
  +You can create it **context** from:
   
   - Plain jdbc connection.
   - link:http://niwibe.github.io/clojure.jdbc[clojure.jdbc] connection object
   - `dbspec` hash-map (same format that link:http://niwibe.github.io/clojure.jdbc/#_connecting_to_database[clojure.jdbc] accepts, including with datasource)
  +
   
   Let see some examples:
   
  
positive.code: ----
  compile "suricatta:suricatta:0.1.0-SNAPSHOT"
  ----
  
  Maven
  ~~~~~
  
negative.code: Transactions
  ~~~~~~~~~~~~
  
  The _suricatta_ library does not have support for low level transactions api, instead of it, offers a
  lightweight abstraction over complex transaction api.
  
  Let see an example:
  
  .Execute some query in a transaction block
  [source, clojure]
  