linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: NeilBrown <neilb@suse.de>, Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, Salvatore Bonaccorso <carnil@debian.org>
Subject: [nfs-utils PATCH] systemd/nfs.systemd.man: Fix small wording typos
Date: Thu,  2 Jan 2025 23:45:11 +0100	[thread overview]
Message-ID: <20250102224510.1145860-2-carnil@debian.org> (raw)

The wording about what is required when configuration changes are done
contained small wording typos. Change the sentence to "When
configuration changes are made, ...".

Fixes: 1b5881d5b9f3 ("Add nfs.systemd man page")
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
---
 systemd/nfs.systemd.man | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/systemd/nfs.systemd.man b/systemd/nfs.systemd.man
index df89ddd13b76..f49e7776a185 100644
--- a/systemd/nfs.systemd.man
+++ b/systemd/nfs.systemd.man
@@ -91,7 +91,7 @@ Most NFS daemons can be restarted at any time.  They will reload any
 state that they need, and continue servicing requests.  This is rarely
 necessary though.
 .PP
-When configuration changesare make, it can be hard to know exactly
+When configuration changes are made, it can be hard to know exactly
 which services need to be restarted to ensure that the configuration
 takes effect.  The simplest approach, which is often the best, is to
 restart everything.  To help with this, the
-- 
2.45.2


             reply	other threads:[~2025-01-02 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 22:45 Salvatore Bonaccorso [this message]
2025-01-03 21:36 ` [nfs-utils PATCH] systemd/nfs.systemd.man: Fix small wording typos Steve Dickson

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=20250102224510.1145860-2-carnil@debian.org \
    --to=carnil@debian.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=steved@redhat.com \
    /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).