Expand contractions.
This commit is contained in:
parent
67c8649f7f
commit
423ac68026
@ -512,7 +512,7 @@ The only reason to call
|
||||
over
|
||||
.Fn dialog_radiolist
|
||||
in the new API model is to inherit the base
|
||||
behavior, you're no longer constrained by it.
|
||||
behavior, you are no longer constrained by it.
|
||||
.Pp
|
||||
Returns 0 on success, 1 on Cancel, and -1 on failure or ESC.
|
||||
.Pp
|
||||
|
@ -117,7 +117,7 @@ The
|
||||
system call
|
||||
will fail if:
|
||||
.Bl -tag -width Er
|
||||
.\" ipcperm could fail (we're opening to read and write, as it were)
|
||||
.\" ipcperm could fail (we are opening to read and write, as it were)
|
||||
.It Bq Er EACCES
|
||||
Access permission failure.
|
||||
.\"
|
||||
|
@ -199,4 +199,4 @@ nor to find a file with a specific hash value.
|
||||
There is on the other hand no guarantee that such a method does not exist.
|
||||
.Pp
|
||||
MD2 has only been licensed for use in Privacy Enhanced Mail.
|
||||
Use MD4 or MD5 if that is not what you're doing.
|
||||
Use MD4 or MD5 if that is not what you are doing.
|
||||
|
@ -74,7 +74,7 @@ In order to retrieve printer info from /dev/lpt0, just apply the
|
||||
.Nm cat
|
||||
command to the device.
|
||||
If the printer supports IEEE1284 nibble mode and has
|
||||
data to send to the host, you'll get it.
|
||||
data to send to the host, you will get it.
|
||||
.Sh FILES
|
||||
.Bl -tag -width Pa -compact
|
||||
.It Pa /dev/lpt0
|
||||
|
@ -85,7 +85,7 @@ corresponding to the device in question.
|
||||
Although this ioctl is available through the
|
||||
.Nm
|
||||
driver, it is of limited use, since the caller must already know that
|
||||
the device in question is a passthrough device if they're issuing this
|
||||
the device in question is a passthrough device if they are issuing this
|
||||
ioctl.
|
||||
It is probably more useful to issue this ioctl through the
|
||||
.Xr xpt 4
|
||||
|
@ -73,7 +73,7 @@ size is 4096).
|
||||
.Pp
|
||||
VM buffers also keep track of a byte-granular dirty range and valid range.
|
||||
This feature is normally only used by the NFS subsystem.
|
||||
I'm not sure why it
|
||||
I am not sure why it
|
||||
is used at all, actually, since we have DEV_BSIZE valid/dirty granularity
|
||||
within the VM buffer.
|
||||
If a buffer dirty operation creates a 'hole',
|
||||
|
@ -245,7 +245,7 @@ discovers all locally attached multicast capable interfaces and forwards
|
||||
on all of them.
|
||||
.It netmask Ar netmask
|
||||
If the kernel's netmask does not accurately reflect
|
||||
the subnet (e.g.\& you're using proxy-ARP in lieu of IP subnetting), use the
|
||||
the subnet (e.g.\& you are using proxy-ARP in lieu of IP subnetting), use the
|
||||
netmask command to describe the real netmask.
|
||||
.It altnet Ar network/mask-len
|
||||
If a phyint is attached to multiple IP subnets, describe each additional subnet
|
||||
|
@ -289,7 +289,7 @@ add match-prefix fec0:0:0:: /48 use-prefix 3ffe:501:ffff:: /48 keeplen 16;
|
||||
.Pp
|
||||
.\"
|
||||
If your routers do not support IPv6 multicast forwarding,
|
||||
you'll need to specify each destination at
|
||||
you will need to specify each destination at
|
||||
.Cm dest
|
||||
command.
|
||||
.\"
|
||||
|
Loading…
Reference in New Issue
Block a user