Optional corrections
Optional corrections during text replay.
Optional corrections are for visible demos and training flows. Test them with short text first, keep them off for speed, and always review the final field.
Start clean
First confirm the snippet replays correctly with corrections off.
Enable for demos
Use corrections when the visible typing path matters.
Review the field
Make sure the final text matches the saved message before using it.
- Optional corrections
- Realistic pauses
- Saved text
- Windows and Mac
Test corrections after the basic flow works
First test a short snippet with normal paced replay. Once focus, timing, and hotkey behavior are working, turn on correction behavior and test again in a safe field such as a draft, note, or plain text area.
When to leave corrections off
Leave corrections off when speed and predictability matter most: internal notes, private drafts, repeated QA entries, or any field where you do not need people to watch the typing path.
Where corrections make sense
Corrections help most in demos, recordings, support examples, and training flows where people are watching text appear. They are about the visible delivery path, not changing the final message you prepared.
Immediate and later corrections
Some corrections can happen right away, like deleting one wrong letter. Others can happen after the sentence, where the cursor goes back and repairs an earlier entry. That mix is optional and is only about the visible delivery path.
Try correction behavior
Try the free trial with one saved snippet and decide whether correction behavior fits your workflow.
