diff --git a/Shorewall-docs2/traffic_shaping.xml b/Shorewall-docs2/traffic_shaping.xml
index aa4dbca41..b7ad2017b 100644
--- a/Shorewall-docs2/traffic_shaping.xml
+++ b/Shorewall-docs2/traffic_shaping.xml
@@ -21,7 +21,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>2005-10-15</pubdate>
+    <pubdate>2005-11-21</pubdate>
 
     <copyright>
       <year>2001-2004</year>
@@ -99,7 +99,12 @@
     the packets were already received by your network card before you can
     decide what to do with them. So the only choice would be to drop them
     which normally makes no sense (since you received the packet already, it
-    went through the possible bottleneck (the incoming connection). The next
+    went through the possible bottleneck (the incoming connection); dropping
+    packets <emphasis>does</emphasis> have an advantage when you are connected
+    to the internet using a Cable Modem or DSL because it can prevent large
+    queues of download traffic from forming at your ISP and thus can improve
+    response time (see the definition of the IN-BANDWIDTH column of the
+    <filename>/etc/shorewall/tcdevices</filename> file below). The next
     possible bottleneck might come if the packet leaves on another interface,
     so this will be the place where queuing might occur. So, defining queues
     for incoming packages is not very useful, you just want to have it
@@ -714,4 +719,4 @@ ppp0            4       90kbit          200kbit         3           default</pro
       </orderedlist>
     </section>
   </section>
-</article>
+</article>
\ No newline at end of file