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

Make only local name/term corrections. Preserve all other wording, punctuation, capitalization, repetitions, and formatting. Do not polish the transcript, repair grammar, remove filler, normalize numbers, or correct unrelated transcription errors. Leave already-correct names and terms unchanged.

The list is a correction vocabulary, not a requirement to mention its entries. Correct an existing occurrence; never introduce a name or term merely because it fits the topic.

## Recognizing names

Use pronunciation, spelling similarity, and local sentence context together. A listed name may have been transcribed as another plausible name, a common word, a clipped fragment, or several words. The raw text being grammatical or containing a valid-looking name does not make it correct.

Pay particular attention to person-reference positions:
- The subject of “said,” “sent,” “asked,” or similar verbs.
- Someone's notes, recipe, replay, or other possession.
- Task ownership and direct address.

Preserve possessive endings when correcting names.

Descriptions in the list are supporting clues, not restrictions. A person can discuss subjects outside their role. Personal conversation does not have to explicitly say “family,” “cousin,” or “friend” before a listed personal name can be recognized.

**Important: recognize Mairead in ordinary personal conversation.** “Merritt” is a plausible transcription of Mairead. In “Merritt sent me her taco recipe,” the intended name is **Mairead**: correct it to “Mairead sent me her taco recipe.” Do not leave “Merritt” unchanged just because it is a plausible name or because the transcript never explicitly mentions a cousin. Recipe-sharing and the personal reference support this correction. Make the name correction even in a long transcript whose remaining sentences need no changes.

Other important person-name corrections:
- “Jackson said” → “Jaxon said”
- “Jackson, please” → “Jaxon, please”
- “Sarah's rollout note” → “Saoirse's rollout note” when referring to the deployment/ops person's note.
- “search's less friendly replay” → “Saoirse's less friendly replay” when referring to someone's replay/test scenario. Do not assume “search” is the intended technical word in a possessive attribution.
- “Pre's API notes” → “Priya's API notes”: a clipped or misheard name can appear before technical notes.

Do not require an exact phonetic match when the approximate sound and context support the listed name.

## Recognizing technical terms

Use a plausible sound/spelling match AND compatible meaning. A term may appear as common words, an unfamiliar acronym, a fragment, or a phrase with incorrect word boundaries. Uppercase text is not necessarily an intended acronym.

Important corrections:
- “the reduced COIB charge” → “the reduced Koyeb charge” in a discussion of hosting, inference costs, or migrating workloads from paid infrastructure to owned hardware. “COIB” is a plausible sound-based transcription of “Koyeb.”
- “If we later test Elora with MLX” → “If we later test a LoRA with MLX” in a discussion of local text-model experiments. Here “Elora” represents the fused phrase “a LoRA,” not a person. Restore the article as part of correcting that local span.

Word boundaries can be wrong: a short article and a term may be fused into one apparent word or name. Restore the article only when it is part of the misrecognized phrase.

These corrections are strictly local. Correcting “COIB” does not authorize changing nearby “re-ranker” to “reranker” or “$480” to words.

## Avoiding false insertions

- Do not add names or terms, expand vague references, or replace unrelated text merely because a listed item fits the topic.
- Shared letters or a technical setting alone are insufficient evidence for a technical replacement.
- “M file” in a sentence about shell execution, loading configuration, and API keys is not evidence for “MLX file.” Leave it unchanged.
- Ordinary uses of words such as “search” must remain unchanged unless the local sentence supports a misrecognized name.
- Do not automatically replace every apparent person name with a technical term. “Elora” → “a LoRA” requires compatible model-experiment context.
- Do not use the list to invent a missing speaker, identify an unspecified person, or complete an unstated reference.
- If there is no reasonably supported name/term correction, retain the original text.

## Final check

Before returning the transcript:
1. Check for overlooked names, especially valid-looking substitute names in personal conversation. If the transcript says “Merritt sent me her taco recipe,” ensure “Merritt” has been corrected to “Mairead.”
2. Check for clipped names, possessive attributions, technical terms disguised as acronyms, and articles fused with terms.
3. Verify that every change corrects an existing name/term occurrence rather than introducing a new one.
4. Verify that unrelated text and formatting remain unchanged, including repetitions such as “the, the.” Do not remove a repetition while correcting a nearby name.
5. Output only the corrected transcript.