1 files changed, 34 insertions, 34 deletions
diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html
index c99a49142c..85863dcd5f 100644
--- a/docs/htmldocs/speed.html
+++ b/docs/htmldocs/speed.html
@@ -5,7 +5,7 @@
 >Samba performance issues</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
 REL="HOME"
 TITLE="SAMBA Project Documentation"
 HREF="samba-howto-collection.html"><LINK
@@ -16,7 +16,7 @@ REL="PREVIOUS"
 TITLE="Group mapping HOWTO"
 HREF="groupmapping.html"><LINK
 REL="NEXT"
-TITLE="Creating Group Profiles"
+TITLE="Creating Group Prolicy Files"
 HREF="groupprofiles.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
@@ -74,15 +74,15 @@ CLASS="CHAPTER"
 ><A
 NAME="SPEED"
 ></A
->Chapter 19. Samba performance issues</H1
+>Chapter 18. Samba performance issues</H1
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3033"
-></A
->19.1. Comparisons</H1
+NAME="AEN2890"
+>18.1. Comparisons</A
+></H1
 ><P
 >The Samba server uses TCP to talk to the client. Thus if you are
 trying to see if it performs well you should really compare it to
@@ -111,9 +111,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3039"
-></A
->19.2. Socket options</H1
+NAME="AEN2896"
+>18.2. Socket options</A
+></H1
 ><P
 >There are a number of socket options that can greatly affect the
 performance of a TCP based server like Samba.</P
@@ -139,9 +139,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3046"
-></A
->19.3. Read size</H1
+NAME="AEN2903"
+>18.3. Read size</A
+></H1
 ><P
 >The option "read size" affects the overlap of disk reads/writes with
 network reads/writes. If the amount of data being transferred in
@@ -165,9 +165,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3051"
-></A
->19.4. Max xmit</H1
+NAME="AEN2908"
+>18.4. Max xmit</A
+></H1
 ><P
 >At startup the client and server negotiate a "maximum transmit" size,
 which limits the size of nearly all SMB commands. You can set the
@@ -188,9 +188,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3056"
-></A
->19.5. Log level</H1
+NAME="AEN2913"
+>18.5. Log level</A
+></H1
 ><P
 >If you set the log level (also known as "debug level") higher than 2
 then you may suffer a large drop in performance. This is because the
@@ -202,9 +202,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3059"
-></A
->19.6. Read raw</H1
+NAME="AEN2916"
+>18.6. Read raw</A
+></H1
 ><P
 >The "read raw" operation is designed to be an optimised, low-latency
 file read operation. A server may choose to not support it,
@@ -224,9 +224,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3064"
-></A
->19.7. Write raw</H1
+NAME="AEN2921"
+>18.7. Write raw</A
+></H1
 ><P
 >The "write raw" operation is designed to be an optimised, low-latency
 file write operation. A server may choose to not support it,
@@ -241,9 +241,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3068"
-></A
->19.8. Slow Clients</H1
+NAME="AEN2925"
+>18.8. Slow Clients</A
+></H1
 ><P
 >One person has reported that setting the protocol to COREPLUS rather
 than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
@@ -258,9 +258,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3072"
-></A
->19.9. Slow Logins</H1
+NAME="AEN2929"
+>18.9. Slow Logins</A
+></H1
 ><P
 >Slow logins are almost always due to the password checking time. Using
 the lowest practical "password level" will improve things a lot. You
@@ -271,9 +271,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3075"
-></A
->19.10. Client tuning</H1
+NAME="AEN2932"
+>18.10. Client tuning</A
+></H1
 ><P
 >Often a speed problem can be traced to the client. The client (for
 example Windows for Workgroups) can often be tuned for better TCP
@@ -431,7 +431,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Creating Group Profiles</TD
+>Creating Group Prolicy Files</TD
 ></TR
 ></TABLE
 ></DIV