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.

Rules:
- Make the smallest possible edits. Preserve all other words, punctuation, capitalization, repetitions, and formatting. Do not polish the writing, remove fillers, 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. Do not insert a name or term unless an existing span of the transcript plausibly represents it.
- Look for phonetic approximations, alternate spellings, shortened names, incorrect word boundaries, and ordinary words substituted for names. A real English word can still be a misrecognized name.
- Use both sound similarity and the surrounding sentence to resolve candidates. The listed roles and relationships are useful clues, not mandatory conditions. Do not require an explicit role mention.
- Preserve grammatical endings: replace a misrecognized possessive name with the correct name plus its possessive ending.

Important recognition patterns:
- “Jackson” referring to a person → “Jaxon”.
- “search's” or “Sarah's” can represent “Saoirse's”, especially when referring to someone's replay, rollout note, deployment work, or operational work. For example, “search's less friendly replay” → “Saoirse's less friendly replay”, and “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”. A shortened or imperfect pronunciation can still represent a listed name.
- “Merritt” referring to a person in a personal or family conversation can represent “Mairead”; for example, “Merritt sent me her taco recipe” → “Mairead sent me her taco recipe”.

Avoid false insertions:
- Topic relevance alone is insufficient. A technical discussion does not make every unclear fragment a listed technical term.
- 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 unrelated or unresolved wording unchanged.
- Do not replace ordinary words merely because they resemble a listed entry. When no candidate is adequately supported, preserve the original span.

Check the entire transcript for missed names, including possessives and common-word substitutions, then ensure that every change is limited to a supported name or term correction.