[src/trunk]: src/dist/ipf/man Spelling fixes and grammar improvements.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/cee86bf634a1
branches:  trunk
changeset: 525648:cee86bf634a1
user:      wiz <wiz%NetBSD.org@localhost>
date:      Sun Apr 14 14:35:05 2002 +0000

description:
Spelling fixes and grammar improvements.

diffstat:

 dist/ipf/man/ipnat.5 |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (26 lines):

diff -r 9f42708f8bf8 -r cee86bf634a1 dist/ipf/man/ipnat.5
--- a/dist/ipf/man/ipnat.5      Sun Apr 14 14:32:19 2002 +0000
+++ b/dist/ipf/man/ipnat.5      Sun Apr 14 14:35:05 2002 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: ipnat.5,v 1.5 2002/04/14 07:53:46 martin Exp $
+.\"    $NetBSD: ipnat.5,v 1.6 2002/04/14 14:35:05 wiz Exp $
 .\"
 .TH IPNAT 5
 .SH NAME
@@ -210,13 +210,13 @@
 .PP
 The mssclamp clause tells the NAT processor to scan for TCP packets in the
 three-way handshake and limit their negotiated MSS value to the number
-given in the rule. This is usefull to make hosts behind a connection with
+given in the rule. This is useful to make hosts behind a connection with
 low MTU (like PPPoE or tunnels) communicate without any outside proxies
 with broken sides that use a misconfigured firewall. Unfortunately such
 sites are not rare.
 .PP
-The value for the clamping clause is calculated as interface-mtu less
-40 bytes (size of IP header plus maximum IP options size), so for
+The value for the clamping clause is calculated as interface-MTU less
+40 bytes (size of IP header plus maximal IP options size), so for a
 PPPoE interface it is 1492 - 40 = 1452. Some sites seem to require clamping
 to even smaller values, but there is no rationale for this behaviour.
 .SH FILES