/* ================================================================
   COMPONENT: INLINE EMPHASIS — the two prose devices
   ================================================================ */

/* Prose carries exactly TWO inline devices, and both are element-level,
   so the markup stays semantic and no emphasis class ever appears in
   the HTML (`content-design.md → Formatting`: presentation is CSS's
   job, the HTML carries plain content).

   It previously ran on four, two of which were never designed — they
   were user-agent defaults:
     · <em>   unstyled → UA italic at the inherited 350. PP Neue Montreal
              has no 350 italic cut, so it resolved to the 400 Italic
              face: the phrase came out slanted, the same ink as its own
              sentence, and a hair heavier. No contrast — a blur.
     · <strong> unstyled → UA `bolder` → 700, a black slab against 350.
     · .about__bio-highlight → --accent teal + 500 (now removed).
     · .case-em → the heading accent, bleeding the idea of "highlight"
              into a third family (serif), a fourth weight (200) and a
              second italic dialect.
   Emphasis in a paragraph is now ink and weight; italic is retired from
   body copy entirely. The serif Ultralight italic (.case-em /
   .footer__cta-em) stays a HEADING device and is unaffected — its class
   outranks the element selectors below. */


/* ── DEVICE 1 — EMPHASIS ──────────────────────────────────────────
   <em> for stress ("the questions they have there"), <strong> for a
   run-in lead-in ("Option 2 moved it to the top"). One treatment for
   both: they are the same job at two grammatical scales, and giving
   them separate looks is what produced the italic/700 split.

   Ink step + one weight step, upright.
   · Not italic — a slant in a grotesk at 16px reads as a rendering
     artefact rather than a decision.
   · Not teal — `DESIGN.md → Color` budgets the accent at 26 sites and
     calls it a labelling colour. 32 prose emphases would have made it
     the default ink of the case pages and retired it as a signal.
   · 500 is the sanctioned "deliberate UI emphasis" weight already worn
     by `.navbar__link` and `.exp-block__label` — a real Medium cut, not
     the 400 the body-copy rule forbids. */
em,
strong {
  font-style: normal;
  font-weight: var(--weight-medium);
  color: var(--text-primary);
}


/* ── DEVICE 2 — QUOTATION ─────────────────────────────────────────
   <q> — a string the interface says, or one the reader types: a query
   ("Type “payments product”"), a button label, an assistant's reply, a
   question someone brings to the screen.

   This is the use–mention distinction, and it is what most of the old
   <em> was actually doing (14 of 18 instances). It gets quote marks and
   an ink step ONLY — the weight stays wherever the host tier put it, so
   a quoted sentence still reads as prose rather than as emphasis. That
   is the whole separation from Device 1: emphasis gains weight, a
   quotation gains punctuation.

   Curly marks are named explicitly rather than left to the UA's locale
   defaults, which fall back to straight quotes in some engines. The
   single pair is declared for nesting even though nothing nests today.

   Distinct from `.case-body code`, which stays reserved for literals a
   machine reads — an endpoint path, a version string. */
q {
  quotes: '\201C' '\201D' '\2018' '\2019';
  font-style: normal;
  color: var(--text-primary);
}