repairs; better English, formatting, etc.

1 files changed, 9 insertions, 9 deletions

diff --git a/src/lib/libc/net/ns.3 b/src/lib/libc/net/ns.3
index ee49237a24..24e69c8388 100644
--- a/src/lib/libc/net/ns.3
+++ b/src/lib/libc/net/ns.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: ns.3,v 1.4 1999/05/23 14:11:02 aaron Exp $
+.\"     $OpenBSD: ns.3,v 1.5 1999/07/05 04:41:00 aaron Exp $
 .\"
 .\" Copyright (c) 1986, 1991, 1993
 .\"     The Regents of the University of California.  All rights reserved.
@@ -43,7 +43,7 @@ address conversion routines
 .Sh SYNOPSIS
 .Fd #include <sys/types.h>
 .Fd #include <netns/ns.h>
-.Ft struct ns_addr 
+.Ft struct ns_addr
 .Fn ns_addr "char *cp"
 .Ft char *
 .Fn ns_ntoa "struct ns_addr ns"
@@ -67,11 +67,11 @@ notation in common use in the Xerox Development Environment:
 .Ed
 .Pp
 Trailing zero fields are suppressed, and each number is printed in hexadecimal,
-in a format suitable for input to 
+in a format suitable for input to
 .Fn ns_addr .
 Any fields lacking super-decimal digits will have a
 trailing
-.Ql H
+.Sq H
 appended.
 .Pp
 Unfortunately, no universal standard exists for representing
@@ -83,11 +83,11 @@ be compatible with most formats in common use.
 It will first separate an address into 1 to 3 fields using a single delimiter
 chosen from
 period
-.Ql \&. ,
+.Pq Ql \&. ,
 colon
-.Ql \&:
+.Pq Ql \&: ,
 or pound-sign
-.Ql \&# .
+.Ql # .
 Each field is then examined for byte separators (colon or period).
 If there are byte separators, each subfield separated is taken to be
 a small hexadecimal number, and the entirety is taken as a network-byte-ordered
@@ -101,7 +101,7 @@ as hexadecimal if there is a leading
 .Ql 0x
 (as in C),
 a trailing
-.Ql H
+.Sq H
 (as in Mesa), or there are any super-decimal digits present.
 It is interpreted as octal is there is a leading
 .Ql 0
@@ -118,7 +118,7 @@ The
 .Fn ns_addr
 and
 .Fn ns_toa
-functions appeared in 
+functions appeared in
 .Bx 4.3 .
 .Sh BUGS
 The string returned by