Merge pull request #1847 from petk/patch-capitalization

Use lowercase

Author: ben

book/01-introduction/sections/history.asc

@@ -17,4 +17,4 @@ Some of the goals of the new system were as follows:
 *  Able to handle large projects like the Linux kernel efficiently (speed and data size)
 
 Since its birth in 2005, Git has evolved and matured to be easy to use and yet retain these initial qualities.
-It's amazingly fast, it's very efficient with large projects, and it has an incredible branching system for non-linear development (See <<ch03-git-branching#ch03-git-branching>>).
+It's amazingly fast, it's very efficient with large projects, and it has an incredible branching system for non-linear development (see <<ch03-git-branching#ch03-git-branching>>).

book/04-git-server/sections/protocols.asc

@@ -90,7 +90,7 @@ In fact, for services like GitHub, the URL you use to view the repository online
 If the server does not respond with a Git HTTP smart service, the Git client will try to fall back to the simpler _Dumb_ HTTP protocol.
 The Dumb protocol expects the bare Git repository to be served like normal files from the web server.
 The beauty of Dumb HTTP is the simplicity of setting it up.
-Basically, all you have to do is put a bare Git repository under your HTTP document root and set up a specific `post-update` hook, and you're done (See <<ch08-customizing-git#_git_hooks>>).
+Basically, all you have to do is put a bare Git repository under your HTTP document root and set up a specific `post-update` hook, and you're done (see <<ch08-customizing-git#_git_hooks>>).
 At that point, anyone who can access the web server under which you put the repository can also clone your repository.
 To allow read access to your repository over HTTP, do something like this: