summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2021-04-11 10:45:56 +0000
committerQMK Bot <hello@qmk.fm>2021-04-11 10:45:56 +0000
commitc9d7a4af45f776d80428f9f0a8f3a86f9f21be24 (patch)
tree8e38eebc76c1995540c195386bee632cb7b1957e
parent34323ecd8b4daa37723d662e2af84a6b81f3d618 (diff)
parent98939868fae77ecb96674d07bd71dea78d726104 (diff)
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r--docs/newbs_getting_started.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md
index 7af9579dfb..ff8337f382 100644
--- a/docs/newbs_getting_started.md
+++ b/docs/newbs_getting_started.md
@@ -172,7 +172,7 @@ Once that completes, re-run `qmk setup` to complete the setup and checks.
?> The qmk home folder can be specified at setup with `qmk setup -H <path>`, and modified afterwards using the [cli configuration](cli_configuration.md?id=single-key-example) and the variable `user.qmk_home`. For all available options run `qmk setup --help`.
-?> If you already know [how to use GitHub](getting_started_github.md), we recommend that you create your own fork and use `qmk setup <github_username>/qmk_firmware` to clone your personal fork. If you don't know what that means you can safely ignore this message.
+?> If you already know how to use GitHub, [we recommend that you follow these instructions](getting_started_github.md) and use `qmk setup <github_username>/qmk_firmware` to clone your personal fork. If you don't know what that means you can safely ignore this message.
## 4. Test Your Build Environment