Fix commit message examples to use imperative mood

Author: HonkingGoose

book/02-git-basics/sections/aliases.asc

@@ -53,7 +53,7 @@ commit 66938dae3329c7aebe598c2246a8e6af90d04646
 Author: Josh Goebel <[email protected]>
 Date:   Tue Aug 26 19:48:51 2008 +0800
 
-    test for current head
+    Test for current head
 
     Signed-off-by: Scott Chacon <[email protected]>
 ----

book/02-git-basics/sections/getting-a-repository.asc

@@ -47,7 +47,7 @@ You can accomplish that with a few `git add` commands that specify the files you
 ----
 $ git add *.c
 $ git add LICENSE
-$ git commit -m 'initial project version'
+$ git commit -m 'Initial project version'
 ----
 
 We'll go over what these commands do in just a minute.

book/02-git-basics/sections/recording-changes.asc

@@ -461,8 +461,8 @@ Alternatively, you can type your commit message inline with the `commit` command
 
 [source,console]
 ----
-$ git commit -m "Story 182: Fix benchmarks for speed"
-[master 463dc4f] Story 182: Fix benchmarks for speed
+$ git commit -m "Story 182: fix benchmarks for speed"
+[master 463dc4f] Story 182: fix benchmarks for speed
  2 files changed, 2 insertions(+)
  create mode 100644 README
 ----
@@ -493,8 +493,8 @@ Changes not staged for commit:
     modified:   CONTRIBUTING.md
 
 no changes added to commit (use "git add" and/or "git commit -a")
-$ git commit -a -m 'added new benchmarks'
-[master 83e38c7] added new benchmarks
+$ git commit -a -m 'Add new benchmarks'
+[master 83e38c7] Add new benchmarks
  1 file changed, 5 insertions(+), 0 deletions(-)
 ----
 

book/02-git-basics/sections/tagging.asc

@@ -91,7 +91,7 @@ commit ca82a6dff817ec66f44342007202690a93763949
 Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
-    changed the version number
+    Change version number
 ----
 
 That shows the tagger information, the date the commit was tagged, and the annotation message before showing the commit information.
@@ -124,7 +124,7 @@ commit ca82a6dff817ec66f44342007202690a93763949
 Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
-    changed the version number
+    Change version number
 ----
 
 ==== Tagging Later
@@ -136,18 +136,18 @@ Suppose your commit history looks like this:
 ----
 $ git log --pretty=oneline
 15027957951b64cf874c3557a0f3547bd83b3ff6 Merge branch 'experiment'
-a6b4c97498bd301d84096da251c98a07c7723e65 beginning write support
-0d52aaab4479697da7686c15f77a3d64d9165190 one more thing
+a6b4c97498bd301d84096da251c98a07c7723e65 Create write support
+0d52aaab4479697da7686c15f77a3d64d9165190 One more thing
 6d52a271eda8725415634dd79daabbc4d9b6008e Merge branch 'experiment'
-0b7434d86859cc7b8c3d5e1dddfed66ff742fcbc added a commit function
-4682c3261057305bdd616e23b64b0857d832627b added a todo file
-166ae0c4d3f420721acbb115cc33848dfcc2121a started write support
-9fceb02d0ae598e95dc970b74767f19372d61af8 updated rakefile
-964f16d36dfccde844893cac5b347e7b3d44abbc commit the todo
-8a5cbc430f1a9c3d00faaeffd07798508422908a updated readme
+0b7434d86859cc7b8c3d5e1dddfed66ff742fcbc Add commit function
+4682c3261057305bdd616e23b64b0857d832627b Add todo file
+166ae0c4d3f420721acbb115cc33848dfcc2121a Create write support
+9fceb02d0ae598e95dc970b74767f19372d61af8 Update rakefile
+964f16d36dfccde844893cac5b347e7b3d44abbc Commit the todo
+8a5cbc430f1a9c3d00faaeffd07798508422908a Update readme
 ----
 
-Now, suppose you forgot to tag the project at v1.2, which was at the ``updated rakefile'' commit.
+Now, suppose you forgot to tag the project at v1.2, which was at the ``Update rakefile'' commit.
 You can add it after the fact.
 To tag that commit, you specify the commit checksum (or part of it) at the end of the command:
 
@@ -178,7 +178,7 @@ commit 9fceb02d0ae598e95dc970b74767f19372d61af8
 Author: Magnus Chacon <[email protected]>
 Date:   Sun Apr 27 20:43:35 2008 -0700
 
-    updated rakefile
+    Update rakefile
 ...
 ----
 
@@ -277,7 +277,7 @@ HEAD is now at 99ada87... Merge pull request #89 from schacon/appendix-final
 
 $ git checkout 2.0-beta-0.1
 Previous HEAD position was 99ada87... Merge pull request #89 from schacon/appendix-final
