>Number:         22035
>Category:       bin
>Synopsis:       ipnat(5) man page typos
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 02 12:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Juha Hyttinen
>Release:        -current (several ones, different dates)
>Organization:
HUT/LCE
>Environment:
scorpion% uname -a
NetBSD scorpion.tky.hut.fi 1.6Q NetBSD 1.6Q (SCORPION) #10: Wed Apr  9 10:50:38 EEST 2003  jthyttin@scorpion.tky.hut.fi:/cvs/obj/sys/arch/i386/compile/SCORPION i386
>Description:
ipnat(5) man page has the following typos:

	- TRANSLATION section
		- last line
			alloted -> allocated
	- TRNSPARENT PROXIES section
		- note the missing "A" in subject
	- EXAMPLES section
		- second last paragraph, second last line
			sides -> sites

Personally I also think this is a typo, but given the English experts
on @netbsd.org mailing lists, I'd rather keep this as a suggestion ;)

	- TRANSLATION section
		- line 3:
			successful -> successfully

>How-To-Repeat:
man 5 ipnat
	- search for "successful"
	- search for "alloted"
	- search for "TRNSPARENT"
	- search for "sides"
>Fix:
Below is a patch for fixing all of the typos (also my "suggestion").
I tested it with the following procedure (against freshly updated
/usr/src/dist/ipf/man/ipnat.5):

# cd /var/tmp
# diff -u /usr/src/dist/ipf/man/ipnat.5 ipnat.5 > ipnat.diff
# patch -p0 < /var/tmp/ipnat.diff
# cd /usr/src/usr.sbin/ipf/ipnat/
# make && make install


--- /usr/src/dist/ipf/man/ipnat.5       2003-03-22 16:35:43.000000000 +0200
+++ ipnat.5     2003-07-02 15:43:27.000000000 +0300
@@ -113,7 +113,7 @@
 .SH TRANSLATION
 .PP
 To the right of the "->" is the address and port specification which will be
-written into the packet providing it has already successful matched the
+written into the packet providing it has already successfully matched the
 prior constraints.  The case of redirections (\fBrdr\fP) is the simplest:
 the new destination address is that specified in the rule.  For \fBmap\fP
 rules, the destination address will be one for which the tuple combining
@@ -127,13 +127,13 @@
 how it searches for a new, free and unique tuple, in that it will used an
 algorithm to determine what the new source address should be, along with the
 range of available ports - the IP address is never changed and nor does the
-port number ever exceed its alloted range.
+port number ever exceed its allocated range.
 .SH KERNEL PROXIES
 .PP
 IP Filter comes with a few, simple, proxies built into the code that is loaded
 into the kernel to allow secondary channels to be opened without forcing the
 packets through a user program.
-.SH TRNSPARENT PROXIES
+.SH TRANSPARENT PROXIES
 .PP
 True transparent proxying should be performed using the redirect (\fBrdr\fP)
 rules directing ports to localhost (127.0.0.1) with the proxy program doing
@@ -228,7 +228,7 @@
 three-way handshake and limit their negotiated MSS value to the number
 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
+with broken sites that use a misconfigured firewall. Unfortunately such
 sites are not rare.
 .PP
 The value for the clamping clause is calculated as interface-MTU less

>Release-Note:
>Audit-Trail:
>Unformatted: