diff options
| author | Ryan <fauxpark@gmail.com> | 2020-05-26 12:43:14 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-25 19:43:14 -0700 |
| commit | e4823aadec24bca0ecfd1184562d27a49fd20544 (patch) | |
| tree | 66699e086fdd4b6c87bf2f83f4fae74c4e8ecded /docs/configurator_step_by_step.md | |
| parent | 5c9906eb4fc569cd08d88dcd85ce9afaa5410ffb (diff) | |
| download | firmware-e4823aadec24bca0ecfd1184562d27a49fd20544.tar.gz firmware-e4823aadec24bca0ecfd1184562d27a49fd20544.tar.bz2 firmware-e4823aadec24bca0ecfd1184562d27a49fd20544.zip | |
Fix capitalisation of "GitHub" (#9184)
Diffstat (limited to 'docs/configurator_step_by_step.md')
| -rw-r--r-- | docs/configurator_step_by_step.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/configurator_step_by_step.md b/docs/configurator_step_by_step.md index aee1d4e1f..965012a90 100644 --- a/docs/configurator_step_by_step.md +++ b/docs/configurator_step_by_step.md @@ -12,7 +12,7 @@ I'll say that again because it's important: !> **MAKE SURE YOU SELECT THE RIGHT VERSION!** -If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own github accounts. Double check for that as well. <!-- FIXME(skullydazed): This feels too wordy and I'm not sure we want to encourage these kinds of issues. Also, should we prompt them to bug the manufacutrer? --> +If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own GitHub accounts. Double check for that as well. <!-- FIXME(skullydazed): This feels too wordy and I'm not sure we want to encourage these kinds of issues. Also, should we prompt them to bug the manufacutrer? --> ## Step 2: Select Your Keyboard Layout |