From c5ae3a64863842960f42589a5ddc07755b4f6316 Mon Sep 17 00:00:00 2001
From: John Terpstra <jht@samba.org>
Date: Wed, 29 Jun 2005 06:37:37 +0000
Subject: Updating TOSHARG files (This used to be commit
 2ada75f02f4ba7de548a56a14f1bb0281029e063)

---
 docs/Samba3-HOWTO/TOSHARG-Speed.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/Samba3-HOWTO/TOSHARG-Speed.xml')

diff --git a/docs/Samba3-HOWTO/TOSHARG-Speed.xml b/docs/Samba3-HOWTO/TOSHARG-Speed.xml
index 1221eedfb4..4ad59eacdc 100644
--- a/docs/Samba3-HOWTO/TOSHARG-Speed.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-Speed.xml
@@ -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">TCP_NODELAY</smbconfoption>
+<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>
-- 
cgit