anchor.diff:            li #[code body]    #[+tag('Sectioning Root','body-sectioning-root')]
             li #[code section] #[+tag('Sectioning Content','section-sectioning-content')]
             li #[code article] #[+tag('Sectioning Content','article-sectioning-content')]
  -          li #[code aside]   #[+tag('Sectioning Content','aside-sectioning-content')]
  +          li: section.c-Document__Draft
  +            h3 #[code aside]
  +            p: +tag('Sectioning Content','aside-sectioning-content')
  +            p Two guidelines for using #[code aside]:
  +            ul
  +              li.
  +                The normal flow of the document must not be disturbed if the aside were removed,
  +                so the reader should be able to completely skip it without missing a beat.
  +              li.
  +                The aside itself must make sense isolated and out of context, so reading the aside
  +                all by itself should make sense.
             li #[code nav]     #[+tag('Sectioning Content','nav-sectioning-content')]
             li #[code main]
  -          li #[code header] #[sup: +reference('header')]
  -          li #[code footer] #[sup: +reference('footer')]
  +          li: section.c-Document__Draft
  +            h3 #[code header] &amp; #[code footer]
  +            p.
  +              The #[code header] element should contain introductory content, data about
  +              #[em the section itself], such as headings, a table of contents, a list of authors/editors,
  +              time written/published/updated, and related tags.
  +            p.
  +              The #[code footer] element should contain secondary information, data about
  +              #[em the content in the section], such as copyright information, contact information,
  +              related links or references, and footnotes.
  +            footer: p: small Neither element may contain any #[code header] or #[code footer] descendants.
             li #[code h1]&ndash;#[code h6] #[+tag('Phrasing Content Model','hn-phrasing-content-model')]
             li #[code address] #[sup: +reference('address')]
         section#grouping-content
  
positive.code:         ul
            li #[code fieldset] #[+tag('Sectioning Root','fieldset-sectioning-root')]
            li #[code legend] #[+tag('Phrasing Content Model','legend-phrasing-content-model')]
            li #[code input] #[+tag('Nothing Content Model','input-nothing-content-model')]
            li #[code label] #[+tag('Phrasing Content Model','label-phrasing-content-model')] #[sup: +reference('label')]
        section#interactive-content
          h2 Interactive Content
  
negative.code:             small All text-level elements have the Phrasing Content Model unless otherwise specified.
            li
              sup
                +footnote('li')
                +footnote('dd')
              | The #[code li] and #[code dd] Elements seem like they should be Sectioning Roots
  