summaryrefslogtreecommitdiff
path: root/share/man/man8
diff options
context:
space:
mode:
authorTheo de Raadt <deraadt@cvs.openbsd.org>1998-09-01 16:38:26 +0000
committerTheo de Raadt <deraadt@cvs.openbsd.org>1998-09-01 16:38:26 +0000
commit1d8b37c69ca15e065c00671f8457b6df577db257 (patch)
tree058988774dd325531ec346aee241ce7435220916 /share/man/man8
parentb71308c90de1005a44413da2491439a019e721e6 (diff)
more man page fixes; aaron@ug.cs.dal.ca
Diffstat (limited to 'share/man/man8')
-rw-r--r--share/man/man8/man8.vax/crash.84
-rw-r--r--share/man/man8/update.84
2 files changed, 4 insertions, 4 deletions
diff --git a/share/man/man8/man8.vax/crash.8 b/share/man/man8/man8.vax/crash.8
index 76e84fe8044..0e20bddfce5 100644
--- a/share/man/man8/man8.vax/crash.8
+++ b/share/man/man8/man8.vax/crash.8
@@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" from: @(#)crash.8 6.5 (Berkeley) 4/20/91
-.\" $Id: crash.8,v 1.1 1995/10/18 08:44:41 deraadt Exp $
+.\" $Id: crash.8,v 1.2 1998/09/01 16:38:23 deraadt Exp $
.\"
.TH CRASH 8 "April 20, 1991"
.UC 4
@@ -152,7 +152,7 @@ Most of the internal processor registers are saved at the time of the fault
and are printed on the console.
For most processors, there is one line that summarizes the type of machine
check.
-Often, the nature of the problem is apparent from this messaage
+Often, the nature of the problem is apparent from this message
and/or the contents of key registers.
The VAX Hardware Handbook should be consulted,
and, if necessary, your friendly field service people should be informed
diff --git a/share/man/man8/update.8 b/share/man/man8/update.8
index 691e9e272af..8d55a63fd5c 100644
--- a/share/man/man8/update.8
+++ b/share/man/man8/update.8
@@ -27,7 +27,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $OpenBSD: update.8,v 1.5 1998/06/29 05:56:26 angelos Exp $
+.\" $OpenBSD: update.8,v 1.6 1998/09/01 16:38:22 deraadt Exp $
.\"
.Dd June 8, 1996
.Dt UPDATE 8
@@ -57,7 +57,7 @@ process will do this in a staggered manner.
.Sh BUGS
It is possible on some systems, that a
.Xr sync
-occuring simultaneously with a crash may cause
+occurring simultaneously with a crash may cause
file system damage. See
.Xr fsck 8 .
.Sh HISTORY