summaryrefslogtreecommitdiff
path: root/Documentation/gittutorial.txt
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@uchicago.edu>2008-07-03 00:49:55 -0500
committerJunio C Hamano <gitster@pobox.com>2008-07-05 11:24:40 -0700
commit42d36bb841eb035eb0f7261f02987893c14e1a02 (patch)
tree08fb3a348d090e9465f3d323034754ed728016b2 /Documentation/gittutorial.txt
parentba020ef5eb5fca3d757bd580ff117adaf81ca079 (diff)
downloadgit-42d36bb841eb035eb0f7261f02987893c14e1a02.tar.gz
manpages: italicize gitk's name (where it was in teletype font)
The name `gitk` is sometimes meant to be entered at the command prompt, but most uses are just referring to the program with that name (not the incantation to start it). Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/gittutorial.txt')
-rw-r--r--Documentation/gittutorial.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index 2c4346c9e8..e71b561172 100644
--- a/Documentation/gittutorial.txt
+++ b/Documentation/gittutorial.txt
@@ -529,7 +529,7 @@ then merged back together, the order in which 'git-log' presents
those commits is meaningless.
Most projects with multiple contributors (such as the linux kernel,
-or git itself) have frequent merges, and `gitk` does a better job of
+or git itself) have frequent merges, and 'gitk' does a better job of
visualizing their history. For example,
-------------------------------------