-HEAD is now at df3f601... add atlas.json and cover image
+HEAD is now at df3f601... Add atlas.json and cover image
 ----
 
 In ``detached HEAD'' state, if you make changes and then create a commit, the tag will stay the same, but your new commit won't belong to any branch and will be unreachable, except by the exact commit hash.

book/02-git-basics/sections/undoing.asc

@@ -24,7 +24,7 @@ As an example, if you commit and then realize you forgot to stage the changes in
 
 [source,console]
 ----
-$ git commit -m 'initial commit'
+$ git commit -m 'Initial commit'
 $ git add forgotten_file
 $ git commit --amend
 ----

book/02-git-basics/sections/viewing-history.asc

@@ -21,19 +21,19 @@ commit ca82a6dff817ec66f44342007202690a93763949
 Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
-    changed the version number
+    Change version number
 
 commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
 Author: Scott Chacon <[email protected]>
 Date:   Sat Mar 15 16:40:33 2008 -0700
 
-    removed unnecessary test
+    Remove unnecessary test
 
 commit a11bef06a3f659402fe7563abf99ad00de2209e6
 Author: Scott Chacon <[email protected]>
 Date:   Sat Mar 15 10:31:28 2008 -0700
 
-    first commit
+    Initial commit
 ----
 
 By default, with no arguments, `git log` lists the commits made in that repository in reverse chronological order; that is, the most recent commits show up first.
@@ -52,7 +52,7 @@ commit ca82a6dff817ec66f44342007202690a93763949
 Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
-    changed the version number
+    Change version number
 
 diff --git a/Rakefile b/Rakefile
 index a874b73..8f94139 100644
@@ -72,7 +72,7 @@ commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
 Author: Scott Chacon <[email protected]>
 Date:   Sat Mar 15 16:40:33 2008 -0700
 
-    removed unnecessary test
+    Remove unnecessary test
 
 diff --git a/lib/simplegit.rb b/lib/simplegit.rb
 index a0a60ae..47c6340 100644
@@ -101,7 +101,7 @@ commit ca82a6dff817ec66f44342007202690a93763949
 Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
-    changed the version number
+    Change version number
 
  Rakefile | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
@@ -110,7 +110,7 @@ commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7
 Author: Scott Chacon <[email protected]>
 Date:   Sat Mar 15 16:40:33 2008 -0700
 
-    removed unnecessary test
+    Remove unnecessary test
 
  lib/simplegit.rb | 5 -----
  1 file changed, 5 deletions(-)
@@ -119,7 +119,7 @@ commit a11bef06a3f659402fe7563abf99ad00de2209e6
 Author: Scott Chacon <[email protected]>
 Date:   Sat Mar 15 10:31:28 2008 -0700
 
-    first commit
+    Initial commit
 
  README           |  6 ++++++
  Rakefile         | 23 +++++++++++++++++++++++
@@ -139,9 +139,9 @@ In addition, the `short`, `full`, and `fuller` options show the output in roughl
 [source,console]
 ----
 $ git log --pretty=oneline
-ca82a6dff817ec66f44342007202690a93763949 changed the version number
-085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 removed unnecessary test
-a11bef06a3f659402fe7563abf99ad00de2209e6 first commit
+ca82a6dff817ec66f44342007202690a93763949 Change version number
+085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Remove unnecessary test
+a11bef06a3f659402fe7563abf99ad00de2209e6 Initial commit
 ----
 
 The most interesting option is `format`, which allows you to specify your own log output format.
@@ -150,9 +150,9 @@ This is especially useful when you're generating output for machine parsing -- b
 [source,console]
 ----
 $ git log --pretty=format:"%h - %an, %ar : %s"
-ca82a6d - Scott Chacon, 6 years ago : changed the version number
-085bb3b - Scott Chacon, 6 years ago : removed unnecessary test
-a11bef0 - Scott Chacon, 6 years ago : first commit
+ca82a6d - Scott Chacon, 6 years ago : Change version number
+085bb3b - Scott Chacon, 6 years ago : Remove unnecessary test
+a11bef0 - Scott Chacon, 6 years ago : Initial commit
 ----
 
 <<pretty_format>> lists some of the more useful options that `format` takes.
@@ -190,15 +190,15 @@ This option adds a nice little ASCII graph showing your branch and merge history
 [source,console]
 ----
 $ git log --pretty=format:"%h %s" --graph
-* 2d3acf9 ignore errors from SIGCHLD on trap
+* 2d3acf9 Ignore errors from SIGCHLD on trap
 *  5e3ee11 Merge branch 'master' of git://github.com/dustin/grit
 |\
-| * 420eac9 Added a method for getting the current branch.
-* | 30e367c timeout code and tests
-* | 5a09431 add timeout protection to grit
-* | e1193f8 support for heads with slashes in them
+| * 420eac9 Add method for getting the current branch
+* | 30e367c Timeout code and tests
+* | 5a09431 Add timeout protection to grit
+* | e1193f8 Support for heads with slashes in them
 |/
