* subversion/libsvn_wc/README : Fix typo.

* subversion/libsvn_client/client.h : Fix typo in the comment dealing with   svn_client__checkout_internal.

* notes/wc-ng-design : Fix typo.

Patch by: Kannan R <kannanr@collab.net>



Index: subversion/libsvn_wc/README
===================================================================
--- subversion/libsvn_wc/README	(revision 38950)
+++ subversion/libsvn_wc/README	(working copy)
@@ -223,7 +223,7 @@
        <mv name="tmp/prop-base/name"
            dest="prop-base/name">
 
-   The problem with the second way is that is violates the
+   The problem with the second way is that it violates the
    separability of .svn subdirectories -- a subdir should be operable
    independent of its location in the local filesystem.  
 
Index: subversion/libsvn_client/client.h
===================================================================
--- subversion/libsvn_client/client.h	(revision 38950)
+++ subversion/libsvn_client/client.h	(working copy)
@@ -587,7 +587,7 @@
    DEPTH must be a definite depth, not (e.g.) svn_depth_unknown.
 
    RA_CACHE is a pointer to a cache of information for the URL at
-   REVISION based of the PEG_REVISION.  Any information not in
+   REVISION based on the PEG_REVISION.  Any information not in
    *RA_CACHE is retrieved by a round-trip to the repository.  RA_CACHE
    may be NULL which indicates that no cache information is available.
 
Index: notes/wc-ng-design
===================================================================
--- notes/wc-ng-design	(revision 38950)
+++ notes/wc-ng-design	(working copy)
@@ -275,7 +275,7 @@
  * No strict separation between public and internal APIs: many public
    APIs also used internally, growing arguments which *should* only
    matter for internal use
- * The lock strategy requires writing a file in every directory of a working,
+ * The lock strategy requires writing a file in every directory of a working copy,
    which severely reduces our performance in several environments. (Windows, 
    NFS). Testing showed that in some cases we used more than 50 seconds on
    writing 8000 lockfiles before we even started looking what to update. A new
entered main.cprocessing arguments