anchor.diff:  
   The definitive manual on Asciidoc syntax is in the http://asciidoctor.org/docs/user-manual/[Asciidoctor User Manual]. To help people get started, however, here is a simpler cheat sheet.
   
  +== AsciiDoc vs Asciidoctor Syntax
  +We use tools from the Asciidoctor project to build the HTML and PDF versions of the Ref Guide. Asciidoctor is a Ruby port of the original AsciiDoc project, which was mostly abandoned several years ago.
  +
  +While much of the syntax between the two is the same, there are many conventions supported by Asciidoctor that did not exist in AsciiDoc. While the Asciidoctor project has tried to provide back-compatibility with the older project, that may not be true forever. For this reason, it's strongly recommended to only use the Asciidoctor User Manual as a reference for any syntax that's not described here.
  +
   == Basic syntax
   
   === Bold
  
positive.code: 
  === More Options
  
  Tables can also be given footer rows, borders, and captions. CSV or DSV can be used instead of formatting the data in pipes.
  
  More info: http://asciidoctor.org/docs/user-manual/#tables
  
  
negative.code: 
  === Headings
  
  Equal signs (`=`) are used for heading levels. Each equal sign is a level. Each page can *only* have one top level (i.e., only one section with a single `=`).
  
  Levels should be appropriately nested. During the build, validation occurs to ensure that level 3s are preceded by level 2s, level 4s are preceded by level 3s, etc. Including out-of-sequence heading levels (such as a level 3 then a level 5) will not fail the build, but will produce an error.
  
  More info: http://asciidoctor.org/docs/user-manual/#sections
  
  === Code Examples
  
  Use backticks ``` for text that should be monospaced, such as code or a class name in the body of a paragraph.
  
  More info: http://asciidoctor.org/docs/user-manual/#mono
  
  Longer code examples can be separated from text with `source` blocks. These allow defining the syntax being used so the code is properly highlighted.
  
  .Example Source Block
  [source]
  ----
  [source,xml]
  <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
  ----
  
  If your code block will include line breaks, put 4 hyphens (`----`) before and after the entire block.
  