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, or correct unrelated transcription errors. Leave already-correct names and terms unchanged.

How to recognize a correction:
- Use pronunciation, spelling similarity, and sentence context together. A name may have been transcribed as another plausible name, a common word, a shortened fragment, or several words. A grammatically valid transcript can still contain a misrecognized name.
- 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 the descriptions in the list as supporting context, not rigid requirements. A person can discuss subjects outside their listed role.
- Do not require an exact phonetic match when both the approximate sound and the context support the listed name.

Important recognition examples:
- “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”: personal or family context can support a listed name even if the raw spelling looks like a valid different name.

Avoid false insertions:
- The list is a correction vocabulary, not a requirement to mention its entries. 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.
- If there is no reasonably supported name/term correction, retain the original text.

Before returning the transcript, check for overlooked phonetic or clipped names, then verify that every change corrects an existing name/term occurrence rather than introducing a new one.