diff options
author | Alex Feldman <alex@cvs.openbsd.org> | 1999-09-23 04:12:13 +0000 |
---|---|---|
committer | Alex Feldman <alex@cvs.openbsd.org> | 1999-09-23 04:12:13 +0000 |
commit | ce5efa4c99adb41d3b8e4e0966f38cca93401ae9 (patch) | |
tree | 2fcfc24c82be6f1539919cceaabc8b1cfe145e99 /share/man/man4/man4.vax | |
parent | 611e3fde18fdf3eb5935c4d652c97a088b5781b2 (diff) |
Typo fixes.
Diffstat (limited to 'share/man/man4/man4.vax')
-rw-r--r-- | share/man/man4/man4.vax/dmv.4 | 4 | ||||
-rw-r--r-- | share/man/man4/man4.vax/ex.4 | 4 | ||||
-rw-r--r-- | share/man/man4/man4.vax/uda.4 | 6 |
3 files changed, 7 insertions, 7 deletions
diff --git a/share/man/man4/man4.vax/dmv.4 b/share/man/man4/man4.vax/dmv.4 index a4368e4423d..e1f1fe3beea 100644 --- a/share/man/man4/man4.vax/dmv.4 +++ b/share/man/man4/man4.vax/dmv.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: dmv.4,v 1.4 1999/06/05 13:18:37 aaron Exp $ +.\" $OpenBSD: dmv.4,v 1.5 1999/09/23 04:12:06 alex Exp $ .\" $NetBSD: dmv.4,v 1.3 1996/03/03 17:13:25 thorpej Exp $ .\" .\" Copyright (c) 1988, 1991 Regents of the University of California. @@ -110,7 +110,7 @@ An input packet was received which contained a type of address unknown to the driver. .Pp .It "dmvxint: dmv%d unallocated packet 0x%x." -A protocol error has occured with the board. +A protocol error has occurred with the board. .Pp .It "dmvoutput, dmv%d can't handle af%d." A packet for an unsupported address family has been sent. diff --git a/share/man/man4/man4.vax/ex.4 b/share/man/man4/man4.vax/ex.4 index 629ae2cace3..872b6c22bf9 100644 --- a/share/man/man4/man4.vax/ex.4 +++ b/share/man/man4/man4.vax/ex.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: ex.4,v 1.4 1999/06/05 13:18:38 aaron Exp $ +.\" $OpenBSD: ex.4,v 1.5 1999/09/23 04:12:06 alex Exp $ .\" $NetBSD: ex.4,v 1.3 1996/03/03 17:13:33 thorpej Exp $ .\" .\" Copyright (c) 1986, 1991 The Regents of the University of California. @@ -81,7 +81,7 @@ autoconfiguration. There was a failure in allocating unibus resources for the device. .Pp .It "ex%d: configuration failed; cc = %x." -The hardware indicated an error when trying to initalize itself. +The hardware indicated an error when trying to initialize itself. The error code returned is described at length in the device Reference Manual. .Pp diff --git a/share/man/man4/man4.vax/uda.4 b/share/man/man4/man4.vax/uda.4 index 664c6c8cd50..ab8d6bdf8c3 100644 --- a/share/man/man4/man4.vax/uda.4 +++ b/share/man/man4/man4.vax/uda.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: uda.4,v 1.4 1999/06/05 13:18:39 aaron Exp $ +.\" $OpenBSD: uda.4,v 1.5 1999/09/23 04:12:06 alex Exp $ .\" $NetBSD: uda.4,v 1.3 1996/03/03 17:14:10 thorpej Exp $ .\" .\" Copyright (c) 1980, 1987, 1991 Regents of the University of California. @@ -252,7 +252,7 @@ The controller did not initialise within ten seconds. A hardware problem, but it sometimes goes away if you try again. .Pp .It uda%d: init failed, sa=%b -The controller refused to initalise. +The controller refused to initialise. .Pp .It uda%d: controller hung The controller never finished initialisation. Retrying may sometimes @@ -568,7 +568,7 @@ never uses compare operations. Something went wrong reading or writing a data sector. A `forced error' is a software-asserted error used to mark a sector that contains suspect data. Rewriting the sector will clear the forced error. This -is normally set only during bad block replacment, and the driver does +is normally set only during bad block replacement, and the driver does no bad block replacement, so these should not occur. A `header compare' error probably means the block is shot. A `sync timeout' presumably has something to do with sector synchronisation. |