diff options
| author | fauxpark <fauxpark@gmail.com> | 2017-12-09 16:36:32 +1100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-12-09 10:46:11 -0500 |
| commit | 7b0356d1d49da6574570e110f61f95692afdb3d0 (patch) | |
| tree | a3e70802085ea8089f1e7851529f0296247fa264 /docs/faq_general.md | |
| parent | 6eb89ae906db7f226570e1839b88dcdd3a8fa962 (diff) | |
| download | qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.gz qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.zip | |
Convert all headings to Title Case
Diffstat (limited to 'docs/faq_general.md')
| -rw-r--r-- | docs/faq_general.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/faq_general.md b/docs/faq_general.md index 7647b1c2a..e0d8c69f2 100644 --- a/docs/faq_general.md +++ b/docs/faq_general.md | |||
| @@ -4,7 +4,7 @@ | |||
| 4 | 4 | ||
| 5 | [QMK](https://github.com/qmk), short for Quantum Mechanical Keyboard, is a group of people building tools for custom keyboards. We started with the [QMK firmware](https://github.com/qmk/qmk_firmware), a heavily modified fork of [TMK](https://github.com/tmk/tmk_keyboard). | 5 | [QMK](https://github.com/qmk), short for Quantum Mechanical Keyboard, is a group of people building tools for custom keyboards. We started with the [QMK firmware](https://github.com/qmk/qmk_firmware), a heavily modified fork of [TMK](https://github.com/tmk/tmk_keyboard). |
| 6 | 6 | ||
| 7 | ### Why the name Quantum? | 7 | ### Why the Name Quantum? |
| 8 | 8 | ||
| 9 | <!-- FIXME --> | 9 | <!-- FIXME --> |
| 10 | 10 | ||
| @@ -17,4 +17,3 @@ From a technical standpoint QMK builds upon TMK by adding several new features. | |||
| 17 | From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follow the quality standards. These are mostly community maintained, but the QMK team also helps when necessary. | 17 | From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follow the quality standards. These are mostly community maintained, but the QMK team also helps when necessary. |
| 18 | 18 | ||
| 19 | Both approaches have their merits and their drawbacks, and code flows freely between TMK and QMK when it makes sense. | 19 | Both approaches have their merits and their drawbacks, and code flows freely between TMK and QMK when it makes sense. |
| 20 | |||
