Leetle punctuations

Author: ben

book/03-git-branching/1-git-branching.asc

@@ -18,7 +18,7 @@ To really understand the way Git does branching, we need to take a step back and
 As you may remember from <<_getting_started>>, Git doesn't store data as a series of changesets or differences, but instead as a series of snapshots.
 
 When you make a commit, Git stores a commit object that contains a pointer to the snapshot of the content you staged.
-This object also contains the authors name and email, the message that you typed, and pointers to the commit or commits that directly came bfore this commit (it's parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches.
+This object also contains the author's name and email, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches.
 
 To visualize this, let's assume that you have a directory containing three files, and you stage them all and commit.
 Staging the files checksums each one (the SHA-1 hash we mentioned in <<_getting_started>>), stores that version of the file in the Git repository (Git refers to them as blobs), and adds that checksum to the staging area:
@@ -749,7 +749,7 @@ Branch sf set up to track remote branch serverfix from origin.
 Switched to a new branch 'sf'
 ----
 
-Now, your local branch sf will automatically push to and pull from `origin/serverfix`.
+Now, your local branch `sf` will automatically push to and pull from `origin/serverfix`.
 
 If you already have a local branch and want to set it to a remote branch you just pulled down, or want to change the upstream branch you're tracking, you can use the `-u` or `--set-upstream-to` option to `git branch` to explicitly set it at any time.