Merge pull request #52 from dpage/patch-1

Fix some typos in the README.

1 files changed, 4 insertions, 4 deletions

diff --git a/README.md b/README.md
index b816d55..ac72385 100644
--- a/README.md
+++ b/README.md
@@ -11,10 +11,10 @@ Mac OS X introduced an innovative and very useful way to package applications :
 While their design has all that is needed to ease distribution of resources and frameworks, it
 seems like dynamic libraries (.dylib) are very complicated to distribute. Sure, applications developed
 specifically for OS X won't make use of them, however applications ported from Linux or other Unices may have
-dependencies that will only compile as dylibs. By default, there exists no mechanism to bundle them but some command-line utilities provided by Apple - however it turns out that for a single program it is often necessary to issue dozens of commands! This often leads each porter to develop their own "home solution" wich are often hacky, poorly portable and/or nonoptimal.
+dependencies that will only compile as dylibs. By default, there exists no mechanism to bundle them but some command-line utilities provided by Apple - however it turns out that for a single program it is often necessary to issue dozens of commands! This often leads each porter to develop their own "home solution" wich are often hacky, poorly portable and/or non-optimal.
 
 **dylibbundler** is a small command-line programs that aims to make bundling .dylibs as easy as possible.
-It automatically determines which dylibs are needed by your program, copies these libraries inside the app bundle, and fixes both them and the executable to be ready for distribution... all this with a single command on the teminal! It will also work if your program uses plug-ins that have dependencies too.
+It automatically determines which dylibs are needed by your program, copies these libraries inside the app bundle, and fixes both them and the executable to be ready for distribution... all this with a single command on the terminal! It will also work if your program uses plug-ins that have dependencies too.
 
 It usually involves 2 actions :
 * Creating a directory (by default called *libs*) that can be placed inside the *Contents* folder of the app bundle.
@@ -57,7 +57,7 @@ fixes dependencies where bundled libraries depend on each other. If this option
 > Dylibs in (path) will be ignored. By default, dylibbundler will ignore libraries installed in `/usr/lib` since they are assumed to be present by default on all OS X installations.*(It is usually recommend not to install additional stuff in `/usr/`, always use ` /usr/local/` or another prefix to avoid confusion between system libs and libs you added yourself)*
 
 `-d`, `--dest-dir` (directory)
-> Sets the name of the directory in wich distribution-ready dylibs will be placed, relative to the current working directory. (Default is `./libs`) For an app bundle, it is often conveniant to set it to something like `./MyApp.app/Contents/libs`.
+> Sets the name of the directory in which distribution-ready dylibs will be placed, relative to the current working directory. (Default is `./libs`) For an app bundle, it is often convenient to set it to something like `./MyApp.app/Contents/libs`.
 
 `-p`, `--install-path` (libraries install path)
 > Sets the "inner" installation path of libraries, usually inside the bundle and relative to executable. (Default is `@executable_path/../libs/`, which points to a directory named `libs` inside the `Contents` directory of the bundle.)
@@ -80,7 +80,7 @@ A command may look like
 `% dylibbundler -od -b -x ./HelloWorld.app/Contents/MacOS/helloworld -d ./HelloWorld.app/Contents/libs/`
 
 
-If you want to create a universal binary by merging toghether two builds from PPC and Intel machines, you can ease it up by putting the ppc and intel libs in different directories, then to create the universal binary you only have to lipo the executable.
+If you want to create a universal binary by merging together two builds from PPC and Intel machines, you can ease it up by putting the ppc and intel libs in different directories, then to create the universal binary you only have to lipo the executable.
 <code>
 <pre>
 % dylibbundler -od -b -x ./HelloWorld.app/Contents/MacOS/helloworld