From 17ae28f0e41aa30937d80e48dc19548c76cc6e43 Mon Sep 17 00:00:00 2001
From: Yanfei Guo <yanf.guo@gmail.com>
Date: Tue, 26 Sep 2023 01:17:20 -0500
Subject: [PATCH] Fix doc for programmable buttons. (#22136)

Co-authored-by: Yanfei Guo <yguo@anl.gov>
---
 docs/feature_programmable_button.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/feature_programmable_button.md b/docs/feature_programmable_button.md
index 43a9e7fc16..091464e19c 100644
--- a/docs/feature_programmable_button.md
+++ b/docs/feature_programmable_button.md
@@ -2,7 +2,7 @@
 
 Programmable Buttons are keys that have no predefined meaning. This means they can be processed on the host side by custom software without the operating system trying to interpret them.
 
-The keycodes are emitted according to the HID Telephony Device page (`0x0B`), Programmable Button usage (`0x07`). On Linux (> 5.14) they are handled automatically and translated to `KEY_MACRO#` keycodes (up to `KEY_MACRO30`).
+The keycodes are emitted according to the HID Telephony Device page (`0x0B`), Programmable Button usage (`0x09`). On Linux (> 5.14) they are handled automatically and translated to `KEY_MACRO#` keycodes (up to `KEY_MACRO30`).
 
 ?> Currently there is no known support in Windows or macOS. It may be possible to write a custom HID driver to receive these usages, but this is out of the scope of the QMK documentation.