- Updating NFS doc to use services instead of specific binaries. Also offered a couple of minor points of clarification in the text.

- Clean up some contractions and a double the.

PR:		180955
Submitted by:	Ken Reed <kreed002@gmail.com>
Reviewed by:	bjk, Allan Jude

en_US.ISO8859-1/books/handbook/network-servers/chapter.xml

@@ -267,7 +267,7 @@
     </sect2>
 
     <sect2 id="network-inetd-conf">
-      <!-- XXX This section isn't very clear, and could do with some lovin' -->
+      <!-- XXX This section is not very clear and could do with some tlc -->
       <title><filename>inetd.conf</filename></title>
 
       <para>Configuration of <application>inetd</application> is
@@ -819,20 +819,15 @@ mountd_flags="-r"</programlisting>
       <para>Please refer to <xref linkend="configtuning-rcd"/> for
 	more information about using rc scripts.</para>
 
-      <para>Alternatively, a reboot will make FreeBSD set everything
+      <para>NFS services can now be started by running the following
-	up properly.  A reboot is not necessary though.
+	command, on the <acronym>NFS</acronym> server, as 
-	Executing the following commands as <username>root</username>
+	<username>root</username>:</para>
-	should start everything up.</para>
 
-      <para>On the <acronym>NFS</acronym> server:</para>
+      <screen>&prompt.root; <userinput>service nfsd start</userinput></screen>
-
-      <screen>&prompt.root; <userinput>rpcbind</userinput>
-&prompt.root; <userinput>nfsd -u -t -n 4</userinput>
-&prompt.root; <userinput>mountd -r</userinput></screen>
 
       <para>On the <acronym>NFS</acronym> client:</para>
 
-      <screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen>
+      <screen>&prompt.root; <userinput>service nfsclient restart</userinput></screen>
 
       <para>Now everything should be ready to actually mount a remote
 	file system.  In these examples the server's name will be
@@ -1609,7 +1604,7 @@ Exports list on foobar:
 	    good reason, never propagate passwords for
 	    <username>root</username> and other administrative
 	    accounts to all the servers in the NIS domain.  Therefore,
-	    before the the NIS maps are initialized, configure the
+	    before the NIS maps are initialized, configure the
 	    primary password files:</para>
 
 	  <screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
@@ -1649,7 +1644,7 @@ Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
 Ok, please remember to go back and redo manually whatever fails.
-If you don't, something might not work.
+If not, something might not work.
 At this point, we have to construct a list of this domains YP servers.
 rod.darktech.org is already known as master server.
 Please continue to add any slave servers, one per line. When you are
@@ -1711,7 +1706,7 @@ Questions will all be asked at the beginning of the procedure.
 Do you want this procedure to quit on non-fatal errors? [y/n: n]  <userinput>n</userinput>
 
 Ok, please remember to go back and redo manually whatever fails.
-If you don't, something might not work.
+If not, something might not work.
 There will be no further questions. The remainder of the procedure
 should take a few minutes, to copy the databases from ellington.
 Transferring netgroup...
@@ -1756,7 +1751,7 @@ Transferring hosts.byname...
 ypxfr: Exiting: Map successfully transferred
 
 coltrane has been setup as an YP slave server without any errors.
-Don't forget to update map ypservers on ellington.</screen>
+Remember to update map ypservers on ellington.</screen>
 
 	  <para>There should be a directory called
 	    <filename>/var/yp/test-domain</filename>.  Copies of the