fixed perrys typos

svn path=/trunk/matplotlib/; revision=4813

Author: jdh2358

INSTALL

@@ -30,9 +30,9 @@ COMPILING
   you can set.
 
   If you want to use a GUI backend, you will need either Tkinter,
-  pygtk or wxpython installed on your system, from src or from a
+  pygtk , wxPython or Qt installed on your system, from src or from a
   package manager including the devel packages.  You can choose which
-  backends to enable by setting the flags in setup.py, but the default
+  backends to enable by setting the flags in setup.cfg, but the default
   is to automatically detect your installed GUIs and build support for
   them.  If you later find that you did not have a GUI toolkit like
   pygtk installed when you built matplotlib, but now want it, you will

MIGRATION.txt

@@ -1,9 +1,9 @@
 Migrating to the new matplotlib codebase
 ========================================
 
-Michael Droettboom has spent the last several month working on the
+Michael Droettboom has spent the last several months working on the
 "transforms branch" of matplotlib, in which he rewrote from the ground
-up the transformation infrastructure in matplotlib, whih many found
+up the transformation infrastructure in matplotlib, which many found
 unintuitive and hard to extend.  In addition to a cleaner code base,
 the refactoring allows you to define your own trasformations and
 projections (eg map projections) within matplotlib.  He has merged his
@@ -13,10 +13,10 @@ future matplotlib releases.
 If you are a svn user, we encourage you to continue using the trunk as
 before, but with the understanding that you are now truly on the
 bleeding edge.  Michael has made sure all the examples still pass with
-the new code base, so for the vast majority of you, I except to see
+the new code base, so for the vast majority of you, I expect to see
 few problems.  But we need to get as many people as possible using the
 new code base so we can find and fix the remaining problems.  We have
-take the svn cde used in the last stable release in the 0.91 series,
+take the svn code used in the last stable release in the 0.91 series,
 and made it a maintenance branch so we can still fix bugs and support
 people who are not ready to migrate to the new transformation
 infrastructure but nonetheless need acccess to svn bug fixes.