From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Petr Muller <pmuller@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: [PATCH] Manual page typos fix
Date: Thu, 14 May 2009 18:27:00 -0000 [thread overview]
Message-ID: <20090514182721.GA30963@in.ibm.com> (raw)
In-Reply-To: <1242318902.3322.3.camel@ziltoid.englab.brq.redhat.com>
On Thu, May 14, 2009 at 06:35:02PM +0200, Petr Muller wrote:
> 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
>
Shouldn't the above line be:
"Fires when in readahead way, read several pages once"?
You missed the space after the comma.
Thanks,
K.Prasad
next prev parent reply other threads:[~2009-05-14 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 16:35 Petr Muller
2009-05-14 18:27 ` K.Prasad [this message]
2009-05-15 8:15 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090514182721.GA30963@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=pmuller@redhat.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).