1 files changed, 8 insertions, 8 deletions
diff --git a/src/lib/libc/net/inet6_option_space.3 b/src/lib/libc/net/inet6_option_space.3
index 8757641eac..4e5dc22711 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.12 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: inet6_option_space.3,v 1.13 2003/08/08 09:26:02 jmc Exp $
 .\"     $KAME: inet6_option_space.3,v 1.7 2000/05/17 14:32:13 itojun Exp $
 .\"
 .\" Copyright (c) 1983, 1987, 1991, 1993
@@ -61,7 +61,7 @@
 Building and parsing the Hop-by-Hop and Destination options is
 complicated due to alignment constraints, padding and
 ancillary data manipulation.
-RFC2292 defines a set of functions to help the application.
+RFC 2292 defines a set of functions to help the application.
 The function prototypes for
 these functions are all in the
 .Aq Pa netinet/in.h
@@ -99,7 +99,7 @@ is the number of options to be stored in the object.
 This is of little consequence, since it is assumed that most
 Hop-by-Hop option headers and Destination option headers carry only
 one option
-.Pq appendix B of [RFC-2460] .
+.Pq appendix B of [RFC 2460] .
 .\"
 .Ss inet6_option_init
 .Fn inet6_option_init
@@ -386,7 +386,7 @@ is not
 .Dv NULL .
 .\"
 .Sh EXAMPLES
-RFC2292 gives comprehensive examples in chapter 6.
+RFC 2292 gives comprehensive examples in chapter 6.
 .\"
 .Sh DIAGNOSTICS
 .Fn inet6_option_init
@@ -420,14 +420,14 @@ value.
 .%A W. Stevens
 .%A M. Thomas
 .%T "Advanced Sockets API for IPv6"
-.%N RFC2292
+.%N RFC 2292
 .%D February 1998
 .Re
 .Rs
 .%A S. Deering
 .%A R. Hinden
 .%T "Internet Protocol, Version 6 (IPv6) Specification"
-.%N RFC2460
+.%N RFC 2460
 .%D December 1998
 .Re
 .\"
@@ -435,10 +435,10 @@ value.
 The functions
 are documented in
 .Dq Advanced Sockets API for IPv6
-.Pq RFC2292 .
+.Pq RFC 2292 .
 .\"
 .Sh HISTORY
 The implementation first appeared in KAME advanced networking kit.
 .\"
 .Sh BUGS
-The text was shamelessly copied from RFC2292.
+The text was shamelessly copied from RFC 2292.

diff --git a/src/lib/libc/net/inet6_option_space.3 b/src/lib/libc/net/inet6_option_space.3 index 8757641eac..4e5dc22711 100644 --- a/src/lib/libc/net/inet6_option_space.3 +++ b/src/lib/libc/net/inet6_option_space.3
@@ -1,4 +1,4 @@
1	.\" $OpenBSD: inet6_option_space.3,v 1.12 2003/06/02 20:18:35 millert Exp $	1	.\" $OpenBSD: inet6_option_space.3,v 1.13 2003/08/08 09:26:02 jmc Exp $
2	.\" $KAME: inet6_option_space.3,v 1.7 2000/05/17 14:32:13 itojun Exp $	2	.\" $KAME: inet6_option_space.3,v 1.7 2000/05/17 14:32:13 itojun Exp $
3	.\"	3	.\"
4	.\" Copyright (c) 1983, 1987, 1991, 1993	4	.\" Copyright (c) 1983, 1987, 1991, 1993
@@ -61,7 +61,7 @@
61	Building and parsing the Hop-by-Hop and Destination options is	61	Building and parsing the Hop-by-Hop and Destination options is
62	complicated due to alignment constraints, padding and	62	complicated due to alignment constraints, padding and
63	ancillary data manipulation.	63	ancillary data manipulation.
64	RFC2292 defines a set of functions to help the application.	64	RFC 2292 defines a set of functions to help the application.
65	The function prototypes for	65	The function prototypes for
66	these functions are all in the	66	these functions are all in the
67	.Aq Pa netinet/in.h	67	.Aq Pa netinet/in.h
@@ -99,7 +99,7 @@ is the number of options to be stored in the object.
99	This is of little consequence, since it is assumed that most	99	This is of little consequence, since it is assumed that most
100	Hop-by-Hop option headers and Destination option headers carry only	100	Hop-by-Hop option headers and Destination option headers carry only
101	one option	101	one option
102	.Pq appendix B of [RFC-2460] .	102	.Pq appendix B of [RFC 2460] .
103	.\"	103	.\"
104	.Ss inet6_option_init	104	.Ss inet6_option_init
105	.Fn inet6_option_init	105	.Fn inet6_option_init
@@ -386,7 +386,7 @@ is not
386	.Dv NULL .	386	.Dv NULL .
387	.\"	387	.\"
388	.Sh EXAMPLES	388	.Sh EXAMPLES
389	RFC2292 gives comprehensive examples in chapter 6.	389	RFC 2292 gives comprehensive examples in chapter 6.
390	.\"	390	.\"
391	.Sh DIAGNOSTICS	391	.Sh DIAGNOSTICS
392	.Fn inet6_option_init	392	.Fn inet6_option_init
@@ -420,14 +420,14 @@ value.
420	.%A W. Stevens	420	.%A W. Stevens
421	.%A M. Thomas	421	.%A M. Thomas
422	.%T "Advanced Sockets API for IPv6"	422	.%T "Advanced Sockets API for IPv6"
423	.%N RFC2292	423	.%N RFC 2292
424	.%D February 1998	424	.%D February 1998
425	.Re	425	.Re
426	.Rs	426	.Rs
427	.%A S. Deering	427	.%A S. Deering
428	.%A R. Hinden	428	.%A R. Hinden
429	.%T "Internet Protocol, Version 6 (IPv6) Specification"	429	.%T "Internet Protocol, Version 6 (IPv6) Specification"
430	.%N RFC2460	430	.%N RFC 2460
431	.%D December 1998	431	.%D December 1998
432	.Re	432	.Re
433	.\"	433	.\"
@@ -435,10 +435,10 @@ value.
435	The functions	435	The functions
436	are documented in	436	are documented in
437	.Dq Advanced Sockets API for IPv6	437	.Dq Advanced Sockets API for IPv6
438	.Pq RFC2292 .	438	.Pq RFC 2292 .
439	.\"	439	.\"
440	.Sh HISTORY	440	.Sh HISTORY
441	The implementation first appeared in KAME advanced networking kit.	441	The implementation first appeared in KAME advanced networking kit.
442	.\"	442	.\"
443	.Sh BUGS	443	.Sh BUGS
444	The text was shamelessly copied from RFC2292.	444	The text was shamelessly copied from RFC 2292.