From 5a38af6632e4524a3e7f8080c553512c80ffbd99 Mon Sep 17 00:00:00 2001
From: moritz-john <70295002+moritz-john@users.noreply.github.com>
Date: Sun, 12 Feb 2023 20:42:53 +0100
Subject: [PATCH] Update docs/en/extension_stringy_keymaps.md

Co-authored-by: xs5871 <60395129+xs5871@users.noreply.github.com>
---
 docs/en/extension_stringy_keymaps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/extension_stringy_keymaps.md b/docs/en/extension_stringy_keymaps.md
index 017f28d..7d8777f 100644
--- a/docs/en/extension_stringy_keymaps.md
+++ b/docs/en/extension_stringy_keymaps.md
@@ -32,4 +32,4 @@ keyboard.extensions.append(stringyKeymaps)
 It should be noted that these are **not** ASCII. The string is **not** what
 will be sent to the computer. The examples above have no functional difference.
 
-When utilizing layer keycodes, such as `KC.MO(layer)`, it's not possible to use a string like `'MO(layer)'` instead employ the standard notation of e.g. `KC.MO(1)` in your keymap.
\ No newline at end of file
+When utilizing argumented keys, such as `KC.MO(layer)`, it's not possible to use a string like `'MO(layer)'` instead employ the standard notation of e.g. `KC.MO(1)` in your keymap.
\ No newline at end of file