diff options
| author | Kevin <chenkevinh11@gmail.com> | 2020-08-29 17:47:41 -0700 |
|---|---|---|
| committer | Kevin <chenkevinh11@gmail.com> | 2020-08-29 17:47:41 -0700 |
| commit | 276a2620b9a5259dd15cd4a6038a6144e5da9432 (patch) | |
| tree | fa5e0bbdefa58d0b50008a9aed3f6494972e9cd4 | |
| parent | dad2d339b3fa038af1b87cdb60b79081d681a6c3 (diff) | |
Minor capitalization fix
| -rw-r--r-- | docs/docs/feature/keymaps.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docs/feature/keymaps.md b/docs/docs/feature/keymaps.md index 367b03c..d991925 100644 --- a/docs/docs/feature/keymaps.md +++ b/docs/docs/feature/keymaps.md @@ -80,7 +80,7 @@ A keymap file is composed of several sections, that together make up a valid dev ### Includes -THe devicetree files are actually preprocessed before being finally leveraged by Zephyr. This allows using standard C defines to create meaningful placeholders +The devicetree files are actually preprocessed before being finally leveraged by Zephyr. This allows using standard C defines to create meaningful placeholders for what would otherwise be cryptic integer keycodes, etc. This also allows bringing in _other_ devicetree nodes from separate files. The top two lines of most keymaps should include: |