anchor.diff:                \*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*/
             section
               h1 Direct CSS Imports
  -            p.
  -              These are pure-CSS statements of the form #[code @import url('normalize.css');].
  -              When a less stylesheet compiles, these get moved to the top (above comments and everything else),
  -              and remain verbatim.
  +            p These are pure-CSS statements of the following form.
  +            figure: pre @import url('normalize.css');
  +            p.
  +              In a Less file, upon compilation, these lines get moved to the top of the output file
  +              and remain verbatim, which means no parsing is done (unlike Less imports mentioned below).
  +            p
  +              strong Remember:
  +              |  If you&rsquo;re writing a pure CSS file, put these statments above the metadata block.
               p.
                 Though these imports make coding CSS easier, they are not recommended; instead,
                 use #[code &lt;link rel="stylesheet" href="normalize.css"/&gt;] at the top of each
  -              document that uses your css file.
  +              document that uses the would-be-importing stylesheet.
             section
               h1 Filename
  -            p Put the filename in a comment block after any CSS imports.
  -            figure: pre.
  -              /*================================*\
  -                  conf.less
  -              \*================================*/
  +            p.
  +              Put the filename in a comment block after the meta block and any CSS imports.
  +              The filename for the main stylesheet has a slightly different style than that for the partials.
  +            figure
  +              figcaption main stylesheet filename:
  +              pre.
  +                /*================================*\
  +                    conf.less
  +                \*================================*/
  +            figure
  +              figcaption partial stylesheet filename (prepended by repo name for clarity):
  +              pre.
  +                /*################################*\
  +                    conf  |  base.less
  +                \*################################*/
             section
               h1 Less Imports
               p.
                 You can use #[a(href="http://lesscss.org/features/#import-directives-feature") Less imports],
                 reference or inline, to import partials into a main stylesheet.
  -              These go after the filename comment block, because any imported code should be
  -              injected afterward.
  +              These go after the filename comment block, because any code injected inline
  +              should be done so underneath.
             section
               h1 Table of Contents
  -            p.
  -              A table of contents really helps ...
               p.
                 There are two types of table-of-contents. The first type is used in the main stylesheet
                 to describe each imported partial. The second may be used within a partial stylesheet
                 to delineate its sections and subsections.
  +            p.
  +              A table of contents really helps keep your codebase organized and proides a catalog
  +              of all the pieces of a project or file. While upkeep maintenance takes some time,
  +              this can be seen as an investment for a lot of time and confusion saved later on.
               figure: pre.
                 /*
                  * # CONTENTS
  
positive.code:                * dev.css.......................development mode: fixes for imported stylesheets
                 *
                 * ## BASE
                 * sections......................secioning content and section-related elements
                 * grouping......................grouping content
                 * text..........................text-level and inline elements
                 *
                 * ## OBJECTS
                 * Box...........................[description]
                 * Textbox.......................[description]
                 *
                 * ## COMPONENTS
                 * ### TYPOGRAPHIC
                 * Document......................[description]
                 * Lede..........................[description]
                 * Caption.......................[description]
                 * Pullquote.....................[description]
                 *
                 * ### UI (USER INTERACTION)
                 * Alert.........................[description]
                 * Label.........................[description]
                 *
                 * ## OVERRIDES
                 * atoms.css.....................project-specific one-liners
                 * shame.css.....................hacks and styles I haven’t figured out where to put yet
                 */
              p.
                Within partials, keep sections at the top level
                and sub-sections to one level deeper. Known as the #[i Inception rule],
                keep sections to 2 levels deep; 3 levels is too much. If you need this kind of
                complexity, it&rsquo;s better to split up the stylesheet into smaller files.
              figure: pre.
                //Table Of Contents
  
negative.code:               //  ## Font size and line height
                //  ## Padding, margin, border
            section
              h1 Section and Subsection Headings
              p.
                Use comment blocks to begin and end sections and subsections with headings.
                Section headings are ALL CAPS and preceded by a single hash, while
                subsection headings are Title case and follow two hashes.
                Only subsections are indented.
              figure: pre.
                /*++++++++++++++++++++++++++++++++*\
                    # HORIZONTAL GRID
                \*++++++++++++++++++++++++++++++++*/
                ... code goes here ...
                  /*--------------------------------*\
                      ## Lines and units
                  \*--------------------------------*/
                  ... code goes here ...
                  //---- end ## Lines and units ----//
                //++++ end # HORIZONTAL GRID ++++//
  