Correct only mis-transcribed names and terms in the raw speech-to-text transcript, using the supplied names-and-terms list. Output only the corrected transcript.

The list is a spelling reference, not a checklist. Correct names and terms that were actually spoken; do not add names merely because their roles fit the topic.

Procedure:
1. Scan the entire transcript for possible misheard names and terms, including the first word, direct addresses, and possessives. Find all candidates, not just the first obvious correction.
2. Use sound similarity and sentence context to decide which candidates refer to listed entries. A misheard name can appear as a valid ordinary word or another correctly spelled name. The person's role need not be explicitly stated.
3. Replace only the misheard spans, using the exact spelling and capitalization from the list. Preserve everything outside those spans exactly.
4. Check the whole transcript again for missed candidates and unsupported replacements.

Recognition rules:
- Recognize phonetic approximations, alternative spellings, distorted possessives, and incorrect word boundaries.
- Use surrounding words and listed roles to disambiguate a plausible sound match. Do not require an exact pronunciation match.
- A name at the beginning of a sentence is not exempt from correction. In “Jackson, by Tuesday, you own…”, “Jackson” is a direct address, not unrelated prose.
- Context supports a sound match; it cannot substitute for one. Never insert a person solely because their role matches the discussion.
- Leave an ambiguous ordinary phrase unchanged when there is no adequate evidence that it represents a listed name or term.

Important recognition examples:
- “Jackson” used as a person's name or direct address → “Jaxon”. For example, “Jackson, by Tuesday, you own the intake vocabulary wiring” → “Jaxon, by Tuesday, you own the intake vocabulary wiring”.
- “Caitlin” or “Kaitlin” used as a person's name or direct address → “Kaitlynn”. Product planning, schedules, rollout documents, or metric definitions can support this identification; the words “product manager” need not appear.
- “Kave” used as a person's name → “Kaveh”.
- “Source says” in a deployment, hosting, billing, or ops discussion, especially when later “she/her” refers to the speaker → “Saoirse says”. For example, in “Source says the Coyab bill went up … I asked her to dig into the logs”, correct both “Source” to “Saoirse” and “Coyab” to “Koyeb”. Do not automatically change literal uses of “source” in unrelated contexts.
- “Ted says” in a personal invitation or outing involving a friend → “Tadhg says”.
- “AFAS evaluation work” in a discussion of someone's work → “Aoife's evaluation work”. Aoife is pronounced approximately “EE-fa”; recognize distorted possessive forms as well.
- “Coyab” referring to the hosting service or its bill → “Koyeb”.
- “voice flow” referring to the product or its team sync → “VoiceFlow”.

Preserve possessives: a misheard possessive referring to Aoife becomes “Aoife's”, not “Aoife”.

Avoid semantic substitutions without a sound match. For example, do not replace “assured investor check-in” with “Kaveh's investor check-in”: the investor role alone is not evidence that his name was spoken.

Make the smallest necessary replacements. Preserve all other words, punctuation, dates, numbers, hyphenation, formatting, and sentence structure exactly as supplied. Do not polish prose, normalize dates, fix grammar, or correct unrelated speech-recognition errors.

Before outputting, silently verify that every change corrects a specific misheard name or term, that all supported corrections throughout the transcript were made, that no name was added solely from topic or role, and that nothing else changed.