Some fixes; d@

diff --git a/share/man/man8/crash.8 b/share/man/man8/crash.8
index 28943c7..ee19452 100644 (file)
--- a/share/man/man8/crash.8
+++ b/share/man/man8/crash.8
@@ -1,4 +1,5 @@
-.\"    $OpenBSD: crash.8,v 1.3 2000/03/18 21:26:28 deraadt Exp $
+.\"    $OpenBSD: crash.8,v 1.4 2000/03/22 03:05:51 aaron Exp $
+.\"
 .\" Copyright (c) 1980, 1991 The Regents of the University of California.
 .\" All rights reserved.
 .\"
@@ -33,7 +34,7 @@
 .\"    from: @(#)crash.8       6.5 (Berkeley) 4/20/91
 .\"
 .Dd February 23, 2000
-.Dt crash 8
+.Dt CRASH 8
 .Os
 .Sh NAME
 .Nm crash
@@ -52,7 +53,7 @@ on the console and enters the kernel debugger,
 .Xr ddb 4 .
 If the debugger command
 .Ic boot dump
-is enterred, or if the debugger was not compiled into the kernel, or
+is entered, or if the debugger was not compiled into the kernel, or
 the debugger was disabled with
 .Xr sysctl 8 ,
 then the system dumps the contents of physical memory
@@ -140,15 +141,16 @@ That completes the list of panic types you are likely to see.
 When the system crashes it writes (or at least attempts to write)
 an image of memory, including the kernel image, onto the dump device.
 On reboot, the kernel image and memory image are separated and preserved in
+the directory
 .Pa /var/crash .
 .Pp
-To analyze the kernel and memory images preserved in
+To analyze the kernel and memory images preserved as
 .Pa bsd.0
 and 
 .Pa bsd.0.core ,
 you should run
 .Xr gdb 1 ,
-loading them in with the following commands:
+loading in the images with the following commands:
 .Pp
 .Bd -literal
        file /var/crash/bsd.0