anchor.diff:  
    $ bundle
   
  -To upgrade the gem, set the new version in the Gemfile and run `bundle` again.
  +To upgrade the gem, specify the new version in the Gemfile and run `bundle` again.
   Using `bundle update` is not recommended as it will also update other gems, which may not be the desired result.
   
   === (c) Linux package managers
  
positive.code: == AsciiDoc Processing
  
  Asciidoctor reads and parses text written in the AsciiDoc syntax, then feeds the parse tree into a set of built-in templates to produce HTML5, DocBook 5 (or 4.5).
  You have the option of writing your own converter or providing {tilt-uri}[Tilt]-supported templates to customize the generated output or produce alternative formats.
  
  NOTE: Asciidoctor is a drop-in replacement for the original AsciiDoc Python processor (`asciidoc.py`).
  The Asciidoctor test suite has {tests-uri}[> 1,500 tests] to ensure compatibility with the AsciiDoc syntax.
  
  In addition to the standard AsciiDoc syntax, Asciidoctor recognizes additional markup and formatting options, such as font-based icons (e.g., [x-]`icon:fire[]`) and UI elements (e.g., [x-]`button:[Save]`).
  Asciidoctor also offers a modern, responsive theme based on {foundation-uri}[Foundation] to style the HTML5 output.
  
  == Requirements
  
  Asciidoctor works on Linux, OSX (Mac) and Windows and requires one of the following implementations of {ruby-uri}[Ruby]:
  
  * MRI (Ruby 1.8.7, 1.9.3, 2.0.0 & 2.1.2)
  * JRuby 1.7 (Ruby 1.8 and 1.9 modes)
  
negative.code: html = document.convert
  ----
  
  Keep in mind, if you don't like the output Asciidoctor produces, _you can change it!_
  Asciidoctor supports custom {uri-tilt}[Tilt]-supported templates, which to allow you customize the output piecemeal, or custom converters, which give you 100% control over the output.
  
  For more information about how to use the API or to customize the output, see the {uri-user-manual}[user manual].
  
  == Contributing
  
  In the spirit of {uri-freesoftware}[free software], _everyone_ is encouraged to help improve this project.
  If you discover errors or omissions in the source code, documentation, or website content, please don't hesitate to submit an issue or open a pull request with a fix.
  New contributors are always welcome!
  
  Here are some ways *you* can contribute:
  
  * by using prerelease (alpha, beta or preview) versions
  * by reporting bugs
  * by suggesting new features
  * by writing or editing documentation
  