1 files changed, 11 insertions, 11 deletions

diff --git a/usr.sbin/nfsd/stablerestart.5 b/usr.sbin/nfsd/stablerestart.5
index 8499986056e6..077dc4931380 100644
--- a/usr.sbin/nfsd/stablerestart.5
+++ b/usr.sbin/nfsd/stablerestart.5
@@ -24,23 +24,23 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd September 7, 2007
+.Dd December 3, 2009
 .Dt STABLERESTART 5
 .Os
 .Sh NAME
 .Nm nfs-stablerestart
 .Nd handles restart edge conditions for the
 .Tn NFS
-V4 server
+v4 server
 .Sh SYNOPSIS
 .Nm nfs-stablerestart
 .Sh DESCRIPTION
 The
 .Nm
 file holds information that allows the
-.Tn NFS
-V4 server to restart without always returning the NFSERR_NOGRACE error, as described in the
-.Tn NFS V4
+.Tn NFSv4
+server to restart without always returning the NFSERR_NOGRACE error, as described in the
+.Tn NFSv4
 server specification; see
 .%T "Network File System (NFS) Version 4 Protocol \\*(tNRFC\\*(sP 3530, Section 8.6.3" .
 .Pp
@@ -49,11 +49,11 @@ The first record in the file, as defined by struct nfsf_rec in
 last incarnation of the server and the number of boot times that follows.
 Following this are the number of previous boot times listed in the
 first record.
-The lease duration is used to set the Grace Period.
+The lease duration is used to set the grace period.
 The boot times
 are used to avoid the unlikely occurrence of a boot time being reused,
 due to a TOD clock going backwards. This record and the previous boot times with this boot time added is re-written at the
-end of the Grace Period.
+end of the grace period.
 .Pp
 The rest of the file are appended records, as defined by
 struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used
@@ -77,14 +77,14 @@ a local disk drive that holds the file, or similar.
 .Sh FILES
 .Bl -tag -width /var/db/nfs-stablerestart -compact
 .It Pa /var/db/nfs-stablerestart
-NFS V4 stable restart file
+NFSv4 stable restart file
 .El
 .Sh SEE ALSO
-.Xr nfsv4 4
+.Xr nfsv4 4 ,
 .Xr nfsd 8
 .Sh BUGS
-If the file is empty, the NFS V4 server has no choice but to return
-NFSERR_NOGRACE for all Reclaim requests. Although correct, this is
+If the file is empty, the NFSv4 server has no choice but to return
+NFSERR_NOGRACE for all reclaim requests. Although correct, this is
 a highly undesirable occurrence, so the file should not be lost if
 at all possible. Nfsd will not create the file if it does not
 exist and will simply log a failure to start, in the hopes that the