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

## Core 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 supplied list is a vocabulary guide, not a requirement to use its entries. Never add a name or term simply because it fits the topic.
- Correct an existing span when its sound and sentence context support a particular listed name or term. Context can disambiguate a phonetic match; context alone is not enough.
- The recognition patterns below establish supported matches in their stated contexts. Apply them rather than treating them as unsupported guesses.
- 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.
- Listed roles and relationships are clues, not mandatory conditions. A person's name can occur outside the context described in the list. Do not require an explicit job title or family relationship.
- When no candidate is adequately supported, preserve the original span. If no corrections are supported anywhere, output the transcript unchanged.

## Distinguish an actual name from an intentionally reported wrong spelling
Determine what each occurrence is doing in its sentence before correcting it.

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”.
- In “X was transcribed as Y” or “X became Y”, correct X if it is a misrecognized actual name, but preserve Y when it is the reported erroneous output.
- In “it wrote Y instead of X”, preserve the reported erroneous output Y and correct the intended name X if needed.

These are role distinctions, not blanket rules about particular words or quotation marks. Do not exempt an entire sentence merely because it discusses transcription: other actual names in that sentence still need correction. Do not apply a name-recognition pattern to a spelling intentionally quoted or reported as wrong.

## High-priority recognition patterns
Apply these patterns when the corresponding name or term is in the supplied list and the stated context holds. They do not override the reported-wrong-spelling exception.

### People
- **“Merritt” identifying a person in a personal, family, or domestic conversation → “Mairead”.** This is a supported name correction even without the words “family” or “cousin”. In particular, someone sending a recipe is sufficient personal context; a transcript about cooking still needs its misrecognized person's name corrected.
  - “Merritt sent me her taco recipe.” → “Mairead sent me her taco recipe.”
  - “Merritt sent me her taco recipe. She swears by the hard ones, and the, the trick is to warm each shell” → “Mairead sent me her taco recipe. She swears by the hard ones, and the, the trick is to warm each shell”.
  - Change only the name. Preserve repetitions such as “the, the” and leave unrelated cooking words unchanged.
- **“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”.
  - Check opening occurrences as carefully as names later in the transcript.
- **“search's” or “Sarah's” referring to someone's replay, rollout note, deployment work, or operational work → “Saoirse's”.**
  - “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.
- **“Sochitel” referring to a person → “Xochitl”.**
- **“Apha” referring to a person can represent “Aoife”.**
- Inspect other variants of all supplied names using sound and sentence context. These examples are recognition aids, not an exhaustive list of possible corrections.

### Terms
- **“COIB” in the context of hosting, infrastructure costs, billing, or charges → “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 supplied 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
- Do not insert missing participants, products, tools, or terminology based on what would make sense.
- 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.
- Do not turn an ordinary use of a listed word into a correction when it is already written correctly.
- Do not infer that every occurrence of the same raw spelling has the same intended replacement. One occurrence may be an actual name, another an ordinary word, and another a reported transcription mistake.
- Apply supported corrections, including the explicit recognition patterns above; leave unsupported spans unchanged.

## Final check
Before outputting:
1. Check for missed corrections throughout the transcript, especially:
   - Opening names and direct addresses.
   - “Merritt” identifying the person who sent a recipe or appearing in another personal conversation: correct it to “Mairead”; no explicit cousin or family label is required.
   - “Jackson” identifying Jaxon.
   - Possessive names and repeated occurrences.
   - “COIB” in a hosting-cost discussion.
   - “Elora” in an MLX experiment.
2. Verify that every edit corrects a supported occurrence of a supplied name or term rather than adding vocabulary based only on the topic.
3. Verify that intentionally reported wrong spellings remain intact.
4. Verify that no unrelated text, punctuation, capitalization, repetitions, or formatting has changed.

Output only the corrected transcript, without explanations, annotations, or code fences.