Documentation: prepare to be consistent about "git-" versus "git "

With the dashed forms of git commands not in $(bindir), we have
to change many instances of "git-command" to "git command". Also,
for consistency it is at times appropriate to make the opposite
change. In some cases, the change is not so simple as changing one
character.

This patch gets rid of some of those cases by rewrapping lines.

Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

Documentation/git-mailinfo.txt

@@ -29,8 +29,8 @@ OPTIONS
 	among which (1) remove 'Re:' or 're:', (2) leading
 	whitespaces, (3) '[' up to ']', typically '[PATCH]', and
 	then prepends "[PATCH] ".  This flag forbids this
-	munging, and is most useful when used to read back 'git
+	munging, and is most useful when used to read back
-	format-patch -k' output.
+	'git format-patch -k' output.
 
 -u::
 	The commit log message, author name and author email are

Documentation/git-tag.txt

@@ -122,8 +122,8 @@ others have already seen the old one. So just use "git tag -f"
 again, as if you hadn't already published the old one.
 
 However, Git does *not* (and it should not) change tags behind
-users back. So if somebody already got the old tag, doing a "git
+users back. So if somebody already got the old tag, doing a
-pull" on your tree shouldn't just make them overwrite the old
+"git pull" on your tree shouldn't just make them overwrite the old
 one.
 
 If somebody got a release tag from you, you cannot just change

Documentation/gitrepository-layout.txt

@@ -167,14 +167,14 @@ info/grafts::
 info/exclude::
 	This file, by convention among Porcelains, stores the
 	exclude pattern list. `.gitignore` is the per-directory
-	ignore file.  `git status`, `git add`, `git rm` and `git
+	ignore file.  `git status`, `git add`, `git rm` and
-	clean` look at it but the core git commands do not look
+	`git clean` look at it but the core git commands do not look
 	at it.  See also: linkgit:gitignore[5].
 
 remotes::
 	Stores shorthands to be used to give URL and default
-	refnames to interact with remote repository to `git
+	refnames to interact with remote repository to
-	fetch`, `git pull` and `git push` commands.
+	`git fetch`, `git pull` and `git push` commands.
 
 logs::
 	Records of changes made to refs are stored in this

Documentation/gittutorial.txt

@@ -19,8 +19,8 @@ If you are instead primarily interested in using git to fetch a project,
 for example, to test the latest version, you may prefer to start with
 the first two chapters of link:user-manual.html[The Git User's Manual].
 
-First, note that you can get documentation for a command such as "git
+First, note that you can get documentation for a command such as
-log --graph" with:
+"git log --graph" with:
 
 ------------------------------------------------
 $ man git-log