/* Links inside FAQ answers.
   The global base rule `a { text-decoration: none }` plus the FAQ answer using a
   plain `.w-richtext` (not `.rl-text-rich-text`) meant links rendered as ordinary
   text - not obviously clickable. This restores the site's own rich-text link
   convention (var(--purple) + underline, cf. .rl-text-rich-text a) inside FAQ
   answers so they read as links. */
.c-faq-body .w-richtext a,
.c-faq-body .text-size-regular a {
  color: var(--purple);
  text-decoration: underline;
  text-underline-offset: 2px;
  font-weight: 500;
  transition: opacity 0.15s ease;
}

.c-faq-body .w-richtext a:hover,
.c-faq-body .text-size-regular a:hover {
  opacity: 0.72;
}

/* Code blocks + inline code embedded via the CMS rich-text editor, on the live
   site. Matches what the admin editor shows (WYSIWYG). */
.w-richtext pre {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  background: #0c1a2e;
  color: #eef2f7;
  padding: 16px 18px;
  border-radius: 10px;
  overflow-x: auto;
  font-size: 14px;
  line-height: 1.6;
  margin: 0 0 1.2em;
  white-space: pre-wrap;
  word-break: break-word;
}

.w-richtext pre code {
  background: none;
  padding: 0;
  color: inherit;
  font-family: inherit;
}

.w-richtext :not(pre) > code {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  background: rgba(3, 21, 48, 0.07);
  padding: 2px 6px;
  border-radius: 4px;
  font-size: 0.92em;
}