aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJ <[email protected]>2024-12-22 15:23:14 -0500
committerGitHub <[email protected]>2024-12-22 12:23:14 -0800
commit58807b02887c116a22f860cd80d5b94ddd77122b (patch)
tree9ab2a6c6cad333aa220e20a5971c4f77fff1cc99 /docs
parent9877af9bf8967ade2a3d1ed752bb3faa52185ecb (diff)
downloadqmk_firmware-58807b02887c116a22f860cd80d5b94ddd77122b.tar.gz
qmk_firmware-58807b02887c116a22f860cd80d5b94ddd77122b.zip
Clarify keymap location and format in newbs_building_firmware.md (#24663)
Diffstat (limited to 'docs')
-rw-r--r--docs/newbs_building_firmware.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_building_firmware.md b/docs/newbs_building_firmware.md
index f3afd6a896..f5e529b9ce 100644
--- a/docs/newbs_building_firmware.md
+++ b/docs/newbs_building_firmware.md
@@ -42,7 +42,7 @@ Look at the output from that command, you should see something like this:
Ψ Created a new keymap called <github_username> in: /home/me/qmk_firmware/keyboards/clueboard/66/rev3/keymaps/<github_username>.
```
-This is the location of your new `keymap.c` file.
+This is the location of your new keymap file. Your keyboards default keymap file may be a `.json` file or a `.c` file. If your keymap is a `.json` file it can be converted to a `.c` file using QMK's [`json2c`](cli_commands#qmk-json2c) utility.
## Open `keymap.c` In Your Favorite Text Editor