capitalize the acronym ID

4 files changed, 16 insertions, 16 deletions

diff --git a/share/man/man4/options.4 b/share/man/man4/options.4
index 4342ef92e9b..8926f90b3a9 100644
--- a/share/man/man4/options.4
+++ b/share/man/man4/options.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: options.4,v 1.32 1999/05/25 02:24:51 provos Exp $
+.\"	$OpenBSD: options.4,v 1.33 1999/06/05 04:16:06 aaron Exp $
 .\"	$NetBSD: options.4,v 1.21 1997/06/25 03:13:00 thorpej Exp $
 .\"
 .\" Copyright (c) 1998 Theo de Raadt 
@@ -131,7 +131,7 @@ available on the alpha architecture.
 See
 .Xr compat_osf1 8 .
 .It Cd option COMPAT_NOMID
-Enable compatibility with a.out executables that lack a machine id.
+Enable compatibility with a.out executables that lack a machine ID.
 On the i386, this includes NetBSD 0.8's ZMAGIC format, 386BSD and BSDI's
 QMAGIC, NMAGIC, and OMAGIC a.out formats.  On the hp300 and other m68k
 architectures this permits certain old
@@ -337,7 +337,7 @@ files in the procfs namespace.  See
 .Xr mount_procfs 8
 for details.
 .It Cd option UMAPFS
-Includes a loopback file system in which user and group ids may be
+Includes a loopback file system in which user and group IDs may be
 remapped -- this can be useful when mounting alien file systems with
 different uids and gids than the local system (eg, remote NFS).  See
 .Xr mount_umap 8
@@ -442,7 +442,7 @@ for details on the implications of this.  The kernel secure level may
 be manipulated by the superuser by altering the
 .Em kern.securelevel
 sysctl variable. (It should be noted that the secure level may only be
-lowered by a call from process id 1, i.e.
+lowered by a call from process ID 1, i.e.,
 .Em init . )
 See also
 .Xr sysctl 8
diff --git a/share/man/man4/raid.4 b/share/man/man4/raid.4
index 4a3125bb959..07a0db7f10c 100644
--- a/share/man/man4/raid.4
+++ b/share/man/man4/raid.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: raid.4,v 1.3 1999/05/16 19:56:35 alex Exp $
+.\"	$OpenBSD: raid.4,v 1.4 1999/06/05 04:16:07 aaron Exp $
 .\"
 .\"
 .\" Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -140,7 +140,7 @@ or a
 .Xr newfs 8
 filesystem integrity and parity integrity can be ensured.  It bears
 repeating again that parity recomputation is 
-.Ar required
+.Em required
 before any filesystems are created or used on the RAID device.  If the
 parity is not correct, then missing data cannot be correctly recovered.
 .Pp
@@ -149,12 +149,12 @@ device can be constructed out of a number of RAID 5 devices (which, in turn,
 may be constructed out of the physical disks, or of other RAID devices).
 .Pp
 At the time of this writing, it is 
-.Ar imperative
+.Em imperative
 that drives be 
 .Sq nailed down
 at their respective addresses (i.e. not left free-floating, where a
 drive with SCSI ID of 4 can end up as /dev/sd0c).  Consider a system 
-with three SCSI drives at SCSI ID's 4, 5, and 6, and which map to 
+with three SCSI drives at SCSI IDs 4, 5, and 6, and which map to 
 components /dev/sd0e, /dev/sd1e, and /dev/sd2e.  If the drive with
 SCSI ID 5 fails,
 and the system reboots, the old /dev/sd2e will show up as /dev/sd1e.
@@ -201,7 +201,7 @@ device is found in
 .Xr raidctl 8 .
 It is highly recommended that the steps to reconstruct, copyback, and
 re-compute parity are well understood by the system administrator(s)
-.Ar before
+.Em before
 a component failure.  Doing the wrong thing when a component fails may
 result in data loss.
 .Pp
@@ -212,11 +212,11 @@ components of a RAID 4 or 5 system, or the loss of a single component
 of a RAID 0 system, will result in the entire filesystems on that RAID
 device being lost.
 RAID is 
-.Ar NOT
+.Em not
 a substitute for good backup practices.
 .Pp
 Recomputation of parity 
-.Ar MUST
+.Em must
 be performed whenever there is a chance that it may have been
 compromised.  This includes after system crashes, or before a RAID
 device has been used for the first time.  Failure to keep parity
diff --git a/share/man/man7/mdoc.samples.7 b/share/man/man7/mdoc.samples.7
index 32aaa5f6457..31d2c2e981f 100644
--- a/share/man/man7/mdoc.samples.7
+++ b/share/man/man7/mdoc.samples.7
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mdoc.samples.7,v 1.13 1999/05/24 18:42:25 aaron Exp $
+.\"	$OpenBSD: mdoc.samples.7,v 1.14 1999/06/05 04:16:07 aaron Exp $
 .\"	$NetBSD: mdoc.samples.7,v 1.5 1996/04/03 20:17:34 jtc Exp $
 .\"
 .\" Copyright (c) 1990, 1993
@@ -2485,7 +2485,7 @@ by the process to pages not loaded in core.
 .It UID
 numerical user-id of process owner
 .It PPID
-numerical id of parent of process process priority
+numerical ID of parent of process process priority
 (non-positive when in non-interruptible wait)
 .El
 .Pp
@@ -2502,7 +2502,7 @@ The raw text:
 \&.It UID
 \&numerical user-id of process owner
 \&.It PPID
-\&numerical id of parent of process process priority
+\&numerical ID of parent of process process priority
 \&(non-positive when in non-interruptible wait)
 \&.El
 .Ed
diff --git a/share/man/man8/man8.hp300/crash.8 b/share/man/man8/man8.hp300/crash.8
index 177e25c8f6a..d72ec57e986 100644
--- a/share/man/man8/man8.hp300/crash.8
+++ b/share/man/man8/man8.hp300/crash.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: crash.8,v 1.2 1997/07/27 08:23:08 downsj Exp $
+.\"	$OpenBSD: crash.8,v 1.3 1999/06/05 04:16:07 aaron Exp $
 .\"
 .\" Copyright (c) 1990, 1991 Regents of the University of California.
 .\" All rights reserved.
@@ -146,7 +146,7 @@ in the low 16.
 ``v'' (hex) is the virtual address which caused the fault.
 Additionally, the kernel will dump about a screenful of semi-useful
 information.
-``pid'' (decimal) is the process id of the process running at the
+``pid'' (decimal) is the process ID of the process running at the
 time of the exception.
 Note that if we panic in an interrupt routine,
 this process may not be related to the panic.