[PATCH] Typo fixes for locking docs

Just a patch to fix a few typos, missing words, etc. in the locking
docs. I'm not sure it even needs a log message besides "Fix typos."
(but if it does, I can write one :)

-- 
Michael W Thelen
It is a mistake to think you can solve any major problems just with
potatoes.       -- Douglas Adams

Index: notes/locking/locking-ui.txt
===================================================================
--- notes/locking/locking-ui.txt (revision 11343)
+++ notes/locking/locking-ui.txt (working copy)
@@ -96,8 +96,8 @@
       This section describes a user interface to accomplish "locking",
       as described in the functional spec. A new property is used to
       enforce locking and prevent people from wasting time; lock
- tokens are objects stored in the working that represent a lock;
- and two new subcommands (lock/unlock) are described.
+ tokens are objects stored in the working copy that represent a
+ lock; and two new subcommands (lock/unlock) are described.
 
    B. The "svn:lock" property
 
@@ -201,7 +201,7 @@
             The 'svn lock' command automatically implies running 'svn
             update' on a path. In other words, it's not possible to
             lock a non-HEAD version of a path. If a file has the
- 'svn:lock' property and has been hijacked, both 'svn lock'
+ 'svn:lock' property and has been hijacked, 'svn lock'
             will interactively ask the user whether to use the
             repository or local version of the file, just as 'svn
             update' does.
@@ -295,7 +295,7 @@
 
             1. seeing lock tokens in a working copy
 
- 'svn status' conisders a lock token "interesting", and
+ 'svn status' considers a lock token "interesting", and
                displays it using some new symbol, in a new column:
 
                    $ svn status
Index: notes/locking/locking-functional-spec.txt
===================================================================
--- notes/locking/locking-functional-spec.txt (revision 11343)
+++ notes/locking/locking-functional-spec.txt (working copy)
@@ -66,7 +66,7 @@
          There must be a system in place that tells users when locking
          is necessary; ideally, it would prevent a user from
          beginning work in the first place. If a lock already exists,
- a user should be able to who created it, when, and why.
+ a user should be able to see who created it, when, and why.
  
    C. Lock manipulation via client