aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/git-reset.txt
diff options
context:
space:
mode:
authorDenton Liu <liu.denton@gmail.com>2019-03-05 15:34:26 -0800
committerJunio C Hamano <gitster@pobox.com>2019-03-06 08:46:54 +0900
commit56cb2d30f8412630b94cbb478272abc3e59488d2 (patch)
treea801ef3fa2a159f5395c87e4dad7cddf62837fa9 /Documentation/git-reset.txt
parent0d0ac3826a3bbb9247e39e12623bbcfdd722f24c (diff)
downloadgit-56cb2d30f8412630b94cbb478272abc3e59488d2.tar.gz
git-reset.txt: clarify documentation
git-reset.txt contained a missing "a" and "wrt". Fix the missing "a" for correctness and replace "wrt" with "with respect to" so that the documentation is not so cryptic. Signed-off-by: Denton Liu <liu.denton@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-reset.txt')
-rw-r--r--Documentation/git-reset.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index 9f69ae8b69..17cbd2fccc 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt
@@ -428,8 +428,8 @@ working index HEAD target working index HEAD
`reset --merge` is meant to be used when resetting out of a conflicted
merge. Any mergy operation guarantees that the working tree file that is
-involved in the merge does not have local change wrt the index before
-it starts, and that it writes the result out to the working tree. So if
+involved in the merge does not have a local change with respect to the index
+before it starts, and that it writes the result out to the working tree. So if
we see some difference between the index and the target and also
between the index and the working tree, then it means that we are not
resetting out from a state that a mergy operation left after failing