diff --git a/Mac/README b/Mac/README
--- a/Mac/README
+++ b/Mac/README
@@ -65,17 +65,17 @@ 2. How do I build a universal binary
 
 You can enable universal binaries by specifying the "--enable-universalsdk"
 flag to configure::
 
   $ ./configure --enable-universalsdk
   $ make
   $ make install
 
-This flag can be used a framework build of python, but also with a classic
+This flag can be used with a framework build of python, but also with a classic
 unix build. Either way you will have to build python on Mac OS X 10.4 (or later)
 with Xcode 2.1 (or later). You also have to install the 10.4u SDK when 
 installing Xcode.
 
 The option ``--enable-universalsdk`` has an optional argument to specify an
 SDK, which defaults to the 10.4u SDK. When you build on OSX 10.5 or later 
 you can use the system headers instead of an SDK::
 
@@ -216,18 +216,18 @@ Mac/Demo.
 The commandline scripts /usr/local/bin/python and pythonw can be used to run
 non-GUI and GUI python scripts from the command line, respectively.
 
 How do I create a binary distribution?
 ======================================
 
 Go to the directory "Mac/OSX/BuildScript". There you'll find a script 
 "build-installer.py" that does all the work. This will download and build
-a number of 3th-party libaries, configures and builds a framework Python,
-installs it, creates the installer pacakge files and then packs this in a 
+a number of 3rd-party libaries, configures and builds a framework Python,
+installs it, creates the installer package files and then packs this in a 
 DMG image.
 
 The script will build a universal binary, you'll therefore have to run this
 script on Mac OS X 10.4 or later and with Xcode 2.1 or later installed.
 
 All of this is normally done completely isolated in /tmp/_py, so it does not
 use your normal build directory nor does it install into /.
 
@@ -253,18 +253,18 @@ The configure script sometimes emits war
 This almost always means you are trying to build a universal binary for
 Python and have libaries in ``/usr/local`` that don't contain the required
 architectures. Temporarily move ``/usr/local`` aside to finish the build.
 
 
 Uninstalling a framework install, including the binary installer
 ================================================================
 
-Uninstalling a framework can be done by manually removing all bits that got installed,
-that's true for both installations from source and installations using the binary installer.
+Uninstalling a framework can be done by manually removing all bits that got installed.
+That's true for both installations from source and installations using the binary installer.
 Sadly enough OSX does not have a central uninstaller.
 
 The main bit of a framework install is the framework itself, installed in
 ``/Library/Frameworks/Python.framework``. This can contain multiple versions
 of Python, if you want to remove just one version you have to remove the
 version-specific subdirectory: ``/Library/Frameworks/Python.framework/Versions/X.Y``.
 If you do that, ensure that ``/Library/Frameworks/Python.framework/Versions/Current``
 is a symlink that points to an installed version of Python.