Correct only mistranscribed occurrences of the supplied names and terms in the raw speech-to-text transcript. Output only the corrected transcript.

The supplied list is a spelling reference, not a requirement to mention every entry. Correct supported occurrences, including ordinary words that are actually mistranscribed names. Do not insert names based only on a role or topic. The roles in the list are helpful context, not prerequisites for recognizing a name.

Use this procedure silently:

1. Scan the entire transcript for listed names and terms and their plausible sound-alikes, alternate spellings, split forms, acronyms, and possessives. Check the first word, sentence beginnings, and direct addresses especially carefully.
2. Decide whether each candidate represents a listed entry using its sound, grammatical position, and surrounding context. A recognizable name variant used as a person's name does not require an explicit statement of that person's role.
3. Replace supported spans with the exact spelling and capitalization from the list. Preserve possessive endings. Leave already-correct occurrences unchanged. Once a recognizable variant is supported as a listed name, correct it; retaining a different valid spelling is not the conservative choice.
4. Check again for missed candidates and unsupported replacements. In particular, check whether an opening name variant was overlooked while names later in the transcript were corrected.
5. Output the transcript without commentary.

Name recognition rules:

- **Direct address counts as evidence that a name was spoken.** A name followed by a comma and a deadline, assignment, question, or request is a direct address. An opening such as “Caitlin, by Tuesday, you own …” or “Jackson, by Tuesday, you own …” is a name occurrence, even if no job title appears. In a compatible work discussion, correct these to “Kaitlynn, by Tuesday, you own …” and “Jaxon, by Tuesday, you own …”. A longer deadline between the name and assignment does not weaken this evidence. Do not leave a recognizable alternate spelling unchanged merely because it is also a valid name.
- Recognizable variants include “Caitlin” and “Kaitlyn” for “Kaitlynn,” “Jackson” for “Jaxon,” and “Kave” for “Kaveh.” Use context to distinguish a person's name from an unrelated word or reference.
- **Recognize phonetic spellings of Aoife, including “Oifi.”** In “Oifi got her transcription script working,” “Oifi” is a person's name in subject position and should become “Aoife.” References such as “her script” and “I'll have her try” support the personal reading. The transcript need not call her an intern, and her work need not match a particular role description.
- **An ordinary word can be a mistranscribed name.** When “Source says …” introduces a person's statement about deployment, hosting, or operations, and a later “her” refers to that speaker, correct “Source” to “Saoirse.” For example, “Source says the Coyab bill went up … I asked her to dig into the logs” becomes “Saoirse says the Koyeb bill went up … I asked her to dig into the logs.” This combination supplies positive evidence; do not reject it just because “Source” is an ordinary word. Do not change genuine uses such as “the source code.”
- **Short-name sound-alikes can be supported by personal context.** In “Ted says the beach by his place is great … he asked if we want to come down … Bring the kids … lunch at his place,” the friend's invitation supports correcting “Ted” to “Tadhg.” Do not require the transcript to explicitly call him a friend. This is a contextual correction, not a universal replacement of “Ted.”
- A name and its possessive ending may be fused into an apparent word or acronym. For example, “AFAS evaluation work” can represent “Aoife's evaluation work.” Correct the entire supported corrupted span, including the possessive.

Term recognition rules:

- Check for phonetic substitutions, spacing, letter names, and capitalization errors in all supplied terms.
- For example, “voice flow” can become “VoiceFlow,” and “Coyab” can become “Koyeb,” when the surrounding text refers to the relevant product or service.
- Preserve ordinary uses of words that also appear in the list. Do not force a technical term into unrelated text.

Avoid unsupported insertions:

- Require an existing spoken-word candidate that plausibly corresponds to the listed entry. A role or topic by itself is not such a candidate.
- An “investor check-in” does not justify inserting “Kaveh” or “Kaveh's.”
- Do not turn an unrelated phrase such as “assured investor check-in” into a person's name merely to make the sentence more plausible.
- If the evidence does not support a name-or-term match, leave the span unchanged.

Preserve everything outside the matched name-or-term spans exactly, including wording, punctuation, dates, numbers, grammar, whitespace, and formatting. Do not repair general transcription errors, change date formats, add hyphens, split sentences, or otherwise rewrite the transcript.