summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorHawley Waldman <321077+hjw@users.noreply.github.com>2021-04-11 06:45:30 -0400
committerGitHub <noreply@github.com>2021-04-11 12:45:30 +0200
commit98939868fae77ecb96674d07bd71dea78d726104 (patch)
tree5e8e83bdd18996f40cc70ae5bb2a1e7c1b627995 /docs
parent7daa2e210cc7fc121259535d724962c9896c5f3a (diff)
Update github instruction link in newbs_getting_started.md (#12510)
Clarify that the link to the github/forking instructions is a link to how to fork this project. Previous wording implied that the link was to a how-to-use github in general page.
Diffstat (limited to 'docs')
-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