Fix typos in several text files

4 files changed, 12 insertions, 12 deletions

diff --git a/NEWS b/NEWS
index a23d56a1..86a7a824 100644
--- a/NEWS
+++ b/NEWS
@@ -20,8 +20,8 @@
 
   See initscript/README.stap-server for details.
 
-- Some of the of the compile server client, server and certificate
-  management tools have been moved from $bindir to $libexecdir/systemtap.
+- Some of the compile server client, server and certificate management
+  tools have been moved from $bindir to $libexecdir/systemtap.
   You should use the new stap-server script or the stap-server initscript
   for server management where possible. The stap-server script provides the same
   functionality as the stap-server initscript except that the servers are
diff --git a/README.security b/README.security
index 323840f6..4f649d5d 100644
--- a/README.security
+++ b/README.security
@@ -71,7 +71,7 @@ the permissions should be 755, like this:
 drwxr-xr-x 2 root root 4096 2007-08-07 13:54 systemtap/
 
 2) More permissive usage.  If all systemtap developers should be able
-to add "approved" systemtap modules to /lib/modules/VERSION/system,
+to add "approved" systemtap modules to /lib/modules/VERSION/systemtap,
 its permissions should be 775 (and be owned by root, group stapdev),
 like this:
 
@@ -108,6 +108,6 @@ permitted to have.  In addition, the effective set of capabilities, the
 capabilities from the permitted set that are currently enabled, is
 cleared.  When needed, a particular capability is enabled, the
 operation is performed, then the capability is disabled.  The staprun
-program was designed this way to prevent several classes of security
+program was designed in this way to prevent several classes of security
 attacks. Security is also heightened by the fact that the only
 external program that staprun executes is stapio.
diff --git a/initscript/README.stap-server b/initscript/README.stap-server
index c4089299..b1cbdbbd 100644
--- a/initscript/README.stap-server
+++ b/initscript/README.stap-server
@@ -77,7 +77,7 @@ to specify servers to be managed.
  The default architecture is the architecture of the host.
 
 2.3.3 -r kernel-release
- This option specifies the target kernel release of the server an is
+ This option specifies the target kernel release of the server and is
  analogous to the -r option of 'stap'. See stap(1) for more details.
  The default release is that of the currently running kernel.
 
@@ -88,7 +88,7 @@ to specify servers to be managed.
  must be a member of the group 'stap-server'.
 
 2.3.5 -I path
- This option specifies an additional path to be searched by thes server for
+ This option specifies an additional path to be searched by the server for
  tapsets and is analogous to the -I option of 'stap'. See stap(1) for more
  details.
 
@@ -119,14 +119,14 @@ to specify servers to be managed.
  the given nickname is found, and the action is 'start' (or an action behaving
  like 'start' (see below), the server will be started with the given nickname.
  If no configuration with the given nickname is found, and the action is not
- 'start' (or an action behaving" "like 'start', it is an error. If a nickname is
+ 'start' (or an action behaving like 'start', it is an error. If a nickname is
  not specified for a server, its nickname will be its process id.
 
 2.3.10 -p pid
  This option allows the specification of a server configuration by process id.
  When -p is specified, a currently running server with the given process id will
  be searched for. If no such server is found, it is an error. If a server with
- the given procss id is found, the -a, -r, -I, -R, -B and -u options for that
+ the given process id is found, the -a, -r, -I, -R, -B and -u options for that
  server will be used as if they were specified on the command line.
 
 3. Files
diff --git a/initscript/README.systemtap b/initscript/README.systemtap
index ebce285e..61bd5b24 100644
--- a/initscript/README.systemtap
+++ b/initscript/README.systemtap
@@ -199,7 +199,7 @@ Configuration file allows us
 
 4.1.9 AUTOCOMPILE
  If this is set 'yes', systemtap initscript automatically tries to compile
- specified script if there is no valid cache. Otherwides, it just fails to
+ specified script if there is no valid cache. Otherwise, it just fails to
  run script(s).
  (default: yes)
 
@@ -396,10 +396,10 @@ script2_REQ=script1
   resulting module on the client host.
 
 6.1.2 Unprivileged Users (Module Signing)
-  If the user on the client host is a an ordinary unprivileged user or a member
+  If the user on the client host is an ordinary unprivileged user or a member
   of the group stapusr, he will get an error when running the example above,
   since he does not have authority to load the unsigned module returned by the
-  server. Howeverm if he is a member of the group stapusr and if he can get the
+  server. However if he is a member of the group stapusr and if he can get the
   module signed by a trusted signer, he will be able to load it.
 
   The server will sign the module if the --unprivileged option is specified by
@@ -428,7 +428,7 @@ script2_REQ=script1
   The example above should now work as expected.   
 
 6.1.3 Ordinary Users
-  Ordinary users are users who are not root and not a member of either of the
+  Ordinary users are users who are not root or a member of either of the
   groups stapdev or stapusr.
 
   These users can still use the stap-server service to compile their scripts