--- README_maintainer	2010-11-16 10:22:56.000000000 +0100
+++ README_maintainer-new.org	2010-11-16 11:17:40.677233600 +0100
@@ -62,5 +62,5 @@
 : pw update -s "Changed Requested" -m "What to change" NNN
 
-This will sand an email to the contributor and the mailing list with a
+This will send an email to the contributor and the mailing list with a
 request for changes.  The =-m= message should not be more than one
 sentence and describe the requested changes.  If you need to explain
@@ -83,5 +83,5 @@
 : pw merge -m "maintainer comment" NNN
 
-This will merge than patch into master, switch back to master and send
+This will merge the patch into master, switch back to master and send
 an email to both contributor and mailing list stating that this change
 has been accepted, along with the comment given in the =-m= message.
@@ -122,5 +122,5 @@
 bugs discovered in a main release.  Only the fix to the bug is
 bundled into a release, without the main development work going on in
-the master branch.  Since the big fix will also be needed in the
+the master branch.  Since the bug fix will also be needed in the
 master branch, usually the fix is made in master and then
 cherry-picked into maint.  When this is done, a release is made from
@@ -146,5 +146,5 @@
 This is still a significant headache.  Some hand work is needed here.
 
-Emacs uses bzr, and while I see all the advantages thiswould have, I
+Emacs uses bzr, and while I see all the advantages this would have, I
 cannot bring myself to switch away from git for my day-to-day work.
 So the way I have been doing things with Emacs is this: