Use consistent spelling,
writeable -> writable (recall prior debate over this? :-) initialise -> initialize recognise -> recognize Merry Christmas! :)
This commit is contained in:
parent
42fa505b7e
commit
dfb9495b2a
@ -33,7 +33,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" @(#)ls.1 8.7 (Berkeley) 7/29/94
|
||||
.\" $Id: ls.1,v 1.14 1997/04/29 10:03:05 dfr Exp $
|
||||
.\" $Id: ls.1,v 1.15 1997/09/18 06:55:21 charnier Exp $
|
||||
.\"
|
||||
.Dd July 29, 1994
|
||||
.Dt LS 1
|
||||
@ -276,7 +276,7 @@ and setgroup-ID mode is set.
|
||||
The file is executable or the directory is
|
||||
searchable.
|
||||
.It Sy \-
|
||||
The file is neither readable, writeable, executable,
|
||||
The file is neither readable, writable, executable,
|
||||
nor set-user-ID nor set-group-ID mode, nor sticky. (See below.)
|
||||
.El
|
||||
.Pp
|
||||
|
@ -25,7 +25,7 @@ and allows customization of
|
||||
.Nm ldd Ns 's
|
||||
output. See
|
||||
.Xr rtld 1
|
||||
for a list of recognised conversion characters.
|
||||
for a list of recognized conversion characters.
|
||||
.Pp
|
||||
The
|
||||
.Fl v
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: pthread.3,v 1.2 1997/03/07 03:27:53 jmg Exp $
|
||||
.\" $Id: pthread.3,v 1.3 1997/11/05 03:54:11 steve Exp $
|
||||
.\"
|
||||
.Dd April 4, 1996
|
||||
.Dt PTHREAD 3
|
||||
@ -120,7 +120,7 @@ Initialize a mutex attributes object with default values.
|
||||
.It int Fn pthread_mutex_destroy "pthread_mutex_t *mutex"
|
||||
Destroy a mutex.
|
||||
.It int Fn pthread_mutex_init "pthread_mutex_t *mutex" "const pthread_mutexattr_t *attr"
|
||||
Initialise a mutex with specified attributes.
|
||||
Initialize a mutex with specified attributes.
|
||||
.It int Fn pthread_mutex_lock "pthread_mutex_t *mutex"
|
||||
Lock a mutex and block until it becomes available.
|
||||
.It int Fn pthread_mutex_trylock "pthread_mutex_t *mutex"
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: od.4,v 1.1 1997/04/01 19:52:37 mpp Exp $
|
||||
.\" $Id: od.4,v 1.2 1997/09/29 10:10:16 wosch Exp $
|
||||
.\"
|
||||
.Dd March 16, 1997
|
||||
.Dt OD 4
|
||||
@ -153,7 +153,7 @@ interface to the SCSI bad-block mapping.
|
||||
.It Dv DIOCGDINFO
|
||||
Read the in-core copy of the disklabel for the
|
||||
drive from the kernel. This may be a fictitious disklabel if the drive
|
||||
has never been initialised, in which case it will contain information read
|
||||
has never been initialized, in which case it will contain information read
|
||||
from the SCSI inquiry commands, and should be the same as
|
||||
the information printed at boot.
|
||||
.It Dv DIOCSDINFO
|
||||
|
@ -26,14 +26,14 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: VFS_INIT.9,v 1.2 1997/04/13 14:48:48 bde Exp $
|
||||
.\" $Id: VFS_INIT.9,v 1.3 1997/09/29 10:10:43 wosch Exp $
|
||||
.\"
|
||||
.Dd July 24, 1996
|
||||
.Os
|
||||
.Dt VFS_INIT 9
|
||||
.Sh NAME
|
||||
.Nm VFS_INIT
|
||||
.Nd initialise a filesystem
|
||||
.Nd initialize a filesystem
|
||||
.Sh SYNOPSIS
|
||||
.Fd #include <sys/param.h>
|
||||
.Fd #include <sys/mount.h>
|
||||
@ -41,7 +41,7 @@
|
||||
.Ft int
|
||||
.Fn VFS_INIT
|
||||
.Sh DESCRIPTION
|
||||
This function is called once to allow a filesystem to initialise any
|
||||
This function is called once to allow a filesystem to initialize any
|
||||
global data structures that it might have. It is either called when
|
||||
the operating system boots or, for dynamically loaded filesystems,
|
||||
when the kernel module containing the filesystem is loaded.
|
||||
|
@ -26,7 +26,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.
|
||||
.\"
|
||||
.\" $Id: VFS_MOUNT.9,v 1.1 1997/03/03 17:59:54 dfr Exp $
|
||||
.\" $Id: VFS_MOUNT.9,v 1.2 1997/09/29 10:10:44 wosch Exp $
|
||||
.\"
|
||||
.Dd July 24, 1996
|
||||
.Os
|
||||
@ -74,7 +74,7 @@ to update the NFS export information for the filesystem.
|
||||
If the
|
||||
.Dv MNT_UPDATE
|
||||
flag is not specified, then this is a newly mounted filesystem. The
|
||||
filesystem code should allocate and initialise
|
||||
filesystem code should allocate and initialize
|
||||
any private data needed to represent
|
||||
the filesystem (it can use the
|
||||
.Fa mp->mnt_data
|
||||
|
@ -25,7 +25,7 @@ and allows customization of
|
||||
.Nm ldd Ns 's
|
||||
output. See
|
||||
.Xr rtld 1
|
||||
for a list of recognised conversion characters.
|
||||
for a list of recognized conversion characters.
|
||||
.Pp
|
||||
The
|
||||
.Fl v
|
||||
|
@ -59,7 +59,7 @@ file, and from this find a driver that can be used to
|
||||
interface to the particular card. There is a many-to-one mapping
|
||||
between cards to drivers i.e a single driver may interface to
|
||||
multiple types of cards. To aid this, card parameters may be
|
||||
specified separately from the driver to initialise the card or
|
||||
specified separately from the driver to initialize the card or
|
||||
extract (in the case of a network card) an Ethernet address.
|
||||
.Pp
|
||||
Once a driver is allocated to a card, it stays
|
||||
@ -112,7 +112,7 @@ The syntax of the resources is as follows:
|
||||
.Pp
|
||||
Each of the statements define I/O, memory or IRQ
|
||||
blocks that can be used to allocate to drivers when
|
||||
they are initialised.
|
||||
they are initialized.
|
||||
.Pp
|
||||
Multiple lines of any of the above statements may be
|
||||
present to allow separate blocks of each resource to be
|
||||
|
@ -23,7 +23,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.
|
||||
.\"
|
||||
.\" $Id: pccardd.8,v 1.7 1997/02/22 16:08:58 peter Exp $
|
||||
.\" $Id: pccardd.8,v 1.8 1997/10/06 11:36:07 charnier Exp $
|
||||
.\"
|
||||
.Dd November 1, 1994
|
||||
.Dt PCCARD 8
|
||||
@ -103,7 +103,7 @@ is that once a driver is associated with a card, the
|
||||
driver's
|
||||
.Fn probe
|
||||
routine has been called, and this usually causes driver specific
|
||||
data areas to be initialised with the I/O ports or memory resources
|
||||
data areas to be initialized with the I/O ports or memory resources
|
||||
allocated to the card. Most drivers are not designed to be
|
||||
disassociated from the hardware and then reassociated with different
|
||||
parameters. This will change significantly when loadable kernel
|
||||
|
@ -22,7 +22,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: pw.conf.5,v 1.6 1997/02/22 16:12:26 peter Exp $
|
||||
.\" $Id: pw.conf.5,v 1.7 1997/10/10 06:23:34 charnier Exp $
|
||||
.\"
|
||||
.Dd December 9, 1996
|
||||
.Dt PW.CONF 5
|
||||
@ -56,7 +56,7 @@ blank lines and lines commencing with a
|
||||
character are considered comments, and any remaining lines are
|
||||
examined for a leading keyword, followed by corresponding data.
|
||||
.Pp
|
||||
Keywords recognised by
|
||||
Keywords recognized by
|
||||
.Xr pw 8
|
||||
are:
|
||||
.Bl -tag -width password_days -offset indent -compact
|
||||
|
Loading…
Reference in New Issue
Block a user