From 721195f77b49e7c341970ad78834a71641ae9577 Mon Sep 17 00:00:00 2001
From: Alexander Bokovoy <ab@samba.org>
Date: Wed, 30 Apr 2003 22:36:16 +0000
Subject: small fixes (This used to be commit
 5b4274c3a10c3ab133fb8a0b8cff41413224f88a)

---
 docs/docbook/devdoc/encryption.xml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'docs/docbook/devdoc')

diff --git a/docs/docbook/devdoc/encryption.xml b/docs/docbook/devdoc/encryption.xml
index 3ca8aa109c..56a1d10c9c 100644
--- a/docs/docbook/devdoc/encryption.xml
+++ b/docs/docbook/devdoc/encryption.xml
@@ -90,8 +90,8 @@
 </sect1>
 
 <sect1>
-	<title><anchor id="SMBPASSWDFILEFORMAT"/>The smbpasswd file</title>
-	
+	<title>The smbpasswd file</title>
+	<anchor id="SMBPASSWDFILEFORMAT"/>
 	<para>In order for Samba to participate in the above protocol 
 	it must be able to look up the 16 byte hashed values given a user name.
 	Unfortunately, as the UNIX password value is also a one way hash
@@ -169,7 +169,8 @@ username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	entry would look like :</para>
 
 	<para><programlisting>
-	bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
+bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+	[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
 	</programlisting></para>
 	
 	<para>If you are allowing users to use the smbpasswd command to set 
-- 
cgit