Merge pull request #961 from td2014/master

Minor typo corrections.

Author: ben

book/04-git-server/sections/generating-ssh-key.asc

@@ -2,7 +2,7 @@
 === Generating Your SSH Public Key
 
 (((SSH keys)))
-That being said, many Git servers authenticate using SSH public keys.
+Many Git servers authenticate using SSH public keys.
 In order to provide a public key, each user in your system must generate one if they don't already have one.
 This process is similar across all operating systems.
 First, you should check to make sure you don't already have a key.

book/09-git-and-other-scms/sections/client-bzr.asc

@@ -62,7 +62,7 @@ The second command clones all the branches contained in the emacs repository; ne
 $ git config remote-bzr.branches 'trunk, xwindow'
 ----
 
-Some remote repositories don't allow to list their branches, in which case you have to manually specify them, and even though you could specify the configuration in the cloning command, you may find this easier:
+Some remote repositories don't allow you to list their branches, in which case you have to manually specify them, and even though you could specify the configuration in the cloning command, you may find this easier:
 
 [source,console]
 ----

book/09-git-and-other-scms/sections/client-p4.asc

@@ -481,7 +481,7 @@ Files:
 
 This is mostly the same content you'd see by running `p4 submit`, except the stuff at the end which git-p4 has helpfully included.
 Git-p4 tries to honor your Git and Perforce settings individually when it has to provide a name for a commit or changeset, but in some cases you want to override it.
-For example, if the Git commit you're importing was written by a contributor who doesn't have a Perforce user account, you may still want the resulting changeset to look like they write it (and not you).
+For example, if the Git commit you're importing was written by a contributor who doesn't have a Perforce user account, you may still want the resulting changeset to look like they wrote it (and not you).
 
 Git-p4 has helpfully imported the message from the Git commit as the content for this Perforce changeset, so all we have to do is save and quit, twice (once for each commit).
 The resulting shell output will look something like this: