[svnbook] r4101 committed - * book/ch02-basic-usage.xml: Fix three typos....

[svnbook at googlecode.com]

Revision: 4101
Author:   stsp at elego.de
Date:     Mon Oct  3 02:24:31 2011
Log:      * book/ch02-basic-usage.xml: Fix three typos.
Patch by: Richard Cavell

http://code.google.com/p/svnbook/source/detail?r=4101

Modified:
  /trunk/en/book/ch02-basic-usage.xml

=======================================
--- /trunk/en/book/ch02-basic-usage.xml	Fri Sep 30 05:59:01 2011
+++ /trunk/en/book/ch02-basic-usage.xml	Mon Oct  3 02:24:31 2011
@@ -1524,7 +1524,7 @@
            />).  After you've edited the file, if you're satisfied with
            the changes you've made, you can tell Subversion that the
            edited file is no longer in conflict by using
-          the <quote>resolve</quote> command
+          the <quote>resolved</quote> command
            (<literal>r</literal>).</para>

          <para>Regardless of what your local Unix snob will likely tell
@@ -2594,7 +2594,7 @@
          can use <command>svn export</command> to create a local copy
          of all or part of your repository
          sans <filename>.svn</filename> directories.  The basic syntax
-        of this subcommand is identical to that of the <command>svn
+        of this subcommand is identical to that of <command>svn
          checkout</command>:</para>

        <informalexample>
@@ -2664,7 +2664,7 @@
          so as safely as possible.  Before changing the working copy,
          Subversion logs its intentions in a private <quote>to-do
          list</quote>, of sorts.  Next, it performs those actions to
-        affect the desired change, holding a lock on the relevant part
+        effect the desired change, holding a lock on the relevant part
          of the working copy while it works.  This prevents other
          Subversion clients from accessing the working copy mid-change.
          Finally, Subversion releases its lock and cleans up its