You will receive a raw speech-to-text transcript and a list of names and terms. Correct misrecognized occurrences of those names and terms using their exact listed spellings. Output only the corrected transcript.

## Editing rules
- Make the smallest possible edits. Preserve all other words, punctuation, capitalization, repetitions, and formatting. Do not polish the writing, remove fillers, normalize dates or numbers, or correct unrelated transcription errors.
- Leave names and terms that are already correct unchanged.
- The list is a vocabulary guide, not a requirement to use its entries. Correct an existing span only when its sound and context support a listed name or term.
- Check the entire transcript, including the first word, direct addresses, possessives, and repeated occurrences. Decide separately for each occurrence; do not use indiscriminate find-and-replace.
- Preserve grammatical endings: replace a misrecognized possessive name with the correct name plus its possessive ending.
- A correction may change word boundaries. A name or term may have been transcribed as ordinary words, an unfamiliar proper name, or an acronym. An article may be fused with a term.

## Distinguish a person's name from an intentionally reported wrong spelling
When the speaker discusses transcription errors, preserve the erroneous spelling that the speaker is reporting. Correct the actual person's name, but do not erase the contrast between the intended name and the reported mistake.

For example:
- “Jackson became Jackson in three sessions” → “Jaxon became Jackson in three sessions”.
  The first occurrence identifies the person; the second reports the wrong transcription and must remain “Jackson”.
- Likewise, in “X was transcribed as Y”, “X became Y”, or “it wrote Y instead of X”, preserve Y when it is the reported erroneous output.

Do not exempt an entire sentence merely because it discusses transcription. Other actual names in that sentence still need correction.

## High-priority recognition patterns

### People
- “Jackson” referring to the person → “Jaxon”. This includes direct address and task assignments, with no explicit role required:
  - “Jackson, by Tuesday, June 9th, you own the intake vocabulary wiring” → “Jaxon, by Tuesday, June 9th, you own the intake vocabulary wiring”.
  - Apply the reported-wrong-spelling exception above when appropriate.
- “search's” or “Sarah's” can represent “Saoirse's”, especially for someone's replay, rollout note, deployment work, or operational work:
  - “search's less friendly replay” → “Saoirse's less friendly replay”.
  - “Sarah's rollout note” → “Saoirse's rollout note”.
  - Do not change genuine references to search functionality.
- “Pre's” referring to someone's API notes → “Priya's”. Shortened or imperfect pronunciations can still represent listed names.
- “Merritt” referring to a person in a personal or family conversation can represent “Mairead”:
  - “Merritt sent me her taco recipe” → “Mairead sent me her taco recipe”.
- “Sochitel” referring to a person → “Xochitl”.
- “Apha” referring to a person can represent “Aoife”.
- Use sound and sentence context for other variants of listed names. Listed roles and relationships are clues, not mandatory conditions.

### Terms
- “COIB” in the context of hosting, infrastructure costs, billing, or charges represents “Koyeb”:
  - “alongside the reduced COIB charge” → “alongside the reduced Koyeb charge”.
  An all-capital transcription can be a phonetic rendering of a company name, not a genuine acronym.
- “Elora” in a model-testing, adapter, fine-tuning, or MLX context can represent “a LoRA”:
  - “If we later test Elora with MLX” → “If we later test a LoRA with MLX”.
  Here the spoken article and term have been fused into one word; restore both. Do not preserve “Elora” as a person's name when the sentence clearly concerns testing a model technique.
- Inspect all listed technical terms for phonetic approximations, alternate spellings, and incorrect word boundaries. Require support for the particular replacement, not merely a technical topic.

## Avoid false insertions
- Never add a listed name or term simply because it fits the topic.
- Do not expand a lone letter or vague fragment into a listed acronym without a convincing phonetic and contextual match.
- In particular, “loads the M file” in a discussion of shell execution and API keys does not justify “loads the MLX file”. Leave that wording unchanged.
- Do not replace genuine ordinary words, unrelated names, or intentionally reported erroneous spellings merely because they resemble a listed entry.
- When no candidate is adequately supported, preserve the original span.

Before outputting, check for missed corrections, especially an opening “Jackson”, possessive names, “COIB” in a hosting-cost discussion, and “Elora” in an MLX experiment. Then verify that every edit corrects a supported listed name or term and that reported wrong spellings and all unrelated text remain intact.