From 6bbe4181fce653a91d3c6e5ab85e140ffe35e804 Mon Sep 17 00:00:00 2001
From: z3APA3A <3APA3A@3proxy.ru>
Date: Fri, 6 Oct 2017 21:39:28 +0300
Subject: [PATCH] update to high load documentation

---
 doc/html/highload.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/html/highload.html b/doc/html/highload.html
index 70594be..dd25296 100644
--- a/doc/html/highload.html
+++ b/doc/html/highload.html
@@ -189,8 +189,8 @@ you can eliminate Nagle's algorithm delay with TCP_NODELAY flag. Usage example:
 proxy -osTCP_NODELAY -ocTCP_NODELAY
 </pre>
 sets TCP_NODELAY for client (oc) and server (os) connections.
-<p>Do not use TCP_NODELAY on slow connections, if connection bandwidth is
-bottleneck, or because it may be more bandwidth-consuming.
+<p>Do not use TCP_NODELAY on slow connections with high delays and then
+connection bandwidth is a bottleneck.
 <h4>Use slice to speedup large data amount transfers</h4>
 slice() allows to copy data between connections without copying to process
 addres space. It can speedup proxy on high bandwidth connections, if most
@@ -203,7 +203,7 @@ devel version. Do not use it in production without testing. Slice requires
 more system buffers, but reduces process memory usage.
 Do not use slice if there is a lot of short-living connections with no bandwidth
 requirements.
-<p>Use slice only on high-speed connections (e.g. 10GBE), where processor or
+<p>Use slice only on high-speed connections (e.g. 10GBE), if processor or
 bus are bottlenecks.
 <p>TCP_NODELAY and slice are not contrary to each over and can be combined on
 high-speed connections.