diff --git a/LDP/howto/docbook/Adv-Routing-HOWTO.sgml b/LDP/howto/docbook/Adv-Routing-HOWTO.sgml
index d07b263a..e0d02448 100644
--- a/LDP/howto/docbook/Adv-Routing-HOWTO.sgml
+++ b/LDP/howto/docbook/Adv-Routing-HOWTO.sgml
@@ -1811,7 +1811,7 @@ only reschedule, delay or drop it.
 <Para>
 These can be used to shape traffic for an entire interface, without any
 subdivisions. It is vital that you understand this part of queueing before
-we go on the the classful qdisc-containing-qdiscs!
+we go onto the classful qdisc-containing-qdiscs!
 </Para>
 
 <Para>
@@ -2049,7 +2049,7 @@ and passes the queue without delay.
  The data arrives in TBF at a rate that's <Emphasis>smaller</Emphasis> than the
 token rate. Only a part of the tokens are deleted at output of each data packet
 that's sent out the queue, so the tokens accumulate, up to the bucket size.
-The unused tokens can then be used to send data a a speed that's exceeding the
+The unused tokens can then be used to send data at a speed that's exceeding the
 standard token rate, in case short data bursts occur.
 
 </Para>
@@ -4116,7 +4116,7 @@ need to be sent from A to B - eth1 might get 1, 3 and 5. eth2 would then do
 3, 4, 5, 6. But the possibility is very real that the kernel gets it like
 this: 2, 1, 4, 3, 6, 5. The problem is that this confuses TCP/IP. While not
 a problem for links carrying many different TCP/IP sessions, you won't be
-able to to a bundle multiple links and get to ftp a single file lots faster,
+able to bundle multiple links and get to ftp a single file lots faster,
 except when your receiving or sending OS is Linux, which is not easily
 shaken by some simple reordering.
 </Para>