diff options
Diffstat (limited to 'src/lib/libc/net/inet6_rth_space.3')
-rw-r--r-- | src/lib/libc/net/inet6_rth_space.3 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/lib/libc/net/inet6_rth_space.3 b/src/lib/libc/net/inet6_rth_space.3 index 6b09e6fa88..fcd023481f 100644 --- a/src/lib/libc/net/inet6_rth_space.3 +++ b/src/lib/libc/net/inet6_rth_space.3 | |||
@@ -1,4 +1,4 @@ | |||
1 | .\" $OpenBSD: inet6_rth_space.3,v 1.5 2012/09/27 11:31:58 jmc Exp $ | 1 | .\" $OpenBSD: inet6_rth_space.3,v 1.6 2014/01/21 03:15:45 schwarze Exp $ |
2 | .\" $KAME: inet6_rth_space.3,v 1.7 2005/01/05 03:00:44 itojun Exp $ | 2 | .\" $KAME: inet6_rth_space.3,v 1.7 2005/01/05 03:00:44 itojun Exp $ |
3 | .\" | 3 | .\" |
4 | .\" Copyright (C) 2004 WIDE Project. | 4 | .\" Copyright (C) 2004 WIDE Project. |
@@ -28,7 +28,7 @@ | |||
28 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | 28 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
29 | .\" SUCH DAMAGE. | 29 | .\" SUCH DAMAGE. |
30 | .\" | 30 | .\" |
31 | .Dd $Mdocdate: September 27 2012 $ | 31 | .Dd $Mdocdate: January 21 2014 $ |
32 | .Dt INET6_RTH_SPACE 3 | 32 | .Dt INET6_RTH_SPACE 3 |
33 | .Os | 33 | .Os |
34 | .\" | 34 | .\" |
@@ -64,10 +64,10 @@ The RFC uses the word | |||
64 | .Dq segments | 64 | .Dq segments |
65 | to describe addresses and that is the term used here as well. | 65 | to describe addresses and that is the term used here as well. |
66 | All of the functions are defined in the header file | 66 | All of the functions are defined in the header file |
67 | .Aq Pa netinet/in.h . | 67 | .In netinet/in.h . |
68 | The functions described in this manual page all operate | 68 | The functions described in this manual page all operate |
69 | on routing header structures which are defined in | 69 | on routing header structures which are defined in |
70 | .Aq Pa netinet/ip6.h | 70 | .In netinet/ip6.h |
71 | but which should not need to be modified outside the use of this API. | 71 | but which should not need to be modified outside the use of this API. |
72 | The size and shape of the route header structures may change, so using | 72 | The size and shape of the route header structures may change, so using |
73 | the APIs is a more portable, long term, solution. | 73 | the APIs is a more portable, long term, solution. |