-* d6016bc require time for xmlschema
+* d6016bc Require time for xmlschema
 *  11d191e Merge branch 'defunkt' into local
 ----
 

book/03-git-branching/sections/basic-branching-and-merging.asc

@@ -50,7 +50,7 @@ Doing so moves the `iss53` branch forward, because you have it checked out (that
 [source,console]
 ----
 $ vim index.html
-$ git commit -a -m 'added a new footer [issue 53]'
+$ git commit -a -m 'Create new footer [issue 53]'
 ----
 
 .The `iss53` branch has moved forward with your work
@@ -83,8 +83,8 @@ Let's create a `hotfix` branch on which to work until it's completed:
 $ git checkout -b hotfix
 Switched to a new branch 'hotfix'
 $ vim index.html
-$ git commit -a -m 'fixed the broken email address'
-[hotfix 1fb7853] fixed the broken email address
+$ git commit -a -m 'Fix broken email address'
+[hotfix 1fb7853] Fix broken email address
  1 file changed, 2 insertions(+)
 ----
 
@@ -130,8 +130,8 @@ Now you can switch back to your work-in-progress branch on issue #53 and continu
 $ git checkout iss53
 Switched to branch "iss53"
 $ vim index.html
-$ git commit -a -m 'finished the new footer [issue 53]'
-[iss53 ad82d7a] finished the new footer [issue 53]
+$ git commit -a -m 'Finish the new footer [issue 53]'
+[iss53 ad82d7a] Finish the new footer [issue 53]
 1 file changed, 1 insertion(+)
 ----
 

book/03-git-branching/sections/branch-management.asc

@@ -22,9 +22,9 @@ To see the last commit on each branch, you can run `git branch -v`:
 [source,console]
 ----
 $ git branch -v
-  iss53   93b412c fix javascript issue
+  iss53   93b412c Fix javascript issue
 * master  7a98805 Merge branch 'iss53'
-  testing 782fd34 add scott to the author list in the readmes
+  testing 782fd34 Add scott to the author list in the readme
 ----
 
 The useful `--merged` and `--no-merged` options can filter this list to branches that you have or have not yet merged into the branch you're currently on.

book/03-git-branching/sections/nutshell.asc

@@ -14,7 +14,7 @@ Staging the files computes a checksum for each one (the SHA-1 hash we mentioned
 [source,console]
 ----
 $ git add README test.rb LICENSE
-$ git commit -m 'The initial commit of my project'
+$ git commit -m 'Initial commit'
 ----
 
 When you create the commit by running `git commit`, Git checksums each subdirectory (in this case, just the root project directory) and stores them as a tree object in the Git repository.
@@ -80,9 +80,9 @@ This option is called `--decorate`.
 [source,console]
 ----
 $ git log --oneline --decorate
-f30ab (HEAD -> master, testing) add feature #32 - ability to add new formats to the central interface
-34ac2 Fixed bug #1328 - stack overflow under certain conditions
-98ca9 The initial commit of my project
+f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface
+34ac2 Fix bug #1328 - stack overflow under certain conditions
+98ca9 Initial commit
 ----
 
 You can see the `master` and `testing` branches that are right there next to the `f30ab` commit.
@@ -175,11 +175,11 @@ If you run `git log --oneline --decorate --graph --all` it will print out the hi
 [source,console]
 ----
 $ git log --oneline --decorate --graph --all
-* c2b9e (HEAD, master) made other changes
-| * 87ab2 (testing) made a change
+* c2b9e (HEAD, master) Made other changes
+| * 87ab2 (testing) Made a change
 |/
-* f30ab add feature #32 - ability to add new formats to the
-* 34ac2 fixed bug #1328 - stack overflow under certain conditions
+* f30ab Add feature #32 - ability to add new formats to the central interface
+* 34ac2 Fix bug #1328 - stack overflow under certain conditions
 * 98ca9 initial commit of my project
 ----
 

book/03-git-branching/sections/remote-branches.asc

@@ -188,10 +188,10 @@ This will list out your local branches with more information including what each
 [source,console]
 ----
 $ git branch -vv
-  iss53     7e424c3 [origin/iss53: ahead 2] forgot the brackets
-  master    1ae2a45 [origin/master] deploying index fix
-* serverfix f8674d9 [teamone/server-fix-good: ahead 3, behind 1] this should do it
-  testing   5ea463a trying something new
+  iss53     7e424c3 [origin/iss53: ahead 2] Add forgotten brackets
+  master    1ae2a45 [origin/master] Deploy index fix
+* serverfix f8674d9 [teamone/server-fix-good: ahead 3, behind 1] This should do it
+  testing   5ea463a Try something new
 ----
 
 So here we can see that our `iss53` branch is tracking `origin/iss53` and is ``ahead'' by two, meaning that we have two commits locally that are not pushed to the server.