This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Manual page typos fix


Hi,

we run some man page checking tool as errata process to spot typos &
friends, so instead of complaining internally or filing bugs, I decided
to fix & post it directly.

Petr
>From b2c326e955ed60656a057f3fd7c800b8d5af22a4 Mon Sep 17 00:00:00 2001
From: Petr Muller <pmuller@redhat.com>
Date: Thu, 14 May 2009 18:21:08 +0200
Subject: [PATCH] Fix few typos in stapprobes manpages found by a spellchecker

---
 man/stapprobes.nfs.3stap.in    |   18 +++++++++---------
 man/stapprobes.nfsd.3stap.in   |    8 ++++----
 man/stapprobes.rpc.3stap.in    |    8 ++++----
 man/stapprobes.signal.3stap.in |   10 +++++-----
 man/stapprobes.socket.3stap.in |    2 +-
 5 files changed, 23 insertions(+), 23 deletions(-)

diff --git a/man/stapprobes.nfs.3stap.in b/man/stapprobes.nfs.3stap.in
index 579af53..2196419 100644
--- a/man/stapprobes.nfs.3stap.in
+++ b/man/stapprobes.nfs.3stap.in
@@ -551,7 +551,7 @@ Fires when a previous async read operation failed
 .TP
 .B nfs.aop.readpages
 
-Fies when in readahead way,read several pages once
+Fires when in readahead way,read several pages once
 
 .B Arguments:
 
@@ -577,7 +577,7 @@ Fies when in readahead way,read several pages once
 .TP
 .B nfs.aop.readpages.return
 
-Fies whenever a nfs read pages operation is done 
+Fires whenever a nfs read pages operation is done
 
 .B Arguments:
 
@@ -588,7 +588,7 @@ Fies whenever a nfs read pages operation is done
 .TP
 .B nfs.aop.set_page_dirty
 
-Fies whenever set page dirty on nfs client side
+Fires whenever set page dirty on nfs client side
 
 .B Arguments:
 
@@ -602,7 +602,7 @@ Fies whenever set page dirty on nfs client side
 .TP
 .B nfs.aop.writepage
 
-Fies whenever writing an mapped page to the server from nfs client side
+Fires whenever writing an mapped page to the server from nfs client side
 
 .B Arguments:
 
@@ -644,7 +644,7 @@ Fies whenever writing an mapped page to the server from nfs client side
 .TP
 .B nfs.aop.writepages
 
-Fies whenever writing several dirty pages to the server from nfs client sides
+Fires whenever writing several dirty pages to the server from nfs client sides
 
 .B Arguments:
 
@@ -674,7 +674,7 @@ Fies whenever writing several dirty pages to the server from nfs client sides
 .TP
 .B nfs.aop.prepare_write
 
-Fies whenever prepare a page for writting on nfs client sides
+Fires whenever prepare a page for writing on nfs client sides
 
 .B Arguments:
 
@@ -703,7 +703,7 @@ Fies whenever prepare a page for writting on nfs client sides
 .TP
 .B nfs.aop.commit_write
 
-Fies often after prepare write operation  
+Fires often after prepare write operation
 
 .B Arguments:
 
@@ -771,7 +771,7 @@ Fies often after prepare write operation
   nfs version
 
 .I filename 
-  the name of  file which client opens/searchs on server
+  the name of  file which client opens/searches on server
 
 .I name_len 
   the length of file name
@@ -851,7 +851,7 @@ Fires when client synchronously writes file to server
 .TP
 .B nfs.proc.write.return
 
-Fires when synchronously writting file from server is done
+Fires when synchronously writing file from server is done
 
 .B Arguments:
 
diff --git a/man/stapprobes.nfsd.3stap.in b/man/stapprobes.nfsd.3stap.in
index 239d3b9..275aba7 100644
--- a/man/stapprobes.nfsd.3stap.in
+++ b/man/stapprobes.nfsd.3stap.in
@@ -29,7 +29,7 @@ It contains the following probe points:
 .TP
 .B nfsd.proc.lookup
 
-Fires whenever client opens/searchs file on server 
+Fires whenever client opens/searches file on server
 
 .B Arguments:
 
@@ -348,7 +348,7 @@ Fires when server commits all pending writes to stable storage
 .TP
 .B nfsd.lookup
 
-Fires whenever client opens/searchs file on server
+Fires whenever client opens/searches file on server
 
 .B Arguments:
 
@@ -419,7 +419,7 @@ on server side,only called by nfsd3_proc_create and nfsd4_open
     NFS3_CREATE_EXCLUSIVE,NFS3_CREATE_UNCHECKED,NFS3_CREATE_GUARDED
 
 .I  truncp 
-  trunp arguments, indicates if the file shouldbe truncate
+  trunp arguments, indicates if the file should be truncated
 
 .I  verfier 
   file attributes (atime,mtime,mode).It's used to reset file
@@ -485,7 +485,7 @@ Fires whenever server closes file
 .TP
 .B nfsd.dispatch
 
-Fires whenever server receives NFS operation from client 
+Fires whenever server receives NFS operation from client
 
 .B Arguments:
 
diff --git a/man/stapprobes.rpc.3stap.in b/man/stapprobes.rpc.3stap.in
index 6061b20..02b37a8 100644
--- a/man/stapprobes.rpc.3stap.in
+++ b/man/stapprobes.rpc.3stap.in
@@ -375,7 +375,7 @@ Fires when an RPC client is to be processed
   The procedure number in the request
 
 .I rq_prot
-  The IP protocol of the reqeust
+  The IP protocol of the request
 
 .P
 .TP
@@ -403,7 +403,7 @@ Fires when an RPC client is to be authorised
   The procedure number in the request
 
 .I rq_prot
-  The IP protocol of the reqeust
+  The IP protocol of the request
 
 .P
 .TP
@@ -450,7 +450,7 @@ Fires when want to return reply to client
   The procedure number in the request
 
 .I rq_prot
-  The IP protocol of the reqeust
+  The IP protocol of the request
 
 .P
 .TP
@@ -478,7 +478,7 @@ Fires when a request is to be dropped
   The procedure number in the request
 
 .I rq_prot
-  The IP protocol of the reqeust
+  The IP protocol of the request
 
 .P
 .TP
diff --git a/man/stapprobes.signal.3stap.in b/man/stapprobes.signal.3stap.in
index 9b7ccd5..cdaa51b 100644
--- a/man/stapprobes.signal.3stap.in
+++ b/man/stapprobes.signal.3stap.in
@@ -74,7 +74,7 @@ Fires when return from sending a signal
 
 .RS
 .RS
-- return 0 if the signal is sucessfully sent to a process, 
+- return 0 if the signal is successfully sent to a process,
 which means the following:
 
 <1> the signal is ignored by receiving process
@@ -90,7 +90,7 @@ by user using something other than kill()
   Return values for "send_group_sigqueue"
 
 .RS
-- return 0 if the signal is either sucessfully added into the
+- return 0 if the signal is either successfully added into the
 sigqueue of receiving process or a SI_TIMER entry is already
 queued so just increment the overrun count
 
@@ -100,7 +100,7 @@ queued so just increment the overrun count
   Return values for "send_sigqueue"
 
 .RS
-- return 0 if the signal is either sucessfully added into the
+- return 0 if the signal is either successfully added into the
 sigqueue of receiving process or a SI_TIMER entry is already
 queued so just increment the overrun count
 
@@ -186,8 +186,8 @@ Fires when wake up the process for new active signals
   indicate whether to wake up a task in STOPPED or TRACED state
 
 .I state_mask
-  a string representation indicate the mask of task states 
-that can be woken. Possible values are 
+  a string representation indicate the mask of task states
+that can be woken. Possible values are
 (TASK_INTERRUPTIBLE|TASK_STOPPED|TASK_TRACED) and
 TASK_INTERRUPTIBLE.
 
diff --git a/man/stapprobes.socket.3stap.in b/man/stapprobes.socket.3stap.in
index 6124e7b..fa6f1c0 100644
--- a/man/stapprobes.socket.3stap.in
+++ b/man/stapprobes.socket.3stap.in
@@ -52,7 +52,7 @@ The message sender.
     to convert to a string.
 
     Common values include:
-         0 - IP (Internet Procotol, local interprocess communications)
+         0 - IP (Internet Protocol, local interprocess communications)
          6 - TCP (Transmission Control Protocol)
         17 - UDP (User Datagram Protocol)
        132 - SCTP (Stream Control Transmission Protocol)
-- 
1.6.0.6

>From 1b78acc5f20fb0c9332c20a2e858f407f54d8227 Mon Sep 17 00:00:00 2001
From: Petr Muller <pmuller@redhat.com>
Date: Thu, 14 May 2009 18:22:42 +0200
Subject: [PATCH] Fixed few typos in various man pages found by a spellchecker

---
 stap-server.8.in    |    8 ++++----
 stap.1.in           |    2 +-
 stapprobes.3stap.in |   12 ++++++------
 staprun.8.in        |    2 +-
 4 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/stap-server.8.in b/stap-server.8.in
index 2ec00c2..262b3fd 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 a8609d6..7736a61 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 b306661..795a9a9 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 b999328..5fe2e7f 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
-- 
1.6.0.6


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]