/* Neutralise the blog theme's global element rules inside .tc scopes.

   The design system's own reset is deliberately `:where(.tc *)` at (0,0,0)
   (see its comment: a reset should lose to any authored rule). The trade-off
   is that ANY bare element selector in the theme bundle outranks it, and
   resources/scss/generic/_base.scss ships two at (0,0,1):

     p,ul,ol,dl,hr,table,blockquote { margin-bottom: calc(...) }
     h1..h6                         { margin-bottom: calc(...); line-height: 1.33 }

   Those would add bottom margins the nav/footer never asked for — every
   .nav-links / .footer-list / .nav-s365-list is a <ul>. The theme's
   clear-bottom-margin mixin happens to cancel it wherever the list is a
   :last-child, which is true of all of them today, so this file is what
   makes the port correct by construction rather than by luck.

   LOAD ORDER IS LOAD-BEARING: this must come AFTER design-system.css and
   BEFORE nav-global.css / footer-global.css, so genuine component rules at
   the same (0,1,1) specificity still win on order — e.g.
   `.footer-cta h2 { margin: 0 auto var(--spacing-xl) }` and
   `.footer-group h4 { margin-bottom: 12px }`. The enqueue dependency chain
   in includes/enqueues.php is what guarantees it.

   line-height is intentionally NOT reset: the design system already sets it
   on .tc h2/h3/h4 and .tc .tc-heading-* at a higher specificity. */
.tc p,
.tc ul,
.tc ol,
.tc dl,
.tc hr,
.tc table,
.tc blockquote,
.tc h1,
.tc h2,
.tc h3,
.tc h4,
.tc h5,
.tc h6 {
	margin-bottom: 0;
}