1 files changed, 33 insertions, 34 deletions
diff --git a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml
index c1874d0e49..d2c981c427 100644
--- a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml
@@ -4,12 +4,12 @@
 <chapterinfo>
 	&author.jht;
 </chapterinfo>
-<title>Stand-alone Servers</title>
+<title>Standalone Servers</title>
 
 <para>
-Stand-alone Servers are independent of Domain Controllers on the network.
-They are not Domain Members and function more like workgroup servers. In many
-cases a Stand-alone Server is configured with a minimum of security control
+Standalone servers are independent of domain controllers on the network.
+They are not domain members and function more like workgroup servers. In many
+cases a standalone server is configured with a minimum of security control
 with the intent that all data served will be readily accessible to all users.
 </para>
 
@@ -17,25 +17,25 @@ with the intent that all data served will be readily accessible to all users.
 <title>Features and Benefits</title>
 
 <para>
-Stand-alone Servers can be as secure or as insecure as needs dictate. They can
+Standalone servers can be as secure or as insecure as needs dictate. They can
 have simple or complex configurations. Above all, despite the hoopla about
-Domain Security they remain a common installation.
+domain security, they remain a common installation.
 </para>
 
 <para>
 If all that is needed is a server for read-only files, or for
 printers alone, it may not make sense to effect a complex installation.
-For example: A drafting office needs to store old drawings and reference
-standards. No-one can write files to the server as it is legislatively
-important that all documents remain unaltered. A share mode read-only Stand-alone
-Server is an ideal solution.
+For example, a drafting office needs to store old drawings and reference
+standards. Noone can write files to the server because it is legislatively
+important that all documents remain unaltered. A share-mode read-only standalone
+server is an ideal solution.
 </para>
 
 <para>
 Another situation that warrants simplicity is an office that has many printers
 that are queued off a single central server. Everyone needs to be able to print
-to the printers, there is no need to effect any access controls and no files will
-be served from the print server. Again, a share mode Stand-alone Server makes
+to the printers, there is no need to effect any access controls, and no files will
+be served from the print server. Again, a share-mode standalone server makes
 a great solution.
 </para>
 </sect1>
@@ -44,34 +44,34 @@ a great solution.
 <title>Background</title>
 
 <para>
-The term <emphasis>Stand-alone Server</emphasis> means that it
+The term <emphasis>standalone server</emphasis> means that it
 will provide local authentication and access control for all resources
 that are available from it. In general this means that there will be a
 local user database. In more technical terms, it means resources
-on the machine will be made available in either SHARE mode or in
-USER mode.
+on the machine will be made available in either <emphasis>share</emphasis> mode or in
+<emphasis>user</emphasis> mode.
 </para>
 
 <para>
-No special action is needed other than to create user accounts. Stand-alone
+No special action is needed other than to create user accounts. Standalone
 servers do not provide network logon services. This means that machines that
 use this server do not perform a domain logon to it. Whatever logon facility
 the workstations are subject to is independent of this machine. It is, however,
-necessary to accommodate any network user so the logon name they use will
-be translated (mapped) locally on the Stand-alone Server to a locally known
+necessary to accommodate any network user so the logon name he or she uses will
+be translated (mapped) locally on the standalone server to a locally known
 user name. There are several ways this can be done.
 </para>
 
 <para>
-Samba tends to blur the distinction a little in respect of what is
-a Stand-alone Server. This is because the authentication database may be
+Samba tends to blur the distinction a little in defining
+a standalone server. This is because the authentication database may be
 local or on a remote server, even if from the SMB protocol perspective
 the Samba server is not a member of a domain security context.
 </para>
 
 <para>
-Through the use of Pluggable Authentication Modules (PAM) and the name service switcher (NSSWITCH),
-which maintains the UNIX-user database) the source of authentication may reside on 
+Through the use of Pluggable Authentication Modules (PAM) and the name service switcher (NSSWITCH,
+which maintains the UNIX-user database), the source of authentication may reside on 
 another server. We would be inclined to call this the authentication server.
 This means that the Samba server may use the local UNIX/Linux system password database
 (<filename>/etc/passwd</filename> or <filename>/etc/shadow</filename>), may use a
@@ -85,8 +85,7 @@ for authentication.
 <title>Example Configuration</title>
 
 <para>
-The examples, <link linkend="simplynice">Reference Documentation Server</link>, and 
-<link linkend="SimplePrintServer">Central Print Serving</link>,
+Examples 7.3.1 and 7.3.2
 are designed to inspire simplicity. It is too easy to attempt a high level of creativity
 and to introduce too much complexity in server and network design.
 </para>
@@ -96,7 +95,7 @@ and to introduce too much complexity in server and network design.
 
 <para>
 Configuration of a read-only data server that everyone can access is very simple.
-<link linkend="simplynice">Following example</link> is the &smb.conf; file that will do this. Assume that all the reference documents
+<link linkend="simplynice">The following example (7.3.1)</link> is the &smb.conf; file that will do this. Assume that all the reference documents
 are stored in the directory <filename>/export</filename>, and the documents are owned by a user other than
 nobody. No home directories are shared, and there are no users in the <filename>/etc/passwd</filename>
 UNIX system database. This is a simple system to administer.
@@ -120,10 +119,10 @@ UNIX system database. This is a simple system to administer.
 </example>
 
 <para>
-In <link linkend="simplynice">the example</link> above, the machine name is set to &example.server.samba;, the workgroup is set to the name
+In <link linkend="simplynice">this example</link>, the machine name is set to &example.server.samba;, and the workgroup is set to the name
 of the local workgroup (&example.workgroup;) so the machine will appear together with systems with
 which users are familiar. The only password backend required is the <quote>guest</quote> backend to allow default
-unprivileged account names to be used. As there is a WINS server on this network, we of obviously make use of it.
+unprivileged account names to be used. As there is a WINS server on this network, we of course make use of it.
 </para>
 
 </sect2>
@@ -137,14 +136,14 @@ on your system.
 </para>
 
 <orderedlist>
-<title> Assumptions:</title>
+<title> Assumptions</title>
 	<listitem><para>
 	The print server must require no administration.
 	</para></listitem>
 
 	<listitem><para>
 	The print spooling and processing system on our print server will be CUPS.
-	(Please refer to <link linkend="CUPS-printing">CUPS Printing Support</link> for more information).
+	(Please refer to <link linkend="CUPS-printing">CUPS Printing Support</link>, for more information).
 	</para></listitem>
 
 	<listitem><para>
@@ -153,7 +152,7 @@ on your system.
 	</para></listitem>
 
 	<listitem><para>
-	All workstations will use only postscript drivers. The printer driver
+	All workstations will use only PostScript drivers. The printer driver
 	of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.
 	</para></listitem>
 </orderedlist>
@@ -162,7 +161,7 @@ on your system.
 In this example our print server will spool all incoming print jobs to
 <filename>/var/spool/samba</filename> until the job is ready to be submitted by
 Samba to the CUPS print processor. Since all incoming connections will be as
-the anonymous (guest) user, two things will be required:
+the anonymous (guest) user, two things will be required to enable anonymous printing.
 </para>
 
 <itemizedlist>
@@ -192,7 +191,7 @@ the anonymous (guest) user, two things will be required:
 </itemizedlist>
 
 <para>
-The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">the next example</link>.
+The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">Example 7.3.2</link>.
 </para>
 
 <example id="AnonPtrSvr">
@@ -226,8 +225,8 @@ On CUPS-enabled systems there is a facility to pass raw data directly to the pri
 intermediate processing via CUPS print filters. Where use of this mode of operation is desired,
 it is necessary to configure a raw printing device. It is also necessary to enable the raw mime
 handler in the <filename>/etc/mime.conv</filename> and <filename>/etc/mime.types</filename>
-files. Refer to <link linkend="cups-raw">Explicitly Enable <quote>raw</quote> Printing for 
-<emphasis>application/octet-stream</emphasis></link>.
+files. Refer to <link linkend="CUPS-printing">CUPS Printing Support</link>, <link linkend="cups-raw">Explicitly Enable raw Printing for 
+application/octet-stream</link>.
 </para></note>
 
 </sect2>