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

Preserve all other text exactly, including wording, punctuation, capitalization, numbers, and sentence boundaries. Do not polish grammar, repair unrelated transcription errors, or add missing information.

Use the following approach:
1. Look for phonetic approximations, alternate spellings, incorrect capitalization, and words incorrectly joined or split that plausibly represent a listed name or term.
2. Use the surrounding sentence to distinguish an intended name or term from an ordinary word. A misrecognized name can look like a valid English word or a different, correctly spelled name; do not overlook it merely because it is readable.
3. Use the listed roles and relationships as supporting evidence, not as a reason to introduce a name. A mention of investors does not by itself imply Kaveh, and a mention of design does not by itself imply Xochitl.
4. Replace only the span corresponding to the misrecognized name or term, using its exact listed spelling. Preserve possessives and surrounding text.
5. Leave already-correct names and terms unchanged. Do not force every unfamiliar expression or person into the supplied list.

Important recognition patterns, applied with context rather than as unconditional replacements:
- “Caitlin,” “Kaitlin,” or “Caitlyn” can represent Kaitlynn, particularly when someone is addressed or assigned work.
- “Source” can represent Saoirse when the sentence refers to a person—for example, “Source says” followed by deployment or hosting discussion and references to “her.” Preserve ordinary uses such as “source code” or “the source says.”
- “Ted” can represent Tadhg in personal conversation about a friend, visits, or family outings. Do not assume a readable name must already be correct.
- “AFAS” or similar sounds can represent “Aoife's” when the phrase calls for a person's possessive, such as “design and AFAS evaluation work.”
- Technical names may appear as ordinary words or separated syllables: for example, “voice flow” may be VoiceFlow and “Coyab” may be Koyeb.

Avoid semantic guesswork. For example, “assured investor check-in” does not provide a spoken approximation of Kaveh and must not become “Kaveh's investor check-in.” Leave unrelated transcription errors untouched.

Before outputting, check both that you have caught plausible name/term errors and that every replacement has a corresponding sound or spelling in the original. Remove any change based only on the topic.