anchor.diff:              p.
                 In contrast to Objects, Components are heavily dependent on content, cosmetics,
                 and function. They are recognizable pieces of user-interaction that have a particular
  -              look-and-feel. Buttons, breadcrumb lists, labels, and tags are all good examples.
  -              Components have properties belonging in the smallest 4 layers of the
  +              look-and-feel. Buttons, navigation bars, and labels are all good examples.
  +              Components have properties belonging in the smallest four layers of the
                 inverted CSS property triangle.
               p.
                 To build a fully-functional visual element on a page, you must combine
                 Objects and Components. Using just a Component class is not sufficient, because
                 you will get the skin without the structure.
               aside
  -              p.
  +              p: small.
                   In most cases, the cosmetics of a Component laregly contribute to its function.
                   As frequent as Components come, they are unusual in that
                   their semantics are derived from their presentation,
                   that is, the look-and-feel of a Component may determine its meaning in terms of usability.
                   For example, a #[code span] might not look like anything with CSS turned off,
  -                but with the right class and CSS turned on it might clearly represent a label attached
  -                to a heading or link.
  +                but with the right class and CSS turned on it might clearly represent
  +                an icon attached to a link.
                 p: small.
                   As a consequence, authors should be careful with Components because users with
                   a visual interface might have an advantage over users with, say, an audio interface.
                   Therefore authors should continue to support
  -                #[a HTML5 Microdata] and #[a ARIA roles]
  -                to accommodate the latter.
  +                SEO and accessibility best practices. Read up on
  +                #[a(href="https://developers.google.com/schemas/formats/microdata") HTML5 Microdata] and
  +                #[a(href="https://www.w3.org/WAI/intro/aria.php") ARIA roles]
  +                for more information.
               div.c-Document__Informative
                 p.
                   I have not decided yet whether to make these next sections formal. This is just an idea:
  
positive.code:               Examples include the Media Object, the Nav Abstraction, and the Island Object.
                These classes do not affect look-and-feel, only visual structure. Think back to
                the #[b Layout] and #[b Box Structure] levels of the inverted CSS property triangle above.
            section
              h4 Components
              p: strong.
  
negative.code:           dd.update: time(datetime="2015-08-20 19:06") Aug 20, 2015 #[span.tod 7:06 PM]
            dd.update: time(datetime="2015-10-03 12:13") Oct 3, 2015 #[span.tod 12:13 PM]
            dd.update: time(datetime="2016-02-03 17:47") Feb 3, 2016 #[span.tod 5:47 PM]
            dd.update: time(datetime="2016-02-03 23:14") Feb 3, 2016 #[span.tod 11:14 PM]
            dd.update
              time(datetime="2016-02-17 15:30" itemprop="dateModified") Feb 17, 2016 #[span.tod 3:30 PM]
              small.o-Textbox.c-Label.c-Label--dang.-ml-1 Latest
        section.c-Document__Draft
          h2 Introduction
  