Several small quotes fixes

Author: hedrok

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

@@ -302,8 +302,8 @@ Each developer has committed a few times and merged each other's work successful
 image::images/small-team-7.png[Jessica's history after pushing all changes back to the server.]
 
 That is one of the simplest workflows.
-You work for a while, generally in a topic branch, and merge into your master branch when it's ready to be integrated.
-When you want to share that work, you fetch and merge your master from `origin/master` if it has changed, and finally push to the `master` branch on the server.
+You work for a while, generally in a topic branch, and merge into your `master` branch when it's ready to be integrated.
+When you want to share that work, you fetch and merge your `master` from `origin/master` if it has changed, and finally push to the `master` branch on the server.
 The general sequence is something like this:
 
 .General sequence of events for a simple multiple-developer Git workflow.

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

@@ -91,7 +91,7 @@ $ rm -Rf .git/refs/remotes/origin
 ----
 
 It may happen that you'll see some extra branches which are suffixed by `@xxx` (where xxx is a number), while in Subversion you only see one branch.
-This is actually a Subversion feature called "peg-revisions", which is something that Git simply has no syntactical counterpart for.
+This is actually a Subversion feature called ``peg-revisions'', which is something that Git simply has no syntactical counterpart for.
 Hence, `git svn` simply adds the svn version number to the branch name just in the same way as you would have written it in svn to address the peg-revision of that branch.
 If you do not care anymore about the peg-revisions, simply remove them using `git branch -d`.