some improvement (spelling, grammar); ok angelos@

1 files changed, 14 insertions, 14 deletions

diff --git a/share/man/man4/ipcomp.4 b/share/man/man4/ipcomp.4
index dc7fddcb51b..32633ef0147 100644
--- a/share/man/man4/ipcomp.4
+++ b/share/man/man4/ipcomp.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipcomp.4,v 1.2 2001/07/05 09:04:03 angelos Exp $
+.\" $OpenBSD: ipcomp.4,v 1.3 2001/07/06 06:01:08 jasoni Exp $
 .\"
 .\" Copyright (c) 2001 Jean-Jacques Bernard-Gundol <jj@wabbitt.org>
 .\" All rights reserved.
@@ -59,7 +59,7 @@ protocol (see
 .Xr ipsec 4  
 for more information about IPsec).
 Encrypting information is increasing its entropy to a point where
-compression to a lower layer become completely useless (i.e PPP
+compression to a lower layer becomes completely useless (i.e PPP
 Compression Control Protocol).
 IPcomp is applied at the network layer before other encryption
 operations are applied (except encryption protocols applied at a
@@ -68,10 +68,10 @@ higher layer such as
 or
 .Xr ssl 8 ).
 .Pp
-Just like for the othre IPsec protocols, IPComp needs some parameters
+Just like for the other IPsec protocols, IPComp needs some parameters
 for each connection, specifying how the compression should be done
 between the entities. 
-The parameters are collected are collected in a structure called an
+The parameters are collected in a structure called an
 IPComp Association or IPCA.
 The parameters stored in an IPCA are the destination address and the
 Compression Parameter Index (CPI).
@@ -82,8 +82,8 @@ Currently, IPCA can be created using the
 tool.
 Using 
 .Xr ipsecadm 8
-it is also possible to create IPComp flows and bundled
-SA/IPCA.
+it is also possible to create IPComp flows and SA/IPCA
+bundles.
 Such a bundle is used to create a combination of IPsec and IPComp
 flows (thus enabling compression in an IPsec protocol).
 .Pp
@@ -95,21 +95,21 @@ compressed since they are modified by the router along the way to the
 destination.
 These extension headers are hop-by-hop, routing, and fragmentation.
 .Pp
-When doing compression, it is possible that compressed data is smaller
-in size than non compressed one.
+When doing compression, it is possible that the uncompressed data is 
+smaller in size than the compressed data.
 To avoid this behaviour, a non expansion policy is used in IPComp.
 If the data payload is smaller than a given threshold, it will not be
 compressed.
 No IPComp header will be inserted.
 .Pp
-Just like for IPsec, the implementation is using the virtual interface
-.Nm enc0
+Just like for IPsec, this implementation uses the virtual interface
+.Nm enc0 ,
 which can be used in packet filters to specify packets that are
 allowed to be processed by IPComp.
-But since IPsec and IPComp are both using this interface, special care
-must be taken when using a bundle SA/IPCA.
+Since IPsec and IPComp are both using this interface, special care
+must be taken when using a SA/IPCA bundle.
 .Pp
-IPComp is using the same policy framework as IPsec.
+IPComp uses the same policy framework as IPsec.
 However unlike IPsec, only one policy is available for IPComp:
 .Bl -tag -width IPSEC_LEVEL_USE 
 .It IPSEC_LEVEL_USE
@@ -139,7 +139,7 @@ The
 protocol first appeared in
 .Ox 3.0 .
 .Sh AUTHOR
-The support for the 
+Support for the 
 .Nm 
 protocol was written by Jean-Jacques
 Bernard-Gundol <jj@wabbitt.org>.