anchor.diff:  === Input examples
   
   DocTest provides a collection of the reference input examples that should be suitable for most backends.
  -You can find them in link:data/examples/asciidoc[].footnote:[Since GitHub implicitly renders them as a plain AsciiDoc, you must view a Raw source if you want to see what’s going on here.]
  +You can find them in link:data/examples/asciidoc[].footnote:[Since GitHub implicitly renders them as a plain AsciiDoc, you must view a Raw source if you want to see what’s going on there.]
   There are a lot of test examples and some of them may not be relevant to your backend — that’s okay, when some output example is not found, it’s marked as skipped in test.
   
   You can also write your own input examples and use them together with those provided (or replace them).
  
positive.code: === Generate examples
  
  Writing examples of an expected output for all the input examples from scratch is quite a chore.
  Therefore DocTest provides a generator, so when you have at least partially working Asciidoctor _backend_ (converter or set of templates), you can pass the input examples through it and generate your output examples.
  Then you should verify them and modify if needed.
  
  Assume that you have defined the generator Rake task named `:generator` (see <<setup-doctest>>).
  
negative.code: 
  == Examples
  
  Test _example_ is just a document fragment in AsciiDoc syntax (a reference input), or the backend’s target syntax (an expected output).
  Example should consider one case of the generated output, i.e. it should reflect one code branch in a converter or template.
  Examples are grouped in _examples suites_. Each suite focuses on one block or inline element — more precisely Asciidoctor’s AST node (paragraph, table, anchor, footnote…).
  
  Examples suite is a text file named similar to Asciidoctor templates, i.e. the AST node name with an extension according to syntax, for example `block_table.adoc`, `block_table.html`. See below for a list of the AST nodes.
  Individual examples in the suite are separated by a special header with the name of the example, an optional description and options.
  
  Each example is identified by its name and the suite name like this: `{suite_name}:{example_name}` (e.g. `block_table:with_title`).
  Input and output examples are paired — for every input example there should be an output example with the same identifier.
  When you <<run-tests, run tests>>, the input example is converted using the tested backend (or templates) and its actual output is compared with the expected output example.
  
  [horizontal]
  .List of Asciidoctor’s AST nodes
  