On 1/2/25 5:45 PM, Salvatore Bonaccorso wrote:
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@xxxxxxxxxx>
Committed... (tag: nfs-utils-2-8-3-rc1)
steved.
---
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
