Use new definition of <smbconfoption>, fixes a bunch of

validity errors.
(This used to be commit 3eb5c35e47951f320f7c2f4cd478a95f6d48236e)

1 files changed, 13 insertions, 13 deletions

diff --git a/docs/Samba-HOWTO-Collection/Speed.xml b/docs/Samba-HOWTO-Collection/Speed.xml
index 74c6ec2b73..2501d2bb85 100644
--- a/docs/Samba-HOWTO-Collection/Speed.xml
+++ b/docs/Samba-HOWTO-Collection/Speed.xml
@@ -65,7 +65,7 @@ line with the <option>-O</option> option, or in the &smb.conf; file.
 </para>
 
 <para>
-The <smbconfoption><name>socket options</name></smbconfoption> section of the &smb.conf; manual page describes how
+The <smbconfoption name="socket options"/> section of the &smb.conf; manual page describes how
 to set these and gives recommendations.
 </para>
 
@@ -78,7 +78,7 @@ much. The correct settings are very dependent on your local network.
 <para>
 The socket option TCP_NODELAY is the one that seems to make the biggest single difference
 for most networks. Many people report that adding
-<?latex \linebreak ?><smbconfoption><name>socket options</name><value>TCP_NODELAY</value></smbconfoption>
+<?latex \linebreak ?><smbconfoption name="socket options">TCP_NODELAY</smbconfoption>
 doubles the read performance of a Samba drive. The best explanation I have seen for
 this is that the Microsoft TCP/IP stack is slow in sending TCP ACKs.
 </para>
@@ -96,7 +96,7 @@ first be quantitatively measured on the server being configured.
 <title>Read Size</title>
 
 <para>
-The option <smbconfoption><name>read size</name></smbconfoption> affects the overlap of disk
+The option <smbconfoption name="read size"/> affects the overlap of disk
 reads/writes with network reads/writes. If the amount of data being
 transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
 SMBreadbraw) is larger than this value, then the server begins writing
@@ -126,7 +126,7 @@ pointless and will cause you to allocate memory unnecessarily.
 <para>
 	At startup the client and server negotiate a <parameter>maximum transmit</parameter> size,
 which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the <smbconfoption><name>max xmit</name></smbconfoption> option
+maximum size that Samba will negotiate using the <smbconfoption name="max xmit"/> option
 in &smb.conf;. Note that this is the maximum size of SMB requests that 
 Samba will accept, but not the maximum size that the client will accept.
 The client maximum receive size is sent to Samba by the client and Samba
@@ -146,7 +146,7 @@ In most cases the default is the best option.
 <title>Log Level</title>
 
 <para>
-If you set the log level (also known as <smbconfoption><name>debug level</name></smbconfoption>) higher than 2
+If you set the log level (also known as <smbconfoption name="debug level"/>) higher than 2
 then you may suffer a large drop in performance. This is because the
 server flushes the log file after each operation, which can be quite
 expensive. 
@@ -157,20 +157,20 @@ expensive.
 <title>Read Raw</title>
 
 <para>
-The <smbconfoption><name>read raw</name></smbconfoption> operation is designed to be an optimized, low-latency
+The <smbconfoption name="read raw"/> operation is designed to be an optimized, low-latency
 file read operation. A server may choose to not support it,
-however, and Samba makes support for <smbconfoption><name>read raw</name></smbconfoption> optional, with it
+however, and Samba makes support for <smbconfoption name="read raw"/> optional, with it
 being enabled by default.
 </para>
 
 <para>
-In some cases clients do not handle <smbconfoption><name>read raw</name></smbconfoption> very well and actually
+In some cases clients do not handle <smbconfoption name="read raw"/> very well and actually
 get lower performance using it than they get using the conventional
 read operations. 
 </para>
 
 <para>
-So you might like to try <smbconfoption><name>read raw</name><value>no</value></smbconfoption> and see what happens on your
+So you might like to try <smbconfoption name="read raw">no</smbconfoption> and see what happens on your
 network. It might lower, raise or not effect your performance. Only
 testing can really tell.
 </para>
@@ -181,13 +181,13 @@ testing can really tell.
 <title>Write Raw</title>
 
 <para>
-The <smbconfoption><name>write raw</name></smbconfoption> operation is designed to be an optimized, low-latency
+The <smbconfoption name="write raw"/> operation is designed to be an optimized, low-latency
 file write operation. A server may choose to not support it, however, and Samba makes support for
-<smbconfoption><name>write raw</name></smbconfoption> optional, with it being enabled by default.
+<smbconfoption name="write raw"/> optional, with it being enabled by default.
 </para>
 
 <para>
-Some machines may find <smbconfoption><name>write raw</name></smbconfoption> slower than normal write, in which
+Some machines may find <smbconfoption name="write raw"/> slower than normal write, in which
 case you may wish to change this option.
 </para>
 
@@ -198,7 +198,7 @@ case you may wish to change this option.
 
 <para>
 Slow logins are almost always due to the password checking time. Using
-the lowest practical <smbconfoption><name>password level</name></smbconfoption> will improve things. 
+the lowest practical <smbconfoption name="password level"/> will improve things. 
 </para>
 
 </sect1>