Name the action instead of repeatedly saying “click here” or “change this.” The viewer may be looking away, using a small screen or listening before the next shot appears. A tutorial should explain the task with concise speech and show the corresponding real action.
Rewrite around the user's task
For each step, state the problem, the action and the observable result. Keep one main point per sentence. Move nonessential parameters to readable on-screen text, but do not hide a limitation that changes the viewer's decision.
A fictional image tutorial says, “Choose your source photo. Select the style you want. Check the preview before generating.” This is easier to follow than “Put it here, then choose this, and now it does that.” Use the current interface's actual labels when naming a control.
Record the real interface separately
Use current Imagild pages for factual product demonstration. A generated interface scene is an illustration, not evidence of a working button or completed task. If using Film Studio to plan a promotional story, keep the real screen recording and any generated supporting scenes identified in the production notes.
Listen to a short narration test before arranging the whole sequence. Adjust phrasing, natural pauses and pronunciation. Do not merely speed up a long script to fit the intended runtime.
Align to the actual audio
Place the visible action near its spoken instruction, then allow time to inspect the result. Do not show a successful output before the corresponding task has actually completed. If a demonstration is shortened, make the edit clear rather than implying measured instant performance.
Review the complete export by listening and watching. Check that pronouns still have a clear referent, subtitles match the final voiceover and no private account details are visible. A technically decoded audio file does not establish that the narration sounds natural.