Merge pull request #908 from rpjday/debugging

Minor cleanup of "Debugging with Git".

Author: ben

book/07-git-tools/sections/debugging.asc

@@ -1,7 +1,7 @@
 === Debugging with Git
 
-Git also provides a couple of tools to help you debug issues in your projects.
-Because Git is designed to work with nearly any type of project, these tools are pretty generic, but they can often help you hunt for a bug or culprit when things go wrong.
+In addition to being primarily for version control, Git also provides a couple commands to help you debug your source code projects.
+Because Git is designed to handle nearly any type of content, these tools are pretty generic, but they can often help you hunt for a bug or culprit when things go wrong.
 
 [[_file_annotation]]
 ==== File Annotation
@@ -32,7 +32,7 @@ b8b0618cf6fab (Cheng Renquan  2009-05-26 16:03:07 +0800 70)   KBUILD_VERBOSE = $
 ----
 
 Notice that the first field is the partial SHA-1 of the commit that last modified that line.
-The next two fields are values extracted from that commit – the author name and the authored date of that commit – so you can easily see who modified that line and when.
+The next two fields are values extracted from that commit -- the author name and the authored date of that commit -- so you can easily see who modified that line and when.
 After that come the line number and the content of the file.
 Also note the `^1da177e4c3f4` commit lines, where the `^` prefix designates lines that were introduced in the repository's initial commit and have remained unchanged ever since.
 This is a tad confusing, because now you’ve seen at least three different ways that Git uses the `^` to modify a commit SHA-1, but that is what it means here.