anchor.diff:  Each chapter must start with a single-line, level-0 section.
   The section title becomes the chapter title (also used as the TOC entry) and the section ID determines the chapter file name inside the EPUB3 archive.
   In other words, you must be explicit.
  -Asciidoctor EPUB3 will not try to guess.
  +{project-name} will not try to guess.
   If your AsciiDoc document is not structured in this way, you'll need to change it to use the {project-name} converter successfully.
   
   You can think of the master document as the spine of the book and the include directives the individual items being bound together.
  
positive.code: 
  == Converter Workflow
  
  {project-name} takes a single, logical AsciiDoc document as input and converts it to an EPUB3 publication archive (often described as a “website in a box”).
  Using the EPUB3 publication as the “digital master”, {project-name} then produces a KF8/MOBI file, the format required by Amazon Kindle.
  The conversion to KF8/MOBI is performed by sending the EPUB3 through http://www.amazon.com/gp/feature.html?docId=1000765211[KindleGen].
  
  An EPUB3 archive is typically structured with the contents of each “chapter” in a separate XHTML file.
  The converter must therefore “chunk” the source document into multiple XHTML files to put in the EPUB3 archive.
  Other converters tend to handle this task by automatically slicing up the XHTML output at predetermined heading levels.
  Asciidoctor takes a different approach.
  
  === Declaring the Spine
  
  
negative.code: 
  == Development
  
  To help develop {project-name}, or to simply test drive the development version, you need to get the source from GitHub.
  Follow the instructions below to learn how to clone the source and run it from your local copy.
  
  === Retrieve the Source Code
  