diff --git a/atvm/AGENTS.md b/atvm/AGENTS.md
index c63386b..645d996 100644
--- a/atvm/AGENTS.md
+++ b/atvm/AGENTS.md
@@ -101,7 +101,7 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
 - Before reporting a categorized grouped sub-run as `PASS`, confirm that the matching child batch also passed in the live launch log or the final `Cloud Run Finished` summary for that child run.
 - If the operator asks for ATVM run status without mentioning Mattermost, respond locally only and do not post externally.
 - If the operator asks to send ATVM run status to Mattermost, use `MATTERMOST_ATVM_WEBHOOK` and `MATTERMOST_ATVM_CHANNEL` from `/home/aw/code/cds/.env.credentials.local` by default and send the final status only after the run has fully completed, whether the run passed or failed.
-- For vCenter VM snapshot requests, default the snapshot name to `VM Snapshot [m/d/yyyy], [h:mm:ss AM/PM]` in the local `America/New_York` timezone unless the operator explicitly requests a different name.
+- For vCenter VM snapshot requests, default the snapshot name to `VM Snapshot [mm/dd/yyyy:hh:mm:ss AM/PM]` in the local `America/New_York` timezone unless the operator explicitly requests a different name.
 - For VM power, shutdown, startup, snapshot, or maintenance requests, operate only on the exact VM names provided by the operator.
 - If any requested VM name is missing or not found, stop immediately and report the missing names; do not infer, substitute, or search for replacement VMs unless the operator explicitly requests a discovery/mapping step.
 - For `atvm_prep` requests, infer common option values from operator shorthand when intent is clear.