improved a few sentences

Changed a sentence that didn't seem well. Also changed the output
messages of git to be consistent with that shown by git in real time

Author: Kaartic Sivaraam

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

@@ -87,7 +87,7 @@ Further paragraphs come after blank lines.
 If all your commit messages look like this, things will be a lot easier for you and the developers you work with.
 The Git project has well-formatted commit messages – try running `git log --no-merges` there to see what a nicely formatted project-commit history looks like.
 
-In the following examples, and throughout most of this book, for the sake of brevity this book doesn't have nicely-formatted messages like this; instead, we use the `-m` option to `git commit`.
+For the sake of brevity, the following examples, and most examples in other parts of this book,  don't have nicely-formatted messages like this; instead, we use the `-m` option to `git commit`.
 Do as we say, not as we do.
 
 [[_private_team]]
@@ -177,7 +177,7 @@ John has a reference to the changes Jessica pushed up, but he has to merge them
 [source,console]
 ----
 $ git merge origin/master
-Merge made by recursive.
+Merge made by the 'recursive' strategy.
  TODO |    1 +
  1 files changed, 1 insertions(+), 0 deletions(-)
 ----
@@ -276,7 +276,7 @@ Now Jessica merges in John's work (`origin/master`):
 ----
 $ git merge origin/master
 Auto-merging lib/simplegit.rb
-Merge made by recursive.
+Merge made by the 'recursive' strategy.
  lib/simplegit.rb |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)
 ----
@@ -394,7 +394,7 @@ Jessica can now merge this into the work she did with `git merge`:
 ----
 $ git merge origin/featureBee
 Auto-merging lib/simplegit.rb
-Merge made by recursive.
+Merge made by the 'recursive' strategy.
  lib/simplegit.rb |    4 ++++
  1 files changed, 4 insertions(+), 0 deletions(-)
 ----