diff --git a/www.i2p2/pages/how_garlicrouting.html b/www.i2p2/pages/how_garlicrouting.html
index 21d21b21..54a18553 100644
--- a/www.i2p2/pages/how_garlicrouting.html
+++ b/www.i2p2/pages/how_garlicrouting.html
@@ -139,7 +139,7 @@ Each client message as delivered to the router through the
 <a href="i2cp.html">I2CP interface</a> becomes a single
 <a href="i2np.html#struct_GarlicClove">Garlic Clove</a>
 with its own
-<a href="tunnel_message_spec.html#delivery">Delilvery Instructions</a>,
+<a href="tunnel_message_spec.html#delivery">Delivery Instructions</a>,
 inside a
 <a href="i2np.html#msg_Garlic">Garlic Message</a>.
 Delivery Instructions may specify a Destination, Router, or Tunnel.
@@ -153,7 +153,7 @@ A
 <a href="i2np.html#msg_DeliveryStatus">Delivery Status Message</a>,
 with
 <a href="tunnel_message_spec.html#delivery">Delivery Instructions</a>
-specifying that it be sent back to the originating router as an acknowledgement.
+specifying that it be sent back to the originating router as an acknowledgment.
 This is similar to the "reply block" or "reply onion"
 described in the references.
 It is used for determining the success or failure of end to end message delivery.
@@ -166,7 +166,7 @@ A
 <a href="i2np.html#msg_DatabaseStore">Database Store Message</a>,
 containing a
 <a href="common_structures_spec#struct_LeaseSet">LeaseSet</a>
-for the originating Destnation, with
+for the originating Destination, with
 <a href="tunnel_message_spec.html#delivery">Delivery Instructions</a>
 specifying the far-end destination's router.
 By periodically bundling a LeaseSet, the router ensures that the far-end will be able