summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Philip Oakley <philipoakley@iee.org>2016-08-12 08:07:45 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-08-13 19:36:44 -0700
commit8cf5739426637e43b881aed2a0e9a9fd18e9b245 (patch)
tree1f809ff2aabda9ca04e18b37a317acba3f63eb55 /Documentation
parentdoc: gitrevisions - use 'reachable' in page description (diff)
downloadtgif-8cf5739426637e43b881aed2a0e9a9fd18e9b245.tar.xz
doc: gitrevisions - clarify 'latter case' is revision walk
The prior sentence has too many clauses for easy parsing. Replace 'the latter case' with a direct quote. Signed-off-by: Philip Oakley <philipoakley@iee.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/gitrevisions.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/gitrevisions.txt b/Documentation/gitrevisions.txt
index 33039c6228..27dec5b91d 100644
--- a/Documentation/gitrevisions.txt
+++ b/Documentation/gitrevisions.txt
@@ -16,8 +16,8 @@ DESCRIPTION
Many Git commands take revision parameters as arguments. Depending on
the command, they denote a specific commit or, for commands which
walk the revision graph (such as linkgit:git-log[1]), all commits which are
-reachable from that commit. In the latter case one can also specify a
-range of revisions explicitly.
+reachable from that commit. For commands that walk the revision graph one can
+also specify a range of revisions explicitly.
In addition, some Git commands (such as linkgit:git-show[1]) also take
revision parameters which denote other objects than commits, e.g. blobs