anchor.diff:  
   === Add additional extensions
   
  -django-jinja, by default set up a great amount of extensions to make your experience
  +django-jinja, by default sets up a great amount of extensions to make your experience
   using jinja in django painless. But if you want to add more extesions, you can do it
  -using `extensions` entry on backend options:
  +using the `extensions` entry of the backend options:
   
   [source, python]
   ----
  
positive.code: }
  ----
  
  As usual, this is a default list of context processors and you can forget
  setup them if you do not have own. Furthermore, it is now not recommended way
  to setup variables in the context and the purpose of its existence is a help
  for migrations.
  
  [NOTE]
  ====
  Take care that django (1.8.x and 1.9.x) lives with backward compatibility with
  old template api and this has its own tradeoffs. If you found you using functions
  like `render_to_string` or `render_to_response` from django, do not forget pass
  request parameter in order to make context processors work.
  ====
  
  
negative.code: - I18n subsystem adapted for Jinja2 (makemessages now collects messages from
    Jinja templates)
  - Compatible with python2 and python3 using same codebase.
  - jinja2 bytecode cache adapted for using django's cache subsystem.
  - Support for django context processors.
  
  
  