Minor fixes

Author: ben

en/book/01-introduction/chapter1.asc

@@ -92,7 +92,7 @@ The mechanism that Git uses for this checksumming is called a SHA-1 hash. This i
 
   24b9da6552252987aa493b52f8696cd6d3b00373
 
-You will see these hash values all over the place in Git because it uses them so much. In fact, Git stores everything in it's database not by file name but by the hash value of its contents.
+You will see these hash values all over the place in Git because it uses them so much. In fact, Git stores everything in its database not by file name but by the hash value of its contents.
 
 ==== Git Generally Only Adds Data
 
@@ -125,7 +125,7 @@ If a particular version of a file is in the Git directory, it’s considered com
 
 === The Command Line
 
-There are a lot of different ways to use Git these days.  There are the original command line tools and there are many graphical user interfaces as well of varying capabilities.  For this book, we will be using Git on the command line. For one, the command line is the only place you can run *all* Git commands - most of the GUIs only implement some subset of Git functionality for simplicity.  If you know how to run the command line version, you can probably also figure out how to run the GUI version, while the opposite is not neccesarily true.  Finally, everyone should have the command line tooling, where everyone may choose different GUIs.
+There are a lot of different ways to use Git these days.  There are the original command line tools and there are many graphical user interfaces as well of varying capabilities.  For this book, we will be using Git on the command line. For one, the command line is the only place you can run *all* Git commands - most of the GUIs only implement some subset of Git functionality for simplicity.  If you know how to run the command line version, you can probably also figure out how to run the GUI version, while the opposite is not neccesarily true.  Finally, while your choice of graphical client is a matter of personal taste, _all_ users will have the command-line tools installed and available.
 
 So, we will expect you to know how to open Terminal in Mac or Command Prompt or Powershell in Windows.  If you don't know what we're talking about here, you may need to stop and research that quickly so that you can follow the rest of the examples and descriptions in this book.
 
@@ -185,7 +185,7 @@ Git comes with a tool called `git config` that lets you get and set configuratio
 *  `~/.gitconfig` file: Specific to your user. You can make Git read and write to this file specifically by passing the `--global` option.
 *  `config` file in the Git directory (that is, `.git/config`) of whatever repository you’re currently using: Specific to that single repository. Each level overrides values in the previous level, so values in `.git/config` trump those in `/etc/gitconfig`.
 
-On Windows systems, Git looks for the `.gitconfig` file in the `$HOME` directory (`C:\Documents and Settings\$USER` for most people). It also still looks for `/etc/gitconfig`, although it’s relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
+On Windows systems, Git looks for the `.gitconfig` file in the `$HOME` directory (`C:\Users\$USER` for most people). It also still looks for `/etc/gitconfig`, although it’s relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
 
 ==== Installing from Source