summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-05-10 20:40:31 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-05-10 20:40:32 (GMT)
commit5a2906812b815ac129f9d324bd132edc045b5329 (patch)
tree4ed8ddaf1fabb2c44ec25e6f573d3512df086af2 /Documentation
parentd5e0d54319ef1941d349719bd253805987ebe19a (diff)
parent2e39a246071eb7bc9153e48e0c9416f069ac2a17 (diff)
downloadgit-5a2906812b815ac129f9d324bd132edc045b5329.zip
git-5a2906812b815ac129f9d324bd132edc045b5329.tar.gz
git-5a2906812b815ac129f9d324bd132edc045b5329.tar.bz2
Merge branch 'rn/glossary-typofix'
* rn/glossary-typofix: Documentation: fix typo 'In such these cases'
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/glossary-content.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index cafc284..8ad29e6 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -145,7 +145,7 @@ current branch integrates with) obviously do not work, as there is no
A fast-forward is a special type of <<def_merge,merge>> where you have a
<<def_revision,revision>> and you are "merging" another
<<def_branch,branch>>'s changes that happen to be a descendant of what
- you have. In such these cases, you do not make a new <<def_merge,merge>>
+ you have. In such a case, you do not make a new <<def_merge,merge>>
<<def_commit,commit>> but instead just update to his
revision. This will happen frequently on a
<<def_remote_tracking_branch,remote-tracking branch>> of a remote