From ffacf7405f949dcbed628aaef5a52c692ffa2acb Mon Sep 17 00:00:00 2001
From: prxnvt <53838599+prxnvt@users.noreply.github.com>
Date: Sun, 25 Oct 2026 04:14:24 -0400
Subject: [PATCH] Docs: Record Macro's shortcut example uses a letter a macro
 may take

The example was K, which GridCraft uses (Group), so a caller who copied it was refused; it is M
now, in the command's description and on the macro page.
---
 crates/engine/src/cmd/macros.rs | 2 +-
 docs/macros.md                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/crates/engine/src/cmd/macros.rs b/crates/engine/src/cmd/macros.rs
index f75cee6ef..6d1cdf08a 100644
--- a/crates/engine/src/cmd/macros.rs
+++ b/crates/engine/src/cmd/macros.rs
@@ -46,7 +46,7 @@ pub fn specs() -> Vec<CommandSpec> {
             "Record Macro",
             ["View", "Macros"],
             None,
-            "{stop?: bool, cancel?: bool (ends a recording without saving it), relative?: bool (default true; when starting), name?, shortcut?: \"Ctrl+Shift+K\" | \"K\", description?} toggles recording; when starting, the name (new and valid) and the shortcut (free) are checked and kept for the save, and without a name the macro gets the next MacroN; when stopping, a name or description given then wins (a taken name gets a suffix); with relative references the selection when it starts is the example input → {recording, name?, relative?, input?} or {recording: false, saved, steps, dropped, skipped, inputs, shortcutDropped? (the shortcut another macro took while recording)}",
+            "{stop?: bool, cancel?: bool (ends a recording without saving it), relative?: bool (default true; when starting), name?, shortcut?: \"Ctrl+Shift+M\" | \"M\", description?} toggles recording; when starting, the name (new and valid) and the shortcut (free) are checked and kept for the save, and without a name the macro gets the next MacroN; when stopping, a name or description given then wins (a taken name gets a suffix); with relative references the selection when it starts is the example input → {recording, name?, relative?, input?} or {recording: false, saved, steps, dropped, skipped, inputs, shortcutDropped? (the shortcut another macro took while recording)}",
             has_doc,
             record
         ),
diff --git a/docs/macros.md b/docs/macros.md
index 5018975d6..3335b5ecc 100644
--- a/docs/macros.md
+++ b/docs/macros.md
@@ -196,7 +196,7 @@ on its own, never as a step of a script or macro, and is never recorded.
 
 `macro.record` toggles recording. Starting takes `relative` (default true; `false` for absolute
 references) and, from the Record Macro dialog, `name`, `shortcut` and `description`: the macro's
-name, its Ctrl+Shift shortcut letter (`"Ctrl+Shift+K"` or `"K"`) and its description. They are
+name, its Ctrl+Shift shortcut letter (`"Ctrl+Shift+M"` or `"M"`) and its description. They are
 checked at once, so a name that is taken (a kept one included), too long or holds line breaks, or a
 letter that GridCraft or another macro uses, is refused before anything is recorded. Without a name
 the macro is called `Macro1`, `Macro2` and so on. A `name` or `description` given when stopping wins