X-Git-Url: http://git.harvie.cz/?p=svn%2FPrometheus-QoS%2F.git;a=blobdiff_plain;f=sample-configuration%2FREADME;fp=sample-configuration%2FREADME;h=3c54219038b1708139aecaa6d27231430c95584c;hp=1d094ae144b2a945d9664e20d685ee4cde6eabb0;hb=ae776b1091bfdea4e2764ccb2652471ee5c9ce00;hpb=128e038085291f40482e39e9481d47942af7ceee

diff --git a/sample-configuration/README b/sample-configuration/README
index 1d094ae..3c54219 100644
--- a/sample-configuration/README
+++ b/sample-configuration/README
@@ -30,10 +30,10 @@ This allows for example easy management of gateway from inside this range,
 or remote management of entire network after ssh to gatway and then another
 ssh to this zone.
 
-We run HTTP proxy at port 3128 of LAN interface of internet gateway. This
-proxy is inside "qos-free-zone". Because of "qos-proxy-enable", 
+We used to run HTTP proxy at port 3128 of LAN interface of internet gateway. 
+This proxy was inside "qos-free-zone". With "qos-proxy-enable", 
 "qos-proxy-ip" (which is actually IP/number of bits of netmask) and 
-"qos-proxy-port" settings, this port is excluded from QoS-free zone.
+"qos-proxy-port" settings, this port was excluded from QoS-free zone.
 
 3) NAT