summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNed Deily <nad@acm.org>2012-03-17 17:25:27 (GMT)
committerNed Deily <nad@acm.org>2012-03-17 17:25:27 (GMT)
commitb07b730e067650f8460d16b6a6f3b648ae70da33 (patch)
tree6f359749e700098d013ceff4e5c8bcd66bab5687
parent94a105705f3c1a4eef912fbc11980cc59969a335 (diff)
downloadcpython-b07b730e067650f8460d16b6a6f3b648ae70da33.zip
cpython-b07b730e067650f8460d16b6a6f3b648ae70da33.tar.gz
cpython-b07b730e067650f8460d16b6a6f3b648ae70da33.tar.bz2
Issue #14346: Fix some typos in the Mac/README file.
(Patch by Dionysios Kalofonos)
-rw-r--r--Mac/README10
1 files changed, 5 insertions, 5 deletions
diff --git a/Mac/README b/Mac/README
index 522903a..6c0eb6f 100644
--- a/Mac/README
+++ b/Mac/README
@@ -70,7 +70,7 @@ flag to configure::
$ 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.
@@ -221,8 +221,8 @@ 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
@@ -258,8 +258,8 @@ 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