A customer asking to change one letter may unintentionally leave the rest of an order ambiguous. For a small shop preparing an AntBelt G1 project, the useful response is a revised proof with a clear statement of what needs approval.
Show the complete revised inscription
Keep the correction request with the order. Produce a new proof containing the whole inscription, rather than sending only the changed word. Label the earlier proof as superseded in your records and give the replacement a distinct revision name.
Ask the customer to approve the wording and placement shown in that replacement. If a requested change also affects layout, identify it explicitly. A longer name can change the visual balance even when the customer only intended a spelling correction.
Release the right file
Place the approved revision beside the job record and mark who checked it. If an old export remains in the working folder, make its obsolete status unmistakable. Treat any later message changing the design as a new review event. This paperwork habit cannot guarantee a finished result, but it makes the intended version traceable before sample work begins.
Explore related preparation notes at /updates/.