[PATCH v4 6/8] doc: gitrevisions - clarify 'latter case' is revision walk

From: Philip Oakley <philipoakley@iee.org>
Date: Jul 20, 2016, 21:10 UTC
Message-ID: <20160720211007.5520-7-philipoakley@iee.org>
In-Reply-To: <20160720211007.5520-1-philipoakley@iee.org>

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>
---
 Documentation/gitrevisions.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/gitrevisions.txt b/Documentation/gitrevisions.txt
index 33039c6..27dec5b 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

-- 
2.9.0.windows.1