diff options
| author | Joel Challis <git@zvecr.com> | 2022-09-15 01:03:55 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-15 01:03:55 +0100 |
| commit | 01f31bf28ebcb5721229697c93dc6e0b2d5b66d7 (patch) | |
| tree | bf1a28b41008be13a52a4a871c34ce594916d791 /docs/faq_misc.md | |
| parent | 0abde386ae46600d0ac12b13a480c060e3292bd9 (diff) | |
[Docs] RESET -> QK_BOOT (#18365)
Diffstat (limited to 'docs/faq_misc.md')
| -rw-r--r-- | docs/faq_misc.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq_misc.md b/docs/faq_misc.md index 9e34a04815..287ca7711d 100644 --- a/docs/faq_misc.md +++ b/docs/faq_misc.md @@ -10,7 +10,7 @@ You probably don't want to "brick" your keyboard, making it impossible to rewrite firmware onto it. Here are some of the parameters to show what things are (and likely aren't) too risky. -- If your keyboard map does not include RESET, then, to get into DFU +- If your keyboard map does not include QK_BOOT, then, to get into DFU mode, you will need to press the reset button on the PCB, which requires unscrewing the bottom. - Messing with tmk_core / common files might make the keyboard |