anchor.diff:  
   We plan on switching to a more elegant testing framework in the future, such as RSpec or Cucumber, in order to make the tests more clear and robust.
   
  +=== Running Asciidoctor in Development Mode
  +
  +Asciidoctor is designed so that you can run the script directly out of the cloned repository.
  +Simply execute the `asciidoctor` command directly (referencing it either by relative or absolute path).
  +There's no need to install it using the `gem` command first.
  +
  +For example, to convert the README file, switch to the root of the project and run:
  +
  + $ ./bin/asciidoctor README.adoc
  +
  +IMPORTANT: You'll need to make sure you reference the correct relative path to the `asciidoctor` command.
  +
  +If you want to be able to execute the `asciidoctor` command from any directory without worrying about the relative (or absolute) path, you can setup the following Bash alias:
  +
  + alias asciidoctor-dev="/path/to/asciidoctor/bin/asciidoctor"
  +
  +Now you can execute the `asciidoctor` command from any folder as follows:
  +
  + $ asciidoctor-dev README.adoc
  +
   == Supporting Additional Ruby Versions
   
   If you would like this library to support another Ruby version, you may volunteer to be a maintainer.
  
positive.code: . Add documentation for your feature or bug fix.
  . If your changes are not 100% documented, go back to step 7.
  . Add, commit, and push your changes.
  . {pr-help-uri}[Submit a pull request].
  
  For ideas about how to use pull requests, see the post http://blog.quickpeople.co.uk/2013/07/10/useful-github-patterns[Useful GitHub Patterns].
  
  
negative.code: 
  == Submitting a Pull Request
  
  . {uri-fork-help}[Fork the repository].
  . Run `bundle install` to install dependencies.
  . {uri-branch-help}[Create a topic branch].
  . Add tests for your unimplemented feature or bug fix. (See <<writing-and-executing-tests>>)
  . Run `bundle exec rake` to run the tests.
  If your tests pass, return to step 3.
  