Fix several typos.

Submitted by:	Erik Salander <erik@whistle.com>

1 files changed, 17 insertions, 17 deletions

diff --git a/sys/netinet/libalias/libalias.3 b/sys/netinet/libalias/libalias.3
index 0183670..f3f187d 100644
--- a/sys/netinet/libalias/libalias.3
+++ b/sys/netinet/libalias/libalias.3
@@ -155,8 +155,8 @@ PacketAliasRedirectAddr().
 If the PKT_ALIAS_RESET_ON_ADDR_CHANGE mode bit
 is set (the default mode of operation), then
 the internal aliasing link tables will be reset
-any time the aliasing address changes, as if
-PacketAliasReset() were called.  This is useful
+any time the aliasing address changes.  
+This is useful
 for interfaces such as ppp where the IP
 address may or may not change on successive
 dial-up attempts.
@@ -205,10 +205,10 @@ numbers unchanged from the actual local port
 number.  This can be done as long as the
 quintuple (proto, alias addr, alias port,
 remote addr, remote port) is unique.  If a
-conflict exists, an new aliasing port number is
+conflict exists, a new aliasing port number is
 chosen even if this mode bit is set.
 .It PKT_ALIAS_USE_SOCKETS.
-This bit should be set when the the packet
+This bit should be set when the packet
 aliasing host originates network traffic as
 well as forwards it.  When the packet aliasing
 host is waiting for a connection from an
@@ -245,7 +245,7 @@ of the packet aliasing engine will be cleared.
 This operating mode is useful for ppp links
 where the interface address can sometimes
 change or remain the same between dial-ups.
-If this mode bit is not set, it the link table
+If this mode bit is not set, the link table
 will never be reset in the event of an
 address change.
 .It PKT_ALIAS_PUNCH_FW.
@@ -254,7 +254,7 @@ ipfw based firewall for FTP/IRC DCC connections.
 The holes punched are bound by from/to IP address
 and port; it will not be possible to use a hole
 for another connection.  A hole is removed when
-the connection that use it die.  To cater for
+the connection that uses it dies.  To cater to
 unexpected death of a program using libalias (e.g
 kill -9), changing the state of the flag will
 clear the entire ipfw range allocated for holes.
@@ -312,7 +312,7 @@ engine occurred.
 The packet aliasing process was successful.
 .It PKT_ALIAS_IGNORED.
 The packet was ignored and not de-aliased.
-This can happen if the protocal is unrecognized,
+This can happen if the protocol is unrecognized,
 possibly an ICMP message type is not handled or
 if incoming packets for new connections are being
 ignored (see PKT_ALIAS_DENY_INCOMING in section
@@ -338,7 +338,7 @@ them with PacketAliasFragmentIn().
 An outgoing packet coming from the local network
 to a remote machine is aliased by this function.
 The IP packet is pointed to by
-.Em buffer r,
+.Em buffer ,
 and
 .Em maxpacketsize
 indicates the maximum packet size permissible
@@ -358,7 +358,7 @@ engine occurred.
 The packet aliasing process was successful.
 .It PKT_ALIAS_IGNORED.
 The packet was ignored and not de-aliased.
-This can happen if the protocal is unrecognized,
+This can happen if the protocol is unrecognized,
 or possibly an ICMP message type is not handled.
 .El
 .Sh 4. Port and Address Redirection
@@ -394,7 +394,7 @@ or
 .Em alias_addr
 is zero, this indicates that the packet aliasing
 address as established by PacketAliasSetAddress()
-is to be used.  Even if PacketAliasAddress() is
+is to be used.  Even if PacketAliasSetAddress() is
 called to change the address after PacketAliasRedirectPort()
 is called, a zero reference will track this change.
 
@@ -406,7 +406,7 @@ any remote address.  Likewise, if
 is zero, this indicates to redirect packets originating
 from any remote port number.  Almost always, the remote
 port specification will be zero, but non-zero remote
-addresses can be sometimes be useful for firewalling. 
+addresses can sometimes be useful for firewalling. 
 If two calls to PacketAliasRedirectPort() overlap in
 their address/port specifications, then the most recent
 call will have precedence.
@@ -447,16 +447,16 @@ or
 .Em alias_addr
 is zero, this indicates that the packet aliasing
 address as established by PacketAliasSetAddress()
-is to be used.  Even if PacketAliasAddress() is
+is to be used.  Even if PacketAliasSetAddress() is
 called to change the address after PacketAliasRedirectAddr()
 is called, a zero reference will track this change.
 
 If subsequent calls to PacketAliasRedirectAddr()
 use the same aliasing address, all new incoming
 traffic to this aliasing address will be redirected
-to the local address made in the last function call,
-but new traffic all of the local machines designated
-in the several function calls will be aliased to
+to the local address made in the last function call.
+New traffic generated by any of the local machines, designated
+in the several function calls, will be aliased to
 the same address.  Consider the following example:
 .Bd -literal -offset left
     PacketAliasRedirectAddr(inet_aton("192.168.0.2"),
@@ -589,7 +589,7 @@ access, or to restrict access to certain external machines.
 This function causes any
 .Em G Ns No eneral
 .Em R Ns No outing
-.Em E Ns No encapsulated
+.Em E Ns No ncapsulation
 .Pq Dv IPPROTO_GRE
 packets to be aliased using
 .Ar addr
@@ -861,7 +861,7 @@ All outgoing packets from the local network
 automatically create a dynamic link if
 they do not match an already existing fully
 specified link.  If an address mapping exists
-for the the outgoing packet, this determines
+for the outgoing packet, this determines
 the alias address to be used.  If no mapping
 exists, then a default address, usually the
 address of the packet aliasing host, is used.