few updates to manual page and README.md

diff --git a/README.md b/README.md
index 77b6f79bb9e9679e2dc1c9ac8d28cd2bc2306450..9db7b6245a3981e2ebc3b6e51ca3e194534809f2 100644 (file)
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ If you're building from the git repository, you'll need to run:
 
        ./bootstrap.sh && ./configure && make
 
-When it looks as if the compilation was succesful, you can
+When it looks as if the compilation was successful, you can
 test mtr with
 
        sudo ./mtr <host>

diff --git a/man/mtr-packet.8.in b/man/mtr-packet.8.in
index 9c024709f77a77d6ac695169fe245f2b4f8a0f29..090c3adb166410f325a43bd2fa4dc69a8e7ae4ea 100644 (file)
--- a/man/mtr-packet.8.in
+++ b/man/mtr-packet.8.in
@@ -121,7 +121,7 @@ probes.
 .I IP-ADDRESS
 .HP 14
 .IP
-The local Internet Procol version 4 address to use when sending probes.
+The local Internet Protocol version 4 address to use when sending probes.
 .HP 7
 .IP
 .B local-ip-6
@@ -407,7 +407,7 @@ value, are used.
 \&...
 .RE 0
 .LP
-Each interemediate host would respond with a
+Each intermediate host would respond with a
 .B ttl-expired
 message, and the destination host would respond with a
 .BR reply :

diff --git a/man/mtr.8.in b/man/mtr.8.in
index db550124c49f809e9f1ef057169b6102d799b432..e8c54047e082549891fe893b483686b09cf76666 100644 (file)
--- a/man/mtr.8.in
+++ b/man/mtr.8.in
@@ -138,7 +138,7 @@ A sudden increase in packet loss or response time is often an indication
 of a bad (or simply overloaded) link. 
 .PP
 The results are usually reported as round-trip-response times in milliseconds
-and the percentage of packetloss. 
+and the percentage of packet loss. 
 .SH OPTIONS
 .TP
 .B \-h\fR, \fB\-\-help