manpages: italicize git command names (which were in teletype font)

[thirdparty/git.git] / Documentation / git-send-pack.txt

diff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt
index 410504df4630bb9fe5d6b2582f0e2c3a0d3ae150..399821832c2a5cd6a718a7dc37a87e6b5bc0b213 100644 (file)
--- a/Documentation/git-send-pack.txt
+++ b/Documentation/git-send-pack.txt
@@ -12,17 +12,17 @@ SYNOPSIS
 
 DESCRIPTION
 -----------
-Usually you would want to use `git-push`, which is a
+Usually you would want to use 'git-push', which is a
 higher-level wrapper of this command, instead. See linkgit:git-push[1].
 
-Invokes `git-receive-pack` on a possibly remote repository, and
+Invokes 'git-receive-pack' on a possibly remote repository, and
 updates it from the current repository, sending named refs.
 
 
 OPTIONS
 -------
 --receive-pack=<git-receive-pack>::
-       Path to the `git-receive-pack` program on the remote
+       Path to the 'git-receive-pack' program on the remote
        end.  Sometimes useful when pushing to a remote
        repository over ssh, and you do not have the program in
        a directory on the default $PATH.
@@ -53,7 +53,7 @@ OPTIONS
 
 <host>::
        A remote host to house the repository.  When this
-       part is specified, `git-receive-pack` is invoked via
+       part is specified, 'git-receive-pack' is invoked via
        ssh.
 
 <directory>::
@@ -86,7 +86,7 @@ and the destination side (after the colon).  The ref to be
 pushed is determined by finding a match that matches the source
 side, and where it is pushed is determined by using the
 destination side. The rules used to match a ref are the same
-rules used by `git-rev-parse` to resolve a symbolic ref
+rules used by 'git-rev-parse' to resolve a symbolic ref
 name. See linkgit:git-rev-parse[1].
 
  - It is an error if <src> does not match exactly one of the