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. Replace supported existing spans; never add a name merely because its role or topic fits. Preserve everything outside the matched spans exactly.

Use this procedure silently:

1. Scan the entire transcript, including the first word, for listed entries and plausible sound-alikes, alternate spellings, split forms, acronyms, and corrupted possessives.
2. Apply the high-confidence name rules below. A recognizable variant in a clear person-name position is sufficient evidence; no explicit job title or relationship label is required.
3. Check other candidates using sound, grammar, and surrounding context. Correct supported terms as well as names.
4. Replace only the supported spans with the exact listed spelling and capitalization. Preserve genuine possessive endings.
5. Before output, scan again for missed candidates, especially opening names and direct addresses. Undo unsupported replacements and any edits outside matched spans.
6. Output only the corrected transcript.

High-confidence name rules:

- **Jackson → Jaxon when Jackson names or addresses a person in the compatible discussion.** This includes sentence openings and direct addresses. In “Jackson, by Tuesday, June 9th, you own the intake vocabulary wiring,” change only “Jackson” to “Jaxon.” Leave “by Tuesday, June 9th” and all other text exactly unchanged. Do not leave Jackson unchanged merely because it is a valid name.
- **Caitlin or Kaitlyn → Kaitlynn when used as a person's name.** Direct address such as “Caitlin, by Tuesday, you own …” is sufficient evidence.
- **Oifi → Aoife when used as a person's name.** For example, “Oifi got her transcription script working” becomes “Aoife got her transcription script working.” The spelling need not closely resemble Aoife: use the spoken-name match and personal grammar. This does not require the transcript to identify her as an intern.
- **Kave → Kaveh when used as a person's name.**
- Apply these rules to every supported occurrence, not just the first one. Do not require a second mention, a role, or an explicit introduction.

Additional name recognition:

- 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.” Do not change genuine ordinary 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 personal invitation supports correcting “Ted” to “Tadhg.” The transcript need not explicitly call him a friend. This is not a universal replacement of Ted.
- In a discussion explicitly about the listed people's names being transcribed or spelled incorrectly, use that context to recognize corrupted names. For example, in “Jackson keeps getting spelled some other way, and so does Sarah's,” the two corrupted name spans are “Jackson” and “Sarah's”: correct them to “Jaxon” and “Saoirse.” Here the final apostrophe-s belongs to the corrupted rendering of the name, rather than a genuine possessive that must survive.
- 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.
- Preserve genuine possessives: when the context means something belonging to a person, retain the possessive ending after correcting the name. Do not indiscriminately strip apostrophe-s from names.
- These examples are recognition guides, not the only permitted corrections. Check all supplied names for plausible spoken variants, using personal grammar and context.

Term recognition:

- Check all supplied terms for phonetic substitutions, spacing, letter-name renderings, and capitalization errors.
- Correct supported occurrences to the exact listed spelling, including internal capitalization and spacing.
- 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.
- Leave already-correct names and terms unchanged.

Avoid unsupported insertions:

- Every correction must replace an existing spoken-word candidate that plausibly corresponds to the listed entry.
- A role, topic, or implied participant alone is not 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.
- Do not replace an unrelated person or reference just because a listed name exists.
- If there is no supported match, leave the span unchanged. However, do not use this caution to reject the clear personal-name variants and direct addresses described above.

Strict preservation:

Preserve everything outside matched name-or-term spans exactly, including wording, punctuation, dates, numbers, grammar, whitespace, and formatting. Do not repair general transcription errors, normalize dates, spell out ordinals, add hyphens, split sentences, or otherwise rewrite the transcript. For example, retain “June 9th” exactly even when correcting an adjacent name. Output no commentary.