From 841de8de3eb51390206ac1b456bf5c9c0755e867 Mon Sep 17 00:00:00 2001
From: John Terpstra <jht@samba.org>
Date: Thu, 16 Jun 2005 03:34:42 +0000
Subject: Fix typos. (This used to be commit
 0a84e3291686e84450c674212acbb4f243dd7c65)

---
 docs/Samba3-HOWTO/TOSHARG-BDC.xml              | 2 +-
 docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml    | 6 +++---
 docs/Samba3-HOWTO/TOSHARG-foreword-cargill.xml | 2 +-
 docs/Samba3-HOWTO/TOSHARG-glossary.xml         | 2 --
 docs/Samba3-HOWTO/index.xml                    | 2 +-
 5 files changed, 6 insertions(+), 8 deletions(-)

(limited to 'docs/Samba3-HOWTO')

diff --git a/docs/Samba3-HOWTO/TOSHARG-BDC.xml b/docs/Samba3-HOWTO/TOSHARG-BDC.xml
index 9b62564ba8..2d601af1b4 100644
--- a/docs/Samba3-HOWTO/TOSHARG-BDC.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-BDC.xml
@@ -382,7 +382,7 @@ implementation requires the DMB to be on the same machine as the PDC.
 
 <para>
 Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to
-<link linkend="NetworkBrwosing">Network Browsing</link>,<link linkend="netdiscuss">Discussion</link>
+<link linkend="NetworkBrowsing">Network Browsing</link>,<link linkend="netdiscuss">Discussion</link>
 for more information regarding TCP/IP network protocols and how SMB/CIFS names are handled.
 </para>
 
diff --git a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml
index 518661359f..27d13b72d6 100644
--- a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml
@@ -430,7 +430,7 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	ink. <quote>Unknown</quote> data are tagged by CUPS as <parameter>MIME type: application/octet-stream</parameter>
 	and not allowed to go to the printer. By default, you can only send other (known) MIME types <quote>raw</quote>.
 	Sending data <quote>raw</quote> means that CUPS does not try to convert them and passes them to the printer
-	untouched (see <link linkend="CUPSprinting">the CUPS Printing Chapter</link> for more background explanations).
+	untouched (see <link linkend="CUPS-printing">the CUPS Printing Chapter</link> for more background explanations).
 	</para>
 	</formalpara>
 
@@ -458,7 +458,7 @@ application/octet-stream   application/vnd.cups-raw   0   -
 	drivers onto the Samba server first (<smbconfsection name="[print$]"/>
 	share). For a discussion on how to deposit printer drivers on the
 	Samba host (so the Windows clients can download and use them via
-	<quote>Point'n'Print</quote>), please refer to the <link linkend="classicprinting">Classic Printing
+	<quote>Point'n'Print</quote>), please refer to the <link linkend="classicalprinting">Classic Printing
 	chapter</link> of this Samba-3 HOWTO Collection. There you will find a description or reference to
 	three methods of preparing the client drivers on the Samba server:
 	</para>
@@ -2480,7 +2480,7 @@ privileges to do this.
 <note><para>
 <indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
 Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all
-printers to this one by proceeding as described in <link linkend="printing">Classical Printing
+printers to this one by proceeding as described in <link linkend="classicalprinting">Classical Printing
 Support</link>. Either change a driver for an existing printer by running the <guilabel>Printer
 Properties</guilabel> dialog, or use <command>rpcclient</command> with the <command>setdriver</command>
 subcommand.
diff --git a/docs/Samba3-HOWTO/TOSHARG-foreword-cargill.xml b/docs/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
index 532b2033df..9b7f9c394e 100644
--- a/docs/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
@@ -20,7 +20,7 @@ John provided.
 </para>
 
 <para>
-The book that you have before you focuses on a particular standardized way of doing something – hence, it is a
+The book that you have before you focuses on a particular standardized way of doing something hence, it is a
 book about a standard. The most important thing to keep in mind about a standard is the rationale for its
 creation. Standards are created not for technical reasons, not for business reasons, but for a deeper and much
 more compelling reason. Standards are created and used to allow people to communicate in a meaningful way.
diff --git a/docs/Samba3-HOWTO/TOSHARG-glossary.xml b/docs/Samba3-HOWTO/TOSHARG-glossary.xml
index da61267e4e..2521f6c9f0 100644
--- a/docs/Samba3-HOWTO/TOSHARG-glossary.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-glossary.xml
@@ -154,8 +154,6 @@
 		</para></glossdef>
 	</glossentry>
 
-	<?latex \newpage ?>
-	
 	<glossentry>
 		<glossterm>Local Master Browser</glossterm>
 		<acronym>LMB</acronym>
diff --git a/docs/Samba3-HOWTO/index.xml b/docs/Samba3-HOWTO/index.xml
index 4d1e8f01d0..209ed8aed1 100644
--- a/docs/Samba3-HOWTO/index.xml
+++ b/docs/Samba3-HOWTO/index.xml
@@ -151,7 +151,7 @@ The chapters in this part each cover specific Samba features.
 
 <!-- Comment out the following line to include the manpages.
 	 *Please* do not commit with the line below enabled! -->
-	 <!--	 <xi:include href="manpages.xml"/> -->
+	<!--	 <xi:include href="manpages.xml"/> -->
 	<xi:include href="manpages.xml"/>
 	<xi:include href="http://www.gnu.org/licenses/gpl.xml"/>
 
-- 
cgit