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

The supplied list is a spelling reference, not a checklist of entries to insert. Every correction must replace an existing span that plausibly represents the listed name or term. Preserve everything outside those spans exactly.

Use this procedure silently:

1. Find personal-name candidates first, including the first word of the transcript, sentence beginnings, direct addresses, and possessives. Resolve clear spelling variants before considering more ambiguous sound-alikes.
2. Scan for supplied terms and their phonetic substitutions, alternate spellings, split forms, letter names, and capitalization errors.
3. Replace supported spans with the exact spelling and capitalization from the supplied list.
4. Compare the result with the original. Undo unsupported replacements and all changes outside matched spans. Check specifically that no supported name variant at the beginning of the transcript was overlooked.
5. Output only the transcript.

## Clear personal-name variants

When the span is being used as a person's name in a compatible context, apply these corrections:

- Jackson → Jaxon
- Caitlin or Kaitlyn → Kaitlynn
- Kave → Kaveh
- Oifi → Aoife

These are spelling corrections, not requests to add people. Do not require an explicit job title, relationship label, or introduction before correcting a recognizable personal-name variant. Conversely, do not replace a word that clearly refers to an unrelated person, place, or ordinary concept.

**Direct address is strong evidence of personal-name use.** In a work assignment, “Jackson, by Tuesday, …” must become “Jaxon, by Tuesday, …”. The assignment may continue for several sentences; its length or administrative details do not weaken the name match. Likewise, “Caitlin, by Tuesday, you own …” becomes “Kaitlynn, by Tuesday, you own …”. Change only the name, not the date or surrounding wording.

**A sentence-initial subject can also be a clear name occurrence.** For example, “Oifi got her transcription script working” becomes “Aoife got her transcription script working”. The spelling “Oifi” is a plausible transcription of Aoife; the subject position and personal pronoun support the match. Do not overlook it because other names appear later in the transcript.

Do not leave a supported variant unchanged merely because it is also a valid spelling of another name.

## Context-dependent name recognition

An ordinary word can be a mistranscribed name, but it needs positive evidence:

- 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”. Preserve 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 invitation supports correcting “Ted” to “Tadhg”. An explicit statement that he is a friend is unnecessary. This is not a universal replacement of “Ted”.
- A name and its possessive ending may be fused into an apparent word or acronym. In a supported personal context, “AFAS evaluation work” can represent “Aoife's evaluation work”. Correct the whole corrupted span.
- Preserve possessive endings when correcting possessive names. Do not mistake a fused possessive for evidence that no name was spoken.

Use pronunciation, grammatical position, and surrounding context together. Roles and relationships can support a spoken candidate, but cannot create one.

## Term recognition

Check all supplied terms for sound-alikes, spacing errors, letter-name transcriptions, and capitalization errors.

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 technical terminology into unrelated text.

## Avoid unsupported insertions

- Require an existing word or span that plausibly corresponds to the proposed name or term.
- A role, topic, or expectation that someone should be mentioned is insufficient.
- “Investor check-in” does not justify adding “Kaveh” or “Kaveh's”.
- Do not turn an unrelated phrase such as “assured investor check-in” into a person's name merely to improve plausibility.
- If a match is not supported, leave the original span unchanged.

## Exact preservation

Outside supported name-or-term spans, preserve wording, punctuation, dates, numbers, grammar, whitespace, and formatting exactly. Do not repair general transcription errors, normalize dates, add hyphens, split sentences, or otherwise rewrite the transcript.