From 87eaab600c47441651d864a45818b5fcc7e46a26 Mon Sep 17 00:00:00 2001
From: atti
Date: Wed, 6 Dec 2023 04:06:06 +0900
Subject: Fixed non-executable codes in the documentation (#22600)

---
 docs/tap_hold.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/tap_hold.md')

diff --git a/docs/tap_hold.md b/docs/tap_hold.md
index 094a10753a..18c90c6932 100644
--- a/docs/tap_hold.md
+++ b/docs/tap_hold.md
@@ -493,7 +493,7 @@ Examples:
 
 One thing that you may notice is that we include the key record for all of the "per key" functions, and may be wondering why we do that.
 
-Well, it's simple really: customization.  But specifically, it depends on how your keyboard is wired up.  For instance, if each row is actually using a row in the keyboard's matrix, then it may be simpler to use `if (record->event.row == 3)` instead of checking a whole bunch of keycodes.  Which is especially good for those people using the Tap Hold type keys on the home row. So you could fine-tune those to not interfere with your normal typing.
+Well, it's simple really: customization.  But specifically, it depends on how your keyboard is wired up.  For instance, if each row is actually using a row in the keyboard's matrix, then it may be simpler to use `if (record->event.key.row == 3)` instead of checking a whole bunch of keycodes.  Which is especially good for those people using the Tap Hold type keys on the home row. So you could fine-tune those to not interfere with your normal typing.
 
 ## Why are there no `*_kb` or `*_user` functions?!
 
-- 
cgit v1.2.3