summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTakeshi ISHII <2170248+mtei@users.noreply.github.com>2019-12-28 07:31:23 +0900
committerJames Young <18669334+noroadsleft@users.noreply.github.com>2019-12-27 14:31:23 -0800
commit26a823082b17ee30aa8a0c5e39a32d854449ce15 (patch)
tree4e7824ebb52ee7445e44ef96421732158f53b551
parent80e73b6210dbcd3bf48c72006df935661435c43d (diff)
downloadqmk_firmware-26a823082b17ee30aa8a0c5e39a32d854449ce15.tar.gz
qmk_firmware-26a823082b17ee30aa8a0c5e39a32d854449ce15.zip
[Docs] Fix minor differences in docs/newbs_git_resynchronize_a_branch.md (#7728)
-rw-r--r--docs/newbs_git_resynchronize_a_branch.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_git_resynchronize_a_branch.md b/docs/newbs_git_resynchronize_a_branch.md
index 2e6b26e094..3e7acdba7a 100644
--- a/docs/newbs_git_resynchronize_a_branch.md
+++ b/docs/newbs_git_resynchronize_a_branch.md
@@ -1,6 +1,6 @@
# Resynchronizing an Out-of-Sync Git Branch
-Suppose you have committed to your `master` branch, and now need to update your QMK repository. You could `git pull` QMK's `master` branch into your own, but GitHub will tell you that your commit is a number of commits ahead of `qmk:master`, which can create issues if you want to make a pull request to QMK.
+Suppose you have committed to your `master` branch, and now need to update your QMK repository. You could `git pull` QMK's `master` branch into your own, but GitHub will tell you that your branch is a number of commits ahead of `qmk:master`, which can create issues if you want to make a pull request to QMK.
?> This document builds upon the concepts detailed in [Your Fork's Master: Update Often, Commit Never](newbs_git_using_your_master_branch.md). If you are not familiar with that document, please read it first, then return here.