path: root/Documentation/gitcore-tutorial.txt
diff options
authorJonathan Nieder <>2008-07-03 05:59:09 (GMT)
committerJunio C Hamano <>2008-07-05 18:24:40 (GMT)
commit5833d730efb7131bccbcdcab13ba56707629be2c (patch)
tree9e0299412247a17143904ea28c6642ceac073b44 /Documentation/gitcore-tutorial.txt
parent2fd02c92dbb6e575b7e62ea9dfa85ef45ebe58b6 (diff)
manpages: italicize git subcommand names (which were in teletype font)
Italicize those git subcommand names already in teletype we missed. Signed-off-by: Jonathan Nieder <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/gitcore-tutorial.txt')
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index 5acdeb7..dd6a268 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -235,7 +235,7 @@ $ git diff-files
Oops. That wasn't very readable. It just spit out its own internal
-version of a `diff`, but that internal version really just tells you
+version of a 'diff', but that internal version really just tells you
that it has noticed that "hello" has been modified, and that the old object
contents it had have been replaced with something else.
@@ -468,7 +468,7 @@ Inspecting Changes
While creating changes is useful, it's even more useful if you can tell
later what changed. The most useful command for this is another of the
-`diff` family, namely 'git-diff-tree'.
+'diff' family, namely 'git-diff-tree'.
'git-diff-tree' can be given two arbitrary trees, and it will tell you the
differences between them. Perhaps even more commonly, though, you can
@@ -1006,7 +1006,7 @@ the tree of your branch to that of the `master` branch. This is
often called 'fast forward' merge.
You can run `gitk \--all` again to see how the commit ancestry
-looks like, or run `show-branch`, which tells you this.
+looks like, or run 'show-branch', which tells you this.
$ git show-branch master mybranch