Merge pull request #93 from schacon/cleanup

Cleanup

Author: schacon

book/01-introduction/sections/basics.asc

@@ -56,7 +56,10 @@ The mechanism that Git uses for this checksumming is called a SHA-1 hash.(((SHA-
 This is a 40-character string composed of hexadecimal characters (0–9 and a–f) and calculated based on the contents of a file or directory structure in Git.
 A SHA-1 hash looks something like this:
 
-  24b9da6552252987aa493b52f8696cd6d3b00373
+[source]
+----
+24b9da6552252987aa493b52f8696cd6d3b00373
+----
 
 You will see these hash values all over the place in Git because it uses them so much.
 In fact, Git stores everything in its database not by file name but by the hash value of its contents.

book/01-introduction/sections/first-time-setup.asc

@@ -24,8 +24,11 @@ It also still looks for `/etc/gitconfig`, although it's relative to the MSys roo
 The first thing you should do when you install Git is to set your user name and e-mail address.
 This is important because every Git commit uses this information, and it's immutably baked into the commits you start creating:
 
-  $ git config --global user.name "John Doe"
-  $ git config --global user.email [email protected]
+[source,console]
+----
+$ git config --global user.name "John Doe"
+$ git config --global user.email [email protected]
+----
 
 Again, you need to do this only once if you pass the `--global` option, because then Git will always use that information for anything you do on that system.
 If you want to override this with a different name or e-mail address for specific projects, you can run the command without the `--global` option when you're in that project.
@@ -38,7 +41,10 @@ Now that your identity is set up, you can configure the default text editor that
 If not configured, Git uses your system's default editor, which is generally Vim.
 If you want to use a different text editor, such as Emacs, you can do the following:
 
-  $ git config --global core.editor emacs
+[source,console]
+----
+$ git config --global core.editor emacs
+----
 
 [NOTE]
 ====
@@ -49,19 +55,25 @@ Vim and Emacs are popular text editors often used by developers on Unix based sy
 
 If you want to check your settings, you can use the `git config --list` command to list all the settings Git can find at that point:
 
-  $ git config --list
-  user.name=John Doe
-  [email protected]
-  color.status=auto
-  color.branch=auto
-  color.interactive=auto
-  color.diff=auto
-  ...
+[source,console]
+----
+$ git config --list
+user.name=John Doe
+[email protected]
+color.status=auto
+color.branch=auto
+color.interactive=auto
+color.diff=auto
+...
+----
 
 You may see keys more than once, because Git reads the same key from different files (`/etc/gitconfig` and `~/.gitconfig`, for example).
 In this case, Git uses the last value for each unique key it sees.
 
 You can also check what Git thinks a specific key's value is by typing `git config <key>`:(((git commands, config)))
 
-  $ git config user.name
-  John Doe
+[source,console]
+----
+$ git config user.name
+John Doe
+----

book/01-introduction/sections/help.asc

@@ -3,13 +3,19 @@
 
 If you ever need help while using Git, there are three ways to get the manual page (manpage) help for any of the Git commands:
 
-  $ git help <verb>
-  $ git <verb> --help
-  $ man git-<verb>
+[source,console]
+----
+$ git help <verb>
+$ git <verb> --help
+$ man git-<verb>
+----
 
 For example, you can get the manpage help for the config command by running(((git commands, help)))
 
-  $ git help config
+[source,console]
+----
+$ git help config
+----
 
 These commands are nice because you can access them anywhere, even offline.
 If the manpages and this book aren't enough and you need in-person help, you can try the `#git` or `#github` channel on the Freenode IRC server (irc.freenode.net).

book/cover.html

@@ -1 +1 @@
-<figure data-type="cover"><img alt="cover" src="../images/cover.png" /></figure>
+<figure data-type="cover"><img alt="cover" src="cover.png" /></figure>

cover.png book/cover.pngcover.png renamed to book/cover.png

@@ -4,7 +4,7 @@ Pro Git
 :docinfo:
 :toc:
 :toclevels: 2
-:front-cover-image: image:cover.png[width=1050,height=1600]
+:front-cover-image: image:book/cover.png[width=1050,height=1600]
 
 include::book/01-introduction/1-introduction.asc[]