From 2c599883b81d233a5dce5ed4813da97d14559d9e Mon Sep 17 00:00:00 2001 From: Alejandro Leal Date: Wed, 17 Jun 2020 17:05:21 -0400 Subject: [PATCH] few updates to manual page and README.md --- README.md | 2 +- man/mtr-packet.8.in | 4 ++-- man/mtr.8.in | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 77b6f79..9db7b62 100644 --- 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 diff --git a/man/mtr-packet.8.in b/man/mtr-packet.8.in index 9c02470..090c3ad 100644 --- 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 db55012..e8c5404 100644 --- 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 -- 2.47.2