Fix typos.

Author: siraben

en/branch.txt

@@ -16,7 +16,7 @@ With this magic word, the files in your directory suddenly shapeshift from one v
 
 === The Boss Key ===
 
-Ever played one of those games where at the push of a button (``the boss key''), the screen would instantly display a spreadsheet or something? So if the boss walked in the office while you were playing the game you could quickly hide it away?
+Ever played one of those games where at the push of a button (``the boss key''), the screen would instantly display a spreadsheet or something? So if the boss walked into the office while you were playing the game you could quickly hide it away?
 
 In some directory:
 

en/clone.txt

@@ -38,7 +38,7 @@ Start the Git daemon if necessary:
 
  $ git daemon --detach  # it may already be running
 
-For Git hosting services, follow the instructions to setup the initially
+For Git hosting services, follow the instructions to set up the initially
 empty Git repository. Typically one fills in a form on a webpage.
 
 'Push' your project to the central server with:

en/drawbacks.txt

@@ -80,7 +80,7 @@ The current implementation of Git, rather than its design, is to blame for this
 
 === Initial Commit ===
 
-A stereotypical computer scientist counts from 0, rather than 1. Unfortunately, with respect to commits, git does not adhere to this convention. Many commands are unfriendly before the initial commit. Additionally, some corner cases must be handled specially, such as rebasing a branch with a different initial commit.
+A stereotypical computer scientist counts from 0, rather than 1. Unfortunately, with respect to commits, Git does not adhere to this convention. Many commands are unfriendly before the initial commit. Additionally, some corner cases must be handled specially, such as rebasing a branch with a different initial commit.
 
 Git would benefit from defining the zero commit: as soon as a repository is constructed, HEAD would be set to the string consisting of 20 zero bytes. This special commit represents an empty tree, with no parent, at some time predating all Git repositories.
 

en/multiplayer.txt

@@ -41,7 +41,7 @@ Now you can publish your latest edits via SSH from any clone:
 
  $ git push web.server:/path/to/proj.git master
 
-and anybody can get your project with:
+and anyone can get your project with:
 
  $ git clone http://web.server/proj.git
 

en/translate.txt

@@ -8,7 +8,7 @@ Clone the source, then create a directory corresponding to the target
 language's IETF tag: see
 http://www.w3.org/International/articles/language-tags/Overview.en.php[the W3C
 article on internationalization]. For example, English is "en" and Japanese is
-"ja". In the new directory, and translate the +txt+ files from the "en"
+"ja". In the new directory, translate the +txt+ files from the "en"
 subdirectory.
 
 For instance, to translate the guide into http://en.wikipedia.org/wiki/Klingon_language[Klingon], you might type: