._wrapper_aun8z_1 {
  display: block;
}

/* The passage's own trailing margin sat between it and its mark, so on a heading or a multi-
   paragraph block the mark drifted far enough away to stop reading as attached to anything. Both
   levels are flattened: the block the caller rendered, and the last element inside it, since a
   Markdown body puts its margin on the final <p> rather than on the wrapper. The spacing is then
   reinstated below the mark, so the pair as a whole still separates from what follows. */
._wrapper_aun8z_1 > :not(._mark_aun8z_10),
._wrapper_aun8z_1 > :not(._mark_aun8z_10) > :last-child {
  margin-bottom: 0;
}

/* Below the passage, in the flow, rather than floating over its corner. Overlaying saved a line of
   height and cost readability: on a heading the mark landed on top of the words, and two marks
   near each other could collide. */
._mark_aun8z_10 {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 8px;
  /* Tight to the text above, normal paragraph spacing below. */
  margin: 3px 0 1.35em;
}

/* The same blue chip the editor uses for provenance. A reader and an organizer are being told the
   same fact, and one visual language for it means neither has to learn a second one. It reads as
   quiet at this size without being faded: the earlier opacity made it look disabled and cost
   contrast for anyone who needed it most. */
._chip_aun8z_31 {
  display: inline-flex;
  align-items: center;
  padding: 2px 8px;
  border-radius: 999px;
  background: #e3f2fd;
  color: #0d47a1;
  font-size: 0.6875rem;
  font-weight: 500;
  line-height: 1.6;
  white-space: nowrap;
}

._toggle_aun8z_44 {
  padding: 0;
  border: 0;
  background: none;
  color: var(--color-text-muted, #6b6b6b);
  font: inherit;
  font-size: 0.6875rem;
  text-decoration: underline;
  cursor: pointer;
  white-space: nowrap;
}

._toggle_aun8z_44:hover {
  color: var(--color-text, #111);
}