X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fnetproto.texi;h=d033656901f090a735b39a268ad49b577969b867;hb=87f01e08c6135b3e2b092903d56d7c49b3f126a5;hp=3aef447e4997fcc02890310e1b5cd9aeb867d734;hpb=e63ec3c5453d66ad7a4b25d00a2067ed043b0409;p=govpn.git

diff --git a/doc/netproto.texi b/doc/netproto.texi
index 3aef447..d033656 100644
--- a/doc/netproto.texi
+++ b/doc/netproto.texi
@@ -3,8 +3,7 @@
 
 You can use either UDP or TCP underlying network transport protocols.
 
-TCP consumes more traffic: two additional bytes per packet. Also it is
-has more complex and slightly slower code. Moreover because of packet
-loss and TCP reliability it can lead to "meltdown" effect: significant
-performance decrease of underlying TCP connections. So generally TCP is
-not advisable for VPNs, but it can help with some nasty firewalls.
+TCP is more resource hungry. Moreover because of packet loss and TCP
+reliability it can lead to "meltdown" effect: significant performance
+loss of underlying TCP connections. Generally TCP is not advisable for
+VPNs, but it can help with some nasty firewalls.