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. Every replacement must correspond to an existing, plausibly misrecognized occurrence.

How to recognize a correction:
- Use pronunciation, spelling similarity, and sentence context together. A name or term may have been transcribed as another plausible name, a common word, an unfamiliar acronym, a shortened fragment, or several words. A grammatically valid transcript can still contain a misrecognized name or term.
- Word boundaries can be wrong. A short article and a term may be fused into one apparent word or name. Correct that local span, restoring the article when it is part of the misrecognized phrase: for example, “Elora” can represent “a LoRA.”
- Pay attention to person-reference positions: who said something, whose notes or recipe are mentioned, who owns a task, and direct address. Possessives are particularly useful clues. Preserve the possessive ending when correcting the name.
- Use descriptions in the list as supporting context, not rigid requirements. A person can discuss subjects outside their listed role. A personal anecdote need not explicitly say “family” or “cousin” to refer to a listed family member.
- Do not require an exact phonetic match when both the approximate sound and the context support the listed name or term. Do not dismiss a possible correction merely because the raw text is a plausible name or is written in uppercase.

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 necessarily the intended technical word in a possessive attribution.
- “Pre's API notes” → “Priya's API notes”: a clipped or misheard person name can appear before technical notes.
- “Merritt sent me her taco recipe” → “Mairead sent me her taco recipe”. In this personal recipe-sharing context, correct “Merritt” to “Mairead”; do not leave it unchanged simply because “Merritt” is itself a valid name or because the sentence does not explicitly mention a cousin. Mairead can be pronounced approximately “muh-RAID” or “muh-RED,” so a transcription such as “Merritt” can be a sound-based name error.
- Keep the rest of a personal anecdote unchanged. For example, correcting “Merritt” to “Mairead” does not authorize removing a later repeated “the, the” or editing cooking instructions.

Technical-term 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”; its uppercase appearance does not make it a separate intended acronym.
- “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. Recover the article as well as the exact term spelling.
- These corrections are local: correcting “COIB” does not authorize changing nearby “re-ranker” to “reranker” or “$480” to words.

Avoid false insertions:
- Do not add names or terms, expand vague references, or replace unrelated text merely because a listed item fits the topic.
- Technical replacements need a plausible sound/spelling match AND compatible meaning. Shared letters or a technical setting alone are insufficient.
- In particular, “M file” in a sentence about shell execution, loading configuration, and API keys is not evidence for “MLX file”. Leave that text alone rather than forcing a listed term.
- 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. The “Elora” → “a LoRA” correction requires a compatible model-experiment context.
- Do not automatically replace every unlisted person name. Use the local context and a plausible pronunciation relationship, including the supported person-name corrections above.
- If there is no reasonably supported name/term correction, retain the original text.

Before returning the transcript:
1. Check for overlooked phonetic or clipped names, technical terms disguised as unfamiliar acronyms, and articles fused with terms.
2. Check personal anecdotes as well as work-related sentences. In particular, do not overlook “Merritt” → “Mairead” in the recipe-sharing context described above.
3. Verify that every change corrects an existing name/term occurrence rather than introducing a new one.
4. Verify that all unrelated text and formatting, including repetitions, remain unchanged.