diff -Nur plpa-0.9a1-orig/README plpa-0.9a1/README
--- plpa-0.9a1-orig/README	2005-12-14 01:32:53.000000000 +0100
+++ plpa-0.9a1/README	2005-12-16 16:44:34.000000000 +0100
@@ -34,7 +34,7 @@
 three different APIs (with different numbers and types of
 parameters) throughout their life in Linux.  Ick.
 
-The PLPA is an attempt to solve this problem by providing a sinlge API
+The PLPA is an attempt to solve this problem by providing a single API
 that developers can write to.  It provides two things:
 
 1. A single API that developers can write to, regardless of what
@@ -115,7 +115,7 @@
 
    This is fortunately restricted to some older versions of glibc, and
    is relatively easy to check for at run-time.  PLPA reliably detects
-   this situation and run-time and returns appropriate error codes
+   this situation at run-time and returns appropriate error codes
    (ENOSYS).
 
    The original SuSE 9.1 version seems to have this problem, but it was
@@ -160,14 +160,14 @@
 ---------------------------------------
 
 As much as Linux binaries are portable, yes.  That is, if you have
-within your power to make an binary that is runnable on several
+within your power to make a binary that is runnable on several
 different Linux distributions/versions/etc., then you may run into
 problems with the Linux processor affinity functions.  PLPA attempts
 to solve this problem for you by *also* making the Linux processor
 affinity calls be binary portable.
 
 Hence, you need to start with something that is already binary
-portable (perahps linking everything statically) -- then PLPA will be
+portable (perhaps linking everything statically) -- then PLPA will be
 of help to you.  Do not fall into the misconception that PLPA will
 magically make your executable be binary portable between different
 Linux variants.
@@ -179,14 +179,14 @@
 
 There are two main uses of the PLPA:
 
-1. Using the plpa_info executable to if your system supports processor
-   affinity and the PLPA can determine which to use at run-time.
+1. Using the plpa_info executable to check if your system supports
+   processor affinity and the PLPA can determine which to use at run-time.
 2. Developers using the PLPA library to enable source and binary Linux
    processor affinity portability.
 
 In more detail:
 
-1. The plpa_info exectuable is a simple call into the PLPA library
+1. The plpa_info executable is a simple call into the PLPA library
    that checks which API variant the system it is running on has.  If
    the kernel supports processor affinity and the PLPA is able to
    figure out which API variant to use, it prints "PLPA_PROBE_OK".
@@ -203,7 +203,7 @@
    int plpa_sched_setaffinity(pid_t pid, size_t cpusetsize,
                               const plpa_cpu_set_t *cpuset);
 
-   int plpa_sched_setaffinity(pid_t pid, size_t cpusetsize,
+   int plpa_sched_getaffinity(pid_t pid, size_t cpusetsize,
                               const plpa_cpu_set_t *cpuset)
 
    These functions perform the run-time test outlined above and
@@ -244,7 +244,7 @@
 shell$ make install
 
 Depending on your --prefix, you may need to run the "make install"
-step as root or some other privlidged user.
+step as root or some other privileged user.
 
 "make install" will install the following:
 
@@ -263,7 +263,7 @@
 
 "make uninstall" will fully uninstall PLPA from the prefix directory
 (again, depending in filesystem permissions, you may need to run this
-as root or some privlidged user).
+as root or some privileged user).
 
 ===========================================================================
 
@@ -276,7 +276,7 @@
 (after all, PLPA is a tiny little project -- why make users bother
 with it?).
 
-When be used in "included" mode, PLPA will:
+When used in "included" mode, PLPA will:
 
 - not install any header files
 - not build or install plpa_info
diff -Nur plpa-0.9a1-orig/src/libplpa/plpa_dispatch.c plpa-0.9a1/src/libplpa/plpa_dispatch.c
--- plpa-0.9a1-orig/src/libplpa/plpa_dispatch.c	2005-12-14 00:19:07.000000000 +0100
+++ plpa-0.9a1/src/libplpa/plpa_dispatch.c	2005-12-16 16:20:00.000000000 +0100
@@ -102,7 +102,7 @@
 
 
 /*
- * Call the kernel's setaffinity, massaging the user's input
+ * Call the kernel's getaffinity, massaging the user's input
  * parameters as necessary
  */
 int PLPA_NAME(sched_getaffinity)(pid_t pid, size_t cpusetsize,