From 9c72dd78f25be4a7ffa5af5a242670ec76930d6f Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Sat, 12 Mar 2005 22:34:38 +0000
Subject: Use new definition of <smbconfoption>, fixes a bunch of validity
 errors. (This used to be commit 3eb5c35e47951f320f7c2f4cd478a95f6d48236e)

---
 docs/Samba-HOWTO-Collection/Problems.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/Samba-HOWTO-Collection/Problems.xml')

diff --git a/docs/Samba-HOWTO-Collection/Problems.xml b/docs/Samba-HOWTO-Collection/Problems.xml
index e6507bf3e1..c7b8f9df90 100644
--- a/docs/Samba-HOWTO-Collection/Problems.xml
+++ b/docs/Samba-HOWTO-Collection/Problems.xml
@@ -34,7 +34,7 @@ on the screen.</para>
 <para>
 One of the best diagnostic tools for debugging problems is Samba itself. 
 You can use the <option>-d option</option> for both &smbd; and &nmbd; to specify the 
-<smbconfoption><name>debug level</name></smbconfoption> at which to run. 
+<smbconfoption name="debug level"/> at which to run. 
 See the man pages for <command>smbd, nmbd</command>  and 
 &smb.conf; for more information regarding debugging options. The debug 
 level can range from 1 (the default) to 10 (100 for debugging passwords).
-- 
cgit