diff --git a/LDP/howto/linuxdoc/Multicast-HOWTO.sgml b/LDP/howto/linuxdoc/Multicast-HOWTO.sgml
index 595ce8ac..7d62dd92 100644
--- a/LDP/howto/linuxdoc/Multicast-HOWTO.sgml
+++ b/LDP/howto/linuxdoc/Multicast-HOWTO.sgml
@@ -380,7 +380,7 @@ when configuring your kernel. If you also want your Linux box to act as a
 multicast router (mrouter) you also need to enable multicast routing in the 
 kernel by selecting "<em>IP: forwarding/gatewaying</em>", "<em/IP: multicast routing/" 
 and "<em/IP: tunneling/", the latter because new versions of <tt/mrouted/ 
-relay on IP tunneling to send multicast datagrams encapsulated into unicast 
+rely on IP tunneling to send multicast datagrams encapsulated into unicast 
 ones. This is necessary when establishing tunnels 
 between multicast hosts separated by unicast-only networks and routers.
 (The <tt/mrouted/ is a daemon that implements the multicast routing algorithm
@@ -1442,7 +1442,7 @@ for more information.
 I feel grateful to. So, I'm afraid this is going to be a large section... It
 is, in any case, the most important one of this paper (for me, at least...).
 
-First, I want to thank Elena Apolinario Fernández de Sousa (yes, Elena is
+First, I want to thank Elena Apolinario Fernández de Sousa (yes, Elena is
 the first name; the REST is THE surname ;-) ). I tried to reflect
 in this Howto all the knowledge I collected while working with her in connecting
 our Department to the MBone and debugging problems with locally generated
@@ -1470,7 +1470,7 @@ entirely from his books (well, the latter also from his programs...).
 Thanks for all, Pablo.
 
 In my first course at the University that "primary source of documentation"
-moved to Pepe Mañas. He was teaching then Computer Programming there, and
+moved to Pepe Mañas. He was teaching then Computer Programming there, and
 soon I became addict to his bookshelf. He lent me his books lots of times
 without asking for a minimum sign that could assure that I was going
 to return them back to him, not even my name! My first approach to TCP/IP
@@ -1481,13 +1481,13 @@ That book influenced me a lot, and TCP/IP has become one of my primary
 fields of interest since that summer.
 
 If there are two persons I must thank most, these are (in alphabetic
-order ;-) ), José Manuel and Paco Moya. Nobody I asked more things more
+order ;-) ), José Manuel and Paco Moya. Nobody I asked more things more
 times (C, C++, Linux, security, Web, OSs, signals &amp; systems, 
 electronics, ... anything!) and, despite my persistence, I always got throughly 
 and friendly responses and help. If I'm using GNU/Linux now, this is, again,
 thanks to them. I feel particularly lucky with friends like them. THANKS.
 
-Iñigo Mascaraque also helped (from him I got my first System Administration
+Iñigo Mascaraque also helped (from him I got my first System Administration
 book) and encouraged me in my beginnings, but never stopped reminding me
 that, although this was a fascinating world and an important part of my
 career, I should not forget the other, less-interesting, parts. (I don't
@@ -1497,9 +1497,9 @@ As I am on the topic, I'd like to thank my parents, too. They always
 tried to make the best opportunities available for me. Many thanks for
 all.
 
-I also feel grateful to Joaquín Seoane, the first who trusted me enough
+I also feel grateful to Joaquín Seoane, the first who trusted me enough
 to give me a root password in the time I was learning system administration
-by myself, and Santiago Pavón, the one who gave me my first opportunity
+by myself, and Santiago Pavón, the one who gave me my first opportunity
 here at DIT.
 
 W. Richard Stevens' books have been a real revelation for me (it's a pity