Fixed few typos in various man pages found by a spellchecker.

4 files changed, 12 insertions, 12 deletions

diff --git a/stap-server.8.in b/stap-server.8.in
index 2ec00c24..262b3fdd 100644
--- a/stap-server.8.in
+++ b/stap-server.8.in
@@ -93,7 +93,7 @@ certificate database, making that server a trusted server for clients using that
 .PP
 The
 .I stap\-client
-program is analagous to the
+program is analogous to the
 .I stap
 front end except that it attempts to find a compatible systemtap server on the
 local network and then attempts to use that server for actions related to
@@ -125,13 +125,13 @@ accepts the following:
 
 .TP
 .B \-\-server=\fIHOSTNAME\fR|\fIIP_ADDRESS\fR[\fB:\fIPORT\fR]
-This option intructs
+This option instructs
 .I stap\-client
 to use the named server instead of looking for one automatically. The server may
 be specified using a valid host name or ip address. If no port is specified, then
 .I stap\-client
-searches for the server among the servers advertizing their presence on the
-local network and uses the port which is being advertized. This is useful for
+searches for the server among the servers advertising their presence on the
+local network and uses the port which is being advertised. This is useful for
 connecting to a specific server on the local network. If a port is specified,
 then
 .I stap\-client
diff --git a/stap.1.in b/stap.1.in
index a8609d6f..7736a612 100644
--- a/stap.1.in
+++ b/stap.1.in
@@ -456,7 +456,7 @@ proceed in a sorted order, by ascending or descending index or value.
 Using the optional
 .BR limit
 keyword limits the number of loop iterations to EXP times.  EXP is
-evaluted once at the beginning of the loop.
+evaluated once at the beginning of the loop.
 .TP
 .BR foreach " ([VAR1, VAR2, ...] " in " ARRAY [ "limit " EXP ]) STMT"
 Same as above, used when the array is indexed with a tuple of keys.
diff --git a/stapprobes.3stap.in b/stapprobes.3stap.in
index b3066611..795a9a92 100644
--- a/stapprobes.3stap.in
+++ b/stapprobes.3stap.in
@@ -37,7 +37,7 @@ that it is optional, and that no error should result if it fails to
 resolve.  Optionalness passes down through all levels of
 alias/wildcard expansion.  Alternately, a probe point may be followed
 by a "!" character, to indicate that it is both optional and
-sufficient.  (Think vaguely of the prolog cut operator.) If it does
+sufficient.  (Think vaguely of the Prolog cut operator.) If it does
 resolve, then no further probe points in the same comma-separated list
 will be resolved.  Therefore, the "!"  sufficiency mark only makes
 sense in a list of probe point alternatives.
@@ -115,7 +115,7 @@ probe point is similar to the
 .IR end
 probe, except that each such probe handler run when the session ends
 after errors have occurred.  In such cases, "end" probes are skipped,
-but each "error" prober is still attempted.  This kind of probe can be
+but each "error" probe is still attempted.  This kind of probe can be
 used to clean up or emit a "final gasp".  It may also be numerically
 parametrized to set a sequence.
 
@@ -606,7 +606,7 @@ The marker name string, which may contain the usual wildcard characters,
 is matched against the names given to the marker macros when the kernel
 and/or module was compiled.    Optionally, you can specify
 .BR format("format") .
-Specifying the marker format string allows differentation between two
+Specifying the marker format string allows differentiation between two
 markers with the same name but different marker format strings.
 
 The handler associated with a marker-based probe may read the
@@ -618,7 +618,7 @@ and string parameters are passed in a type-safe manner.
 
 The marker format string associated with a marker is available in
 .BR $format .
-And also the marker name string is avalable in
+And also the marker name string is available in
 .BR $name .
 
 .SS TRACEPOINTS
@@ -669,10 +669,10 @@ Performance monitor hardware points begin with a
 The next part of the names the event being counted
 .BR counter("event") .
 The event names are processor implementation specific with the
-execption of the generic
+exception of the generic
 .BR cycles " and " instructions
 events, which are available on all processors. This sets up a counter
-on the processor to count the number of events occuring on the
+on the processor to count the number of events occurring on the
 processor. For more details on the performance monitoring events
 available on a specific processor use the command perfmon2 command:
 
diff --git a/staprun.8.in b/staprun.8.in
index b9993288..5fe2e7fa 100644
--- a/staprun.8.in
+++ b/staprun.8.in
@@ -52,7 +52,7 @@ The '_stp_target' variable will be set to PID.
 .TP
 .B \-o FILE
 Send output to FILE. If the module uses bulk mode, the output will
-be in percpu files FILE_x(FILE_cpux in backgroud and bulk mode)
+be in percpu files FILE_x(FILE_cpux in background and bulk mode)
 where 'x' is the cpu number. This supports strftime(3) formats
 for FILE.
 .TP