Merge pull request #644 from ben4ever/fix_format

Format various git commands with code formatting

Author: ben

book/04-git-server/sections/gitlab.asc

@@ -75,7 +75,7 @@ If the project belongs to a user, the owner of the project has direct control ov
 Every project also has a visibility level, which controls who has read access to that project's pages and repository.
 If a project is _Private_, the project's owner must explicitly grant access to specific users.
 An _Internal_ project is visible to any logged-in user, and a _Public_ project is visible to anyone.
-Note that this controls both git ``fetch'' access as well as access to the web UI for that project.
+Note that this controls both `git fetch` access as well as access to the web UI for that project.
 
 ===== Hooks
 

book/05-distributed-git/sections/maintaining.asc

@@ -87,10 +87,10 @@ Subject: [PATCH 1/2] add limit to log function
 Limit log functionality to the first 20
 ----
 
-This is the beginning of the output of the format-patch command that you saw in the previous section.
+This is the beginning of the output of the `format-patch` command that you saw in the previous section.
 This is also a valid mbox email format.
-If someone has emailed you the patch properly using git send-email, and you download that into an mbox format, then you can point git am to that mbox file, and it will start applying all the patches it sees.
-If you run a mail client that can save several emails out in mbox format, you can save entire patch series into a file and then use git am to apply them one at a time.
+If someone has emailed you the patch properly using `git send-email`, and you download that into an mbox format, then you can point `git am` to that mbox file, and it will start applying all the patches it sees.
+If you run a mail client that can save several emails out in mbox format, you can save entire patch series into a file and then use `git am` to apply them one at a time.
 
 However, if someone uploaded a patch file generated via `format-patch` to a ticketing system or something similar, you can save the file locally and then pass that file saved on your disk to `git am` to apply it:
 

book/08-customizing-git/sections/attributes.asc

@@ -294,7 +294,7 @@ You can add the following line to your Git attributes file:
 test/ export-ignore
 ----
 
-Now, when you run git archive to create a tarball of your project, that directory won't be included in the archive.
+Now, when you run `git archive` to create a tarball of your project, that directory won't be included in the archive.
 
 ===== `export-subst`
 
@@ -324,7 +324,7 @@ $ cat ../deployment-testing/LAST_COMMIT
 Last commit date: Tue Apr 21 08:38:48 2009 -0700 by Scott Chacon
 ----
 
-The substitutions can include for example the commit message and any git notes, and git log can do simple word wrapping:
+The substitutions can include for example the commit message and any `git notes`, and `git log` can do simple word wrapping:
 
 [source,console]
 ----

book/09-git-and-other-scms/sections/client-svn.asc

@@ -338,7 +338,7 @@ When someone else clones that work, all they see is the merge commit with all th
 ===== Subversion Branching
 
 Branching in Subversion isn't the same as branching in Git; if you can avoid using it much, that's probably best.
-However, you can create and commit to branches in Subversion using git svn.
+However, you can create and commit to branches in Subversion using `git svn`.
 
 ===== Creating a New SVN Branch
 

book/09-git-and-other-scms/sections/import-custom.asc

@@ -31,7 +31,7 @@ Your strategy will be to go through the snapshots one at a time and create commi
 
 As we did in <<_an_example_git_enforced_policy>>, we'll write this in Ruby, because it's what we generally work with and it tends to be easy to read.
 You can write this example pretty easily in anything you're familiar with – it just needs to print the appropriate information to `stdout`.
-And, if you are running on Windows, this means you'll need to take special care to not introduce carriage returns at the end your lines – git fast-import is very particular about just wanting line feeds (LF) not the carriage return line feeds (CRLF) that Windows uses.
+And, if you are running on Windows, this means you'll need to take special care to not introduce carriage returns at the end your lines – `git fast-import` is very particular about just wanting line feeds (LF) not the carriage return line feeds (CRLF) that Windows uses.
 
 To begin, you'll change into the target directory and identify every subdirectory, each of which is a snapshot that you want to import as a commit.
 You'll change into each subdirectory and print the commands necessary to export it.
@@ -192,8 +192,8 @@ return mark
 [NOTE]
 ====
 If you are running on Windows you'll need to make sure that you add one extra step.
-As mentioned before, Windows uses CRLF for new line characters while git fast-import expects only LF.
-To get around this problem and make git fast-import happy, you need to tell ruby to use LF instead of CRLF:
+As mentioned before, Windows uses CRLF for new line characters while `git fast-import` expects only LF.
+To get around this problem and make `git fast-import` happy, you need to tell ruby to use LF instead of CRLF:
 
 [source,ruby]
 ----

book/10-git-internals/sections/environment.asc

@@ -176,7 +176,7 @@ $ GIT_TRACE_PACKET=true git ls-remote origin
 ----
 
 *`GIT_TRACE_PERFORMANCE`* controls logging of performance data.
-The output shows how long each particular git invocation takes.
+The output shows how long each particular `git` invocation takes.
 
 [source,console]
 ----