anchor.diff:  
   Text in paragraphs, lists, and tables should be broken into pieces that are easier to review{semantic-line-breaks}.
   Start a new line at the end of each sentence, and split sentences themselves at natural breaks between clauses.
  -
  -=== Abstracts (preamble)
  -
  -For optimum findability, add a short description using user-oriented keywords to summarize the document's purpose, task, and intent in no more than three sentences.
  -Avoid self-referential expressions and filler words, such as "This document..", "This tutorial..", and "The following.." 
  -Mentioning the benefits users gain from reading the content is also helpful.
  -
  -[IMPORTANT]
  -====
  -The first sentence of the abstract must explain the value and some benefit of the content in less than 26 words because this automatically displays on the link:https://quarkus.io/guides/[Quarkus guides homepage].
  -====
   
   === Automatic Table of Contents (TOC)
   
  
positive.code: 
  == File naming conventions
  
  Quarkus docs are stored in a fairly flat structure in an effort to make things easier to discover.
  The bulk of the file name should be some representation of its title.
  Use all lowercase letters, separate words with hyphens, and don't use symbols or special characters.
  
  
negative.code: 
  - Is this information in the right place?
  For example, if this is a reference, should some of this content be moved to a concept doc or how-to guide instead?
  - Can the content be reorganized to make it simpler to consume?
  
  See xref:{doc-guides}/doc-concepts.adoc[Quarkus documentation concepts] for more information about content types and organization.
  ====
  