1.1 --- a/en/intro.tex	Tue Aug 26 14:14:24 2008 -0700
     1.2 +++ b/en/intro.tex	Sat Feb 14 13:27:23 2009 +0100
     1.3 @@ -359,7 +359,7 @@
     1.4  
     1.5  Before you read on, please understand that this section necessarily
     1.6  reflects my own experiences, interests, and (dare I say it) biases.  I
     1.7 -have used every one of the revision control tools listed below, in
     1.8 +I have used every one of the revision control tools listed below, in
     1.9  most cases for several years at a time.
    1.10  
    1.11  
    1.12 @@ -406,7 +406,7 @@
    1.13  Because Subversion doesn't store revision history on the client, it is
    1.14  well suited to managing projects that deal with lots of large, opaque
    1.15  binary files.  If you check in fifty revisions to an incompressible
    1.16 -10MB file, Subversion's client-side space usage stays constant The
    1.17 +10MB file, Subversion's client-side space usage stays constant. The
    1.18  space used by any distributed SCM will grow rapidly in proportion to
    1.19  the number of revisions, because the differences between each revision
    1.20  are large.