more minor tweaks, ok jmc

2 files changed, 26 insertions, 18 deletions

diff --git a/src/lib/libc/net/inet6_option_space.3 b/src/lib/libc/net/inet6_option_space.3
index 7c3b78033a..5beec487ac 100644
--- a/src/lib/libc/net/inet6_option_space.3
+++ b/src/lib/libc/net/inet6_option_space.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: inet6_option_space.3,v 1.17 2005/01/07 10:00:20 jmc Exp $
+.\"     $OpenBSD: inet6_option_space.3,v 1.18 2005/01/11 17:45:41 jaredy Exp $
 .\"     $KAME: inet6_option_space.3,v 1.11 2005/01/05 03:00:44 itojun Exp $
 .\"
 .\" Copyright (C) 2004 WIDE Project.
@@ -81,7 +81,7 @@ an option when it is stored as ancillary data, including the
 .Li cmsghdr
 structure at the beginning, and any necessary padding at the end.
 The
-.Li nbytes
+.Fa nbytes
 argument indicates the size of the structure defining the option,
 and must include any pad bytes at the beginning (the value
 .Li y
@@ -117,7 +117,7 @@ The
 .Fa bp
 argument points to a previously allocated area of memory which must be
 large enough to contain all the arguments that the application intends
-to add later via
+to add later via the
 .Fn inet6_option_append
 and
 .Fn inet6_option_alloc
@@ -181,7 +181,8 @@ which is then followed by the option data.
 The option types of
 .Li 0
 and
-.Li 1 are reserved for the
+.Li 1
+are reserved for the
 .Li Pad1
 and
 .Li PadN
@@ -300,9 +301,9 @@ options remain to be processed, the return value is
 and
 .Fa *tptrp
 is
-.Dv NULL
-and when an error occurs, the return value is
-.Li \-1
+.Dv NULL .
+When an error occurs, the return value is
+.Li \-1 ,
 but the
 .Fa *tptrp
 argument is not
@@ -317,11 +318,11 @@ argument points to a
 .Li cmsghdr
 where the
 .Li cmsg_level
-equals
+element equals
 .Dv IPPROTO_IPV6
-and
+and the
 .Li cmsg_type
-is either
+element is either
 .Dv IPV6_HOPOPTS
 or
 .Dv IPV6_DSTOPTS .
@@ -402,7 +403,7 @@ When
 or
 .Fn inet6_option_find
 detect an error they return
-.Li \-1
+.Li \-1 ,
 setting
 .Fa *tptrp
 to a non
@@ -410,6 +411,8 @@ to a non
 value.
 .\"
 .Sh SEE ALSO
+.Xr inet6 4 ,
+.Xr ip6 4
 .Rs
 .%A W. Stevens
 .%A M. Thomas
@@ -431,5 +434,5 @@ The functions are documented in
 (RFC 2292).
 .\"
 .Sh HISTORY
-The implementation first appeared in KAME advanced networking kit.
+This implementation first appeared in the KAME advanced networking kit.
 .\"
diff --git a/src/lib/libc/net/inet6_rthdr_space.3 b/src/lib/libc/net/inet6_rthdr_space.3
index 4474228be0..7c00c42e42 100644
--- a/src/lib/libc/net/inet6_rthdr_space.3
+++ b/src/lib/libc/net/inet6_rthdr_space.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: inet6_rthdr_space.3,v 1.16 2005/01/06 11:08:47 jmc Exp $
+.\"     $OpenBSD: inet6_rthdr_space.3,v 1.17 2005/01/11 17:45:41 jaredy Exp $
 .\"     $KAME: inet6_rthdr_space.3,v 1.11 2005/01/05 03:00:44 itojun Exp $
 .\"
 .\" Copyright (C) 2004 WIDE Project.
@@ -103,7 +103,9 @@ is supported,
 .Dv IPV6_RTHDR_TYPE_0 ,
 and it can hold from 1 to 23 segments.
 The return value includes the
-size of the cmsghdr structure that precedes the routing header, and
+size of the
+.Vt cmsghdr
+structure that precedes the routing header and
 any required padding.
 .Pp
 A return value of 0 indicates an error.
@@ -168,7 +170,7 @@ function specifies the strict or loose flag for the final hop of a
 routing header.
 The
 .Fa flags
-must be either
+argument must be either
 .Dv IPV6_RTHDR_LOOSE
 or
 .Dv IPV6_RTHDR_STRICT .
@@ -212,7 +214,7 @@ function returns a pointer to the IPv6 address specified by the
 argument from the routing header pointed to by
 .Fa cmsg .
 The index must be between 1 and the number returned by
-.Fn inet6_rthdr_segments
+.Fn inet6_rthdr_segments ,
 described above.
 An application must call
 .Fn inet6_rthdr_segments
@@ -254,7 +256,8 @@ The
 function returns 0 when an error occurs.
 .Pp
 The
-.Fn inet6_rthdr_add ,
+.Fn inet6_rthdr_add
+and
 .Fn inet6_rthdr_lasthop
 functions return 0 on success, and \-1 on error.
 .Pp
@@ -274,6 +277,8 @@ and
 functions return \-1 on error.
 .\"
 .Sh SEE ALSO
+.Xr inet6 4 ,
+.Xr ip6 4
 .Rs
 .%A W. Stevens
 .%A M. Thomas
@@ -290,7 +295,7 @@ functions return \-1 on error.
 .Re
 .\"
 .Sh HISTORY
-The implementation first appeared in KAME advanced networking kit.
+This implementation first appeared in the KAME advanced networking kit.
 .\"
 .Sh BUGS
 The