Typos, spell check, untab

pep-0101.txt

@@ -49,7 +49,7 @@ How to Make A Release
       All Python development happens on the trunk.  A few days before
       the release, the RM will create a branch for this release.  Only
       the RM is authorized to make commits to this branch, but
-      checkins can proceed as normal on the trunk.  It is the
+      check ins can proceed as normal on the trunk.  It is the
       responsibility of the RM to decide on a case-by-case basis which
       trunk modifications should be merged into the branch.
 
@@ -71,7 +71,7 @@ How to Make A Release
       python-checkins mailing list), you need to decide whether the
       change should also be applied to the branch.
 
-      If so, it's fairly easy to apply the change by diffing the file
+      If so, it's fairly easy to apply the change by diff'ing the file
       and patching it manually.  You can also sometimes get away with
       just copying the file from the trunk directory to the branch
       directory, but be careful so you don't lose changes that only
@@ -89,7 +89,7 @@ How to Make A Release
       verify with Tim Peters about changes on Windows, and Jack Jansen
       about changes on the Mac.
 
-    - Also the night before the release, a freeze is put on checkins
+    - Also the night before the release, a freeze is put on check ins
       into the branch.  At this point, nobody except Fred Drake or Tim
       Peters should make any commits to the branch.  If the RM screwed
       up and some desperate last minute change to the branch is
@@ -179,10 +179,10 @@ How to Make A Release
 
     - Start your upload to SF.  You need to get Python-2.2a3.tgz into
       SourceForge.  This can take a while both because of the time it
-      takes to upload 650+KB of data, /and/ because SF has a 30 minute
-      delay built into the file release process.  The next few steps
-      can be taken in parallel, so it's best to start the upload now
-      and keep an eye on its progress.
+      takes to upload such a huge file, /and/ because SF has a 30
+      minute delay built into the file release process.  The next few
+      steps can be taken in parallel, so it's best to start the upload
+      now and keep an eye on its progress.
 
       I've found that the `ncftpput' program is a great tool to use if
       you have it available.  You can execute the following command to
@@ -414,7 +414,7 @@ How to Make A Release
         indicating that the trunk is going to be moving forward with
         development.  E.g. the line should look like:
 
-        #define PY_VERSION		"2.2a2+"
+        #define PY_VERSION              "2.2a2+"
 
         Commit this change.