/* ==========================================================================
   GOOGLE ADS MANAGEMENT — A SECTION HEADING FOR THE FAQ, AND ITS CLOSE
   --------------------------------------------------------------------------
   Built as /doctor/gads-faq-head-r6q.html, 2026-09-09.

   THIS FILE DOES NOT TOUCH THE FAQ COMPONENT.

   Not one rule here selects .gfaq-title, .gfaq-box, .gfaq-scroll, .gfaq-item,
   .gfaq-q, .gfaq-a or anything inside them. The title plate and its notch, the
   -30px pull that drives the plate into the box's top border, the 10px
   bracket, the rounded right corners, the 400px inner scroll, the card, the
   Q/A squares, the +/- marker, the open transition and every measurement in
   gads-pkg-faq/gfaq.css are exactly as they were. The accordion markup and
   gfaq.js are untouched. `_r6qqa.py` proves it: it reads the computed style of
   every one of those elements off the live page and off this one and requires
   them to be identical, property for property.

   Two things are added, and they are both OUTSIDE the component.

   1 · A SECTION HEADING ABOVE IT.  The FAQ was the one section on the page
       with no section heading — it opened straight onto its own component.
       It now gets the same heading the section directly above it has:
       #pricing's centred eyebrow, headline and supporting line. Centred,
       because that is what that heading is. The values are read from
       gads-pkg-faq/pkg.css's .pricing-header / .pricing-badge / .pricing-h2 /
       .pricing-sub, so the two headings are the same object and the FAQ reads
       as the next section rather than as a loose box.

   2 · AN ENDING BEFORE THE FOOTER.  site/shelf.css part 4 takes the bottom
       edge and the aisle off the last block on every page, so the page
       "closes rather than opens one more block". That works where the last
       block changes colour at the seam. It does not here: #gfaq is --ground
       #F4F7FC and #sfoot is --ground #F4F7FC, so with no aisle and no bottom
       edge the FAQ and the footer were one uninterrupted surface. The FAQ
       takes back the ordinary block ending — its bottom edge, then the aisle
       of floor white, then the footer's own edge — which is the boundary the
       reader has already crossed six times further up this page. Scoped to
       #gfaq, so no other page's ending moves.
   ========================================================================== */


/* ── 1 · the section heading ────────────────────────────────────────────────
   .gfaq-shead is new markup that sits BEFORE .gfaq-title in .gfaq-wrap. It is
   a sibling of the component, never a wrapper around it, so the component's
   own box model, its plate, its notch and its -30px pull are all untouched.

   Centred, because the site's major section titles are centred and measuring
   them says so: on the homepage Industries, Success Stories, Client Proof,
   Why Choose Us and About Us are all centred; on about-us.html Our Story and
   Our Capabilities are; and on THIS page #pricing — the section directly
   above the FAQ — is centred at L58 R58. The left-aligned ones are the
   detail-page headers (#gads-services, #w8-system, #wcu-ga), not the major
   titles.

   The three parts are the site's own, not new inventions:
     · the eyebrow is .k-eyebrow, styled entirely by site/ds.css — mono 11px,
       .24em, uppercase, --ink-2 — so it is the same object as the eyebrow on
       every other page and moves when that file moves. Nothing is written for
       it here except the gap under it.
     · the headline takes --ds-h2, ds.css's section-headline token. That is
       the same clamp, line-height and tracking vm.css gives #w8-system and
       #wcu-ga on this page (--vm-h2 and --ds-h2 are the same three values),
       so it lands at exactly their size.
     · the supporting line is .k-sub held to 52ch and centred, which is
       ds.css's own written rule for a centred header: "the homepage holds its
       sub to 52ch so a centred header stays a block and not a banner."
   ========================================================================= */
#gfaq .gfaq-shead{
  text-align: center;
  /* bridge.css puts line-height 1.5 on #gfaq to reproduce the reference
     page's reboot for the question cards. Inherited, it makes an 11px
     eyebrow a 16.5px box and shifts the gap under it by 3px against the same
     eyebrow on every other page. The cards keep the reboot; the heading takes
     the page's own default, which is `normal`. */
  line-height: normal;
  /* the distance from this heading to the component below it. The component
     begins at its title plate — the plate is what is pulled 30px down into
     the box — so this is measured to the plate and the notch geometry under
     it is not disturbed. */
  margin: 0 0 clamp(24px, 2.6vw, 34px);
}

/* ds.css leaves .k-eyebrow at margin:0 and lets the headline's own top margin
   do the spacing. Every art-directed header on the site sets the gap instead:
   contact-us #answers 14px, #w8-system and #wcu-ga clamp(12px,1.2vw,18px),
   #gads-services clamp(11px,1.1vw,15px). The middle one is taken here — this
   is a major section title, not a sub-header. It collapses with the
   headline's own margin rather than adding to it. */
#gfaq .gfaq-shead .k-eyebrow{ margin-bottom: clamp(12px, 1.2vw, 18px); }

#gfaq .gfaq-shead .gfaq-sh2{
  margin: 0;
  font-family: var(--sans);
  font-size: var(--ds-h2);
  font-weight: 800;
  letter-spacing: var(--ds-h2-ls);
  line-height: var(--ds-h2-lh);
  color: var(--ink);
  text-wrap: balance;
}

/* .k-sub is ds.css's; the two lines here are the centring and the reboot.
   gads-pkg-faq/bridge.css gives every <p> inside #gfaq a 1rem bottom margin,
   and this is the last thing in the heading — left alone it would push the
   component down by an em nobody asked for. */
#gfaq .gfaq-shead .k-sub{
  max-width: 52ch;
  margin-left: auto;
  margin-right: auto;
  margin-bottom: 0;
}


/* ── 2 · the close ──────────────────────────────────────────────────────────
   0,1,0 against site/shelf.css's own 0,1,0, and later in the document, so it
   settles both that file's base rule and its <=760px restatement without
   needing a media query of its own or !important. --sh-aisle and --sh-pb are
   shelf.css's tokens and still shrink with it on a phone. */
#gfaq{
  /* a little more floor under the component than a mid-page block takes: the
     box's 10px bracket is heavy, and this is the page's last breath before
     the footer. 46px -> 58px at 1440, 32px -> 40px at 390. */
  padding-bottom: clamp(40px, 4vw, 58px);
  border-bottom: 1px solid var(--sh-edge);
  margin-bottom: var(--sh-aisle);
}
