Re: [PATCH] README: fix typos and grammar

From: Steve Dickson <steved@redhat.com>
To: yegorslists@googlemail.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] README: fix typos and grammar
Date: Sat, 19 Nov 2022 14:49:13 -0500	[thread overview]
Message-ID: <3abb5a3b-d800-3c22-5793-0ce20e71343a@redhat.com> (raw)
In-Reply-To: <20221115103116.11038-1-yegorslists@googlemail.com>


On 11/15/22 5:31 AM, yegorslists@googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> Also remove unneeded spaces.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Committed...

steved.
> ---
>   README | 14 +++++++-------
>   1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/README b/README
> index 5e982409..0b62a4f1 100644
> --- a/README
> +++ b/README
> @@ -25,7 +25,7 @@ Unpack the sources and run these commands:
>       # ./configure
>       # make
>   
> -To install binaries and documenation, run this command:
> +To install binaries and documentation, run this command:
>   
>       # make install
>   
> @@ -40,7 +40,7 @@ Updating to the latest head after you've already got it.
>   
>   	git pull
>   
> -Building requires that autotools be installed.  To invoke them
> +Building requires that autotools be installed. To invoke them
>   simply
>   
>   	sh autogen.sh
> @@ -95,27 +95,27 @@ scripts can be written to work correctly.
>   
>      D/ rpc.statd --no-notify
>          It is best if statd is started before nfsd though this isn't
> -       critical.  Certainly it should be at most a few seconds after
> +       critical. Certainly, it should be at most a few seconds after
>          nfsd.
>          When nfsd starts it will start lockd. If lockd then receives a
> -       lock request it will communicate with statd.  If statd is not
> +       lock request, it will communicate with statd. If statd is not
>          running lockd will retry, but it won't wait forever for a
>          reply.
>          Note that if statd is started before nfsd, the --no-notify
> -       option must be used.  If notify requests are sent out before
> +       option must be used. If notify requests are sent out before
>          nfsd start, clients may try to reclaim locks and, on finding
>          that lockd isn't running, they will give up and never reclaim
>          the lock.
>          rpc.statd is only needed for NFSv2 and NFSv3 support.
>   
>      E/ rpc.nfsd
> -       Starting nfsd will automatically start lockd.  The nfs server
> +       Starting nfsd will automatically start lockd. The nfs server
>          will now be fully active and respond to any requests from
>          clients.
>          
>      F/ sm-notify
>          This will notify any client which might have locks from before
> -       a reboot to try to reclaim their locks.  This should start
> +       a reboot to try to reclaim their locks. This should start
>          immediately after rpc.nfsd is started so that clients have a
>          chance to reclaim locks within the 90 second grace period.
>          sm-notify is only needed for NFSv2 and NFSv3 support.