[src/trunk]: src/share/man/man4 Instead of .Ar use .Fa or .Vt as appropriate.

[uwe <uwe%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/6a3b0b544aff
branches:  trunk
changeset: 786931:6a3b0b544aff
user:      uwe <uwe%NetBSD.org@localhost>
date:      Wed May 22 18:41:08 2013 +0000

description:
Instead of .Ar use .Fa or .Vt as appropriate.

diffstat:

 share/man/man4/route.4 |  14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diffs (54 lines):

diff -r c294463a1484 -r 6a3b0b544aff share/man/man4/route.4
--- a/share/man/man4/route.4    Wed May 22 18:29:41 2013 +0000
+++ b/share/man/man4/route.4    Wed May 22 18:41:08 2013 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: route.4,v 1.20 2013/05/22 18:29:41 uwe Exp $
+..\"   $NetBSD: route.4,v 1.21 2013/05/22 18:41:08 uwe Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
 .\"    The Regents of the University of California.  All rights reserved.
@@ -140,7 +140,7 @@
 .Pp
 The kernel may reject certain messages, and will indicate this
 by filling in the
-.Ar rtm_errno
+.Fa rtm_errno
 field.
 The routing code returns
 .Er EEXIST
@@ -155,7 +155,7 @@
 to install a new route.
 In the current implementation, all routing processes run locally,
 and the values for
-.Ar rtm_errno
+.Fa rtm_errno
 are available through the normal
 .Em errno
 mechanism, even if the routing reply message is lost.
@@ -256,22 +256,22 @@
 The
 .Dv RTM_IFINFO
 message uses a
-.Ar if_msghdr
+.Vt if_msghdr
 header, the
 .Dv RTM_NEWADDR ,
 .Dv RTM_CHGADDR ,
 and
 .Dv RTM_DELADDR
 messages use a
-.Ar ifa_msghdr
+.Vt ifa_msghdr
 header,
 the
 .Dv RTM_IFANNOUNCE
 message uses a
-.Ar if_announcemsghdr
+.Vt if_announcemsghdr
 header,
 and all other messages use the
-.Ar rt_msghdr
+.Vt rt_msghdr
 header.
 .Pp
 The metrics structure is: