A wrong product name in a caption needs a text correction. A wrong product name in the recording needs an audio correction too. Find which version of the error exists before you regenerate the video or replace every subtitle.
This matters most when a founder explains an unfamiliar app, a customer names an integration, or an engineer says an acronym that sounds like an ordinary word. The rest of the transcript can look plausible while the one term a prospective customer needs is wrong.
The procedure below uses an illustrative product called QueueNest. It is a fictional example, not a Prolifik customer or a transcription test.
Inspect three versions of the same sentence
Play the source recording, read its caption, then watch the exported video. Do not assume the text in an editor is the text already embedded in the file.
Suppose the speaker says, “QueueNest keeps the original webhook payload.” The review sheet might look like this:
| Layer | What it contains | Required action |
|---|---|---|
| Recorded speech | Correct product name and technical term | Keep the audio |
| Editable caption | “Q nest keeps the original web hook payload” | Correct spelling and word grouping |
| Exported picture | Earlier wrong caption remains visible | Render and inspect a replacement file |
A fourth possibility is that the speaker actually says the wrong integration name. Correcting the text to the intended name would make the audio and caption disagree. Ask the speaker to record the sentence again or remove the claim. Do not quietly replace a customer's meaning with the marketing team's preferred version.
YouTube lets creators edit caption text and timing in a caption track. That does not erase text already burned into a video's picture. An uploaded file with a wrong embedded word needs a corrected export, even if its separate caption track is accurate.
Build a short reference sheet before correcting anything
Gather the terms the recording really uses. A useful sheet contains the official spelling, the pronunciation heard in the source, and a source that establishes the term. Keep customer names private unless their use is authorized.
For the illustrative QueueNest recording:
| Heard in the source | Approved text | Check against |
|---|---|---|
| “queue nest” | QueueNest | Current product name |
| “web hook” | webhook | Product documentation |
| “J son” | JSON | The actual payload format |
| “retry queue” | retry queue | The feature being shown |
This is an editorial reference, not a promise that a video tool has a custom vocabulary feature. A human can use it while reviewing the transcript even when the tool has no vocabulary controls.
Do not normalize terms that are genuinely different. A queue and a webhook perform different jobs. If the speaker uses the wrong one, changing the caption alone hides a factual issue rather than fixing transcription.
Correct the smallest truthful unit
Start with spelling and punctuation. Then inspect the words around the correction. A longer name may wrap onto another line or remain visible for too little time.
The original caption “Connect Q nest and go” might become “Connect QueueNest.” The spelling is repaired, but the sentence has also lost the vague “and go.” That second change is an editorial rewrite. In a verbatim interview caption, keep what was said unless your caption policy explicitly permits light cleanup that preserves meaning.
For an authored explainer, rewrite the script before rendering. For a recorded quotation, preserve the quotation. Those are different editing permissions.
Check numbers and negatives beside technical terms. “Does not retry failed payments” and “does retry failed payments” are not interchangeable. A correct app name cannot rescue the wrong promise.
Our short-form caption guide covers line length and timing once the words are accurate. Use it after the correction, rather than styling a sentence you have not verified.
Review all places the term can appear
The same mistake may exist in an opening title, lower-third, end card, post caption and filename. Search editable copy, but inspect the picture too. A screenshot can contain an old product label that is not part of the transcript.
For QueueNest, the reviewer would play the sentence, read the opening label, inspect the displayed integration screen and check the post caption. If the interface now uses a new name, decide whether the old recording remains accurate. A misleading old screen may require a new capture.
Keep an issue log with timecode, current text, replacement and reviewer. This lets a teammate fix the right occurrence without guessing which version was approved. If a source quotation needs a substantive change, put it back to the speaker or owner.
Check the delivered file, not the correction request
After rendering, watch the corrected moment with audio and then muted. Confirm the product name is legible, the timing still follows the speech, and no old text remains underneath it. Recheck the surrounding sentence, not only the changed word.
If you are creating candidates from a longer recording, Prolifik's Clipper provides the clipping workflow. Review names and technical terms in the finished candidates before approving them. This guide does not assume a native vocabulary-training control or an editable subtitle-file import.
For interview material, also use the customer interview clipping guide to preserve the speaker's conditions and attribution. A clean caption should make the original statement easier to understand, not make it say something new.
Create clips you can check against the recording
Bring a source you have rights to use, then review boundaries, captions and framing.
Explore Prolifik ClipperFacts checked 2026-10-24. Worked examples are illustrative unless a real source is identified.
- YouTube: edit or remove captions Checked 2026-10-24
- YouTube: add subtitles and captions Checked 2026-10-24
