More validation fixes; building FO-PDF versions of the HOWTO and

the Guide work now!
(This used to be commit 2192c44663d3031cd6c0f228aea4a8cdd2a29a82)

1 files changed, 7 insertions, 7 deletions

diff --git a/docs/Samba-HOWTO-Collection/Diagnosis.xml b/docs/Samba-HOWTO-Collection/Diagnosis.xml
index ffc79c7dcc..9cf797a702 100644
--- a/docs/Samba-HOWTO-Collection/Diagnosis.xml
+++ b/docs/Samba-HOWTO-Collection/Diagnosis.xml
@@ -50,14 +50,14 @@ The procedure is similar for other types of clients.
 
 <para>
 It is also assumed you know the name of an available share in your
-&smb.conf;. I will assume this share is called <smbconfsection>tmp</smbconfsection>.
-You can add a <smbconfsection>tmp</smbconfsection> share like this by adding the
+&smb.conf;. I will assume this share is called <smbconfsection name="tmp"/>.
+You can add a <smbconfsection name="tmp"/> share like this by adding the
 lines shown in <link linkend="tmpshare">the next example</link>.
 </para>
 
 <para><smbconfexample id="tmpshare">
 <title>smb.conf with [tmp] share</title>
-<smbconfsection>[tmp]</smbconfsection>
+<smbconfsection name="[tmp]"/>
 <smbconfoption name="comment">temporary files </smbconfoption>
 <smbconfoption name="path">/tmp</smbconfoption>
 <smbconfoption name="read only">yes</smbconfoption>
@@ -242,7 +242,7 @@ the &smb.conf; file entries as shown in <link linkend="modif1">the next example<
 <para>
 <smbconfexample id="modif1">
 	<title>Configuration for only allowing connections from a certain subnet</title>
-<smbconfsection>[globals]</smbconfsection>
+<smbconfsection name="[globals]"/>
 <member>...</member>
 <smbconfoption name="hosts deny">ALL</smbconfoption>
 <smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy</smbconfoption>
@@ -261,7 +261,7 @@ To solve this problem, change these lines as shown in <link linkend="modif2">the
 <para>
 <smbconfexample id="modif2">
 	<title>Configuration for allowing connections from a certain subnet and localhost</title>
-<smbconfsection>[globals]</smbconfsection>
+<smbconfsection name="[globals]"/>
 <member>...</member>
 <smbconfoption name="hosts deny">ALL</smbconfoption>
 <smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy 127.</smbconfoption>
@@ -383,7 +383,7 @@ It is possible to specify the password along with the username as follows:
 <para>
 Once you enter the password, you should get the <prompt>smb></prompt> prompt. If you
 do not, then look at the error message. If it says <quote><errorname>invalid network
-name</errorname></quote>, then the service <smbconfsection>tmp</smbconfsection> is not correctly setup in your &smb.conf;.
+name</errorname></quote>, then the service <smbconfsection name="tmp"/> is not correctly setup in your &smb.conf;.
 </para>
 
 <para>
@@ -503,7 +503,7 @@ and other config lines in &smb.conf; are correct.
 It's also possible that the server can't work out what user name to connect you as.
 To see if this is the problem, add the line
 <smbconfoption name="user">username</smbconfoption> to the
-<smbconfsection>[tmp]</smbconfsection> section of 
+<smbconfsection name="[tmp]"/> section of 
 &smb.conf; where <parameter>username</parameter> is the
 username corresponding to the password you typed. If you find this
 fixes things, you may need the username mapping option.