aboutsummaryrefslogtreecommitdiff
path: root/docs/faq_keymap.md
diff options
context:
space:
mode:
authorjack <jack@pngu.org>2024-09-06 10:30:54 -0600
committerGitHub <noreply@github.com>2024-09-06 17:30:54 +0100
commitf0435451446621a0e768c8a9123789b239a325b4 (patch)
tree2edd6213e016497e5e962de52892e197d84ee282 /docs/faq_keymap.md
parentc44f5375ab6aa3ad98d48a8a32a973f8fe6ad20b (diff)
downloadqmk_firmware-f0435451446621a0e768c8a9123789b239a325b4.tar.gz
qmk_firmware-f0435451446621a0e768c8a9123789b239a325b4.zip
[Docs] Remove references to bootmagic lite (#24369)
Diffstat (limited to 'docs/faq_keymap.md')
-rw-r--r--docs/faq_keymap.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq_keymap.md b/docs/faq_keymap.md
index 56ccc6f6cc..05bd4fed3e 100644
--- a/docs/faq_keymap.md
+++ b/docs/faq_keymap.md
@@ -34,7 +34,7 @@ On first run, the VIA code in the firmware will copy the keymap from flash memor
The simple fix for this is to clear the EEPROM. You can do this in several ways:
-* Hold the Bootmagic Lite key (usually top left/Escape) while plugging the board in, which will also place the board into bootloader mode; then unplug and replug the board.
+* Hold the Bootmagic key (usually top left/Escape) while plugging the board in, which will also place the board into bootloader mode; then unplug and replug the board.
* Press the `QK_CLEAR_EEPROM`/`EE_CLR` keycode if it is accessible on your keymap.
* Place the board into bootloader mode and hit the "Clear EEPROM" button. This may not be available for all bootloaders, and you may need to reflash the board afterwards.