# HG changeset patch
# User Romain PELISSE <romain.pelisse@atosorigin.com>
# Date 1234103898 -3600
# Node ID d2e041bef460797f71c39510c2a0290848608f73
# Parent  730d912ef843a1911b62505734c0f92965c77e16
Correcting a few typos, spotted while translating the hgboox in french, in the english version

diff -r 730d912ef843 -r d2e041bef460 en/intro.tex
--- a/en/intro.tex	Sun Feb 08 14:17:16 2009 +0100
+++ b/en/intro.tex	Sun Feb 08 15:38:18 2009 +0100
@@ -359,7 +359,7 @@
 
 Before you read on, please understand that this section necessarily
 reflects my own experiences, interests, and (dare I say it) biases.  I
-have used every one of the revision control tools listed below, in
+I have used every one of the revision control tools listed below, in
 most cases for several years at a time.
 
 
@@ -406,7 +406,7 @@
 Because Subversion doesn't store revision history on the client, it is
 well suited to managing projects that deal with lots of large, opaque
 binary files.  If you check in fifty revisions to an incompressible
-10MB file, Subversion's client-side space usage stays constant The
+10MB file, Subversion's client-side space usage stays constant. The
 space used by any distributed SCM will grow rapidly in proportion to
 the number of revisions, because the differences between each revision
 are large.