linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] man pages: fixed a few typos in a couple man pages
Date: Tue, 04 Oct 2011 12:52:42 -0400	[thread overview]
Message-ID: <4E8B39DA.1060604@RedHat.com> (raw)
In-Reply-To: <1317740912-4589-1-git-send-email-steved@redhat.com>



On 10/04/2011 11:08 AM, Steve Dickson wrote:
> Signed-off-by: Steve Dickson <steved@redhat.com>
> ---
>  utils/exportfs/nfsd.man |    6 +++---
>  utils/nfsd/nfsd.man     |    2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)
Committed....

steved.

> 
> diff --git a/utils/exportfs/nfsd.man b/utils/exportfs/nfsd.man
> index 7365a1b..47b73be 100644
> --- a/utils/exportfs/nfsd.man
> +++ b/utils/exportfs/nfsd.man
> @@ -12,7 +12,7 @@ nfsd \- special filesystem for controlling Linux NFS server
>  .SH DESCRIPTION
>  The
>  .B nfsd
> -filesytem is a special filesystem which provides access to the Linux
> +filesystem is a special filesystem which provides access to the Linux
>  NFS server.  The filesystem consists of a single directory which
>  contains a number of files.  These files are actually gateways into
>  the NFS server.  Writing to them can affect the server.  Reading from
> @@ -86,7 +86,7 @@ should be followed by a newline, with white-space separating the
>  fields, and octal quoting of special characters.
>  
>  On writing this, the program will be able to read back a filehandle
> -for that path as exported to the given client.  The filehandles length
> +for that path as exported to the given client.  The filehandle's length
>  will be at most the number of bytes given.
>  
>  The filehandle will be represented in hex with a leading '\ex'.
> @@ -165,7 +165,7 @@ file.  The user-space program might then write
>  .ti +5
>  nfsd 127.0.0.1 1057206953 localhost
>  .br
> -to indicate that 127.0.0.1 should map to localhost, atleast for now.
> +to indicate that 127.0.0.1 should map to localhost, at least for now.
>  
>  If the program uses select(2) or poll(2) to discover if it can read
>  from the
> diff --git a/utils/nfsd/nfsd.man b/utils/nfsd/nfsd.man
> index d8988d2..1cf9296 100644
> --- a/utils/nfsd/nfsd.man
> +++ b/utils/nfsd/nfsd.man
> @@ -38,7 +38,7 @@ request on all known network addresses.  This may change in future
>  releases of the Linux Kernel.
>  .TP
>  .B \-p " or " \-\-port  port
> -specify a diferent port to listen on for NFS requests. By default,
> +specify a different port to listen on for NFS requests. By default,
>  .B rpc.nfsd
>  will listen on port 2049.
>  .TP

      reply	other threads:[~2011-10-04 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 15:08 [PATCH 1/1] man pages: fixed a few typos in a couple man pages Steve Dickson
2011-10-04 16:52 ` Steve Dickson [this message]

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=4E8B39DA.1060604@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.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 NNTP newsgroup(s).