Expand contractions.
This commit is contained in:
parent
7b97099d42
commit
fbf9b468d5
@ -292,7 +292,7 @@ This works well with regard to threading scalability, but incurs some costs.
|
||||
There is a small fixed per-arena overhead, and additionally, arenas manage
|
||||
memory completely independently of each other, which means a small fixed
|
||||
increase in overall memory fragmentation.
|
||||
These overheads aren't generally an issue, given the number of arenas normally
|
||||
These overheads are not generally an issue, given the number of arenas normally
|
||||
used.
|
||||
Note that using substantially more arenas than the default is not likely to
|
||||
improve performance, mainly due to reduced cache performance.
|
||||
|
@ -172,7 +172,7 @@ destroy his keys,
|
||||
it is possible to get the data back by restoring keys from the backup.
|
||||
.It
|
||||
Providers can be configured to automatically detach on last close
|
||||
(so users don't have to remember to detach providers after unmounting
|
||||
(so users do not have to remember to detach providers after unmounting
|
||||
the file systems).
|
||||
.It
|
||||
Allows to attach a provider with a random, one-time key - useful for swap
|
||||
@ -250,7 +250,7 @@ Additional options include:
|
||||
.Bl -tag -width ".Fl a Ar algo"
|
||||
.It Fl d
|
||||
If specified, a decrypted provider will be detached automatically on last close.
|
||||
This can help with short memory - user doesn't have to remember to detach the
|
||||
This can help with short memory - user does not have to remember to detach the
|
||||
provider after unmounting the file system.
|
||||
It only works when the provider was opened for writing, so it will not work if
|
||||
the file system on the provider is mounted read-only.
|
||||
|
@ -93,7 +93,7 @@ In addition to the ISA devices, the PC Card devices based on the CS889x0
|
||||
family are also supported.
|
||||
The IBM EtherJet PCMCIA Card is the only known device based on this
|
||||
chip.
|
||||
The PC Card support doesn't need the above specific ISA hints to work.
|
||||
The PC Card support does not need the above specific ISA hints to work.
|
||||
The PC Card support may not work for 10base2 (thinnet) connections and may
|
||||
bogusly claim to support 10base5 (there are no known cards that have an
|
||||
AUI necessary for 10base5 support on their dongles).
|
||||
|
@ -171,7 +171,7 @@ The driver was unable to allocate the I/O space that it thinks
|
||||
should be there.
|
||||
Look for conflicts with other devices.
|
||||
.It "ep0: No irq?!"
|
||||
The driver couldn't allocate the interrupt it wanted.
|
||||
The driver could not allocate the interrupt it wanted.
|
||||
Look for conflicts, although sharing interrupts for PC Card is normal.
|
||||
.It "ep0: No connectors!"
|
||||
The driver queried the hardware for what ethernet attachment were
|
||||
@ -186,7 +186,7 @@ This may happen in extremely low memory conditions.
|
||||
The driver does not know what to do with the information the EEPROM
|
||||
has about connectors, so it is assuming the worst.
|
||||
.It "ep0: unknown ID 0xXXXXXXXX"
|
||||
The driver has found an ID that it believes it supports, but doesn't
|
||||
The driver has found an ID that it believes it supports, but does not
|
||||
have a specific identification string to present to the user.
|
||||
.It "ep0: <%s> at port 0x%03x in EISA mode"
|
||||
The 3C509 ISA card is in EISA mode.
|
||||
|
@ -196,7 +196,7 @@ When
|
||||
.Nm
|
||||
is a PPPoE client, it initiates a session encapsulating packets into
|
||||
incorrect 3Com ethertypes.
|
||||
This compatibility option doesn't affect server mode.
|
||||
This compatibility option does not affect server mode.
|
||||
In server mode
|
||||
.Nm
|
||||
supports both modes simultaneously, depending on the ethertype, the
|
||||
@ -209,7 +209,7 @@ to a PADI requests with empty Service-Name tag, returning all available
|
||||
Service-Name(s) on node.
|
||||
This option is necessary for compatibility with D-Link DI-614+ and DI-624+
|
||||
SOHO routers as clients, when serving only specific Service-Name.
|
||||
This compatibility option doesn't affect client mode.
|
||||
This compatibility option does not affect client mode.
|
||||
.El
|
||||
.Pp
|
||||
.It Dv NGM_PPPOE_SETMODE
|
||||
|
@ -191,7 +191,7 @@ sysctl. It defaults to 1000.
|
||||
It is not recommanded to use more than 1000 pseudo-terminals, as all software
|
||||
which use
|
||||
.Xr utmp 5
|
||||
won't be able to handle pseudo-terminals with number superior to 999.
|
||||
will not be able to handle pseudo-terminals with number superior to 999.
|
||||
|
||||
The pts implementation also supports the
|
||||
.Dv TIOCGPTN
|
||||
|
@ -68,7 +68,7 @@ new ruleset is started.
|
||||
.Pp
|
||||
One custom ruleset has to be enabled in
|
||||
.Pa /etc/rc.conf ,
|
||||
otherwise it won't be applied to the
|
||||
otherwise it will not be applied to the
|
||||
.Pa /dev
|
||||
file system by the default system startup process.
|
||||
For example, to enable a
|
||||
|
@ -56,7 +56,7 @@ In all other cases
|
||||
It is questionable what bootable means here.
|
||||
Does it mean that the BIOS is available to start a boot on that file system
|
||||
or does it mean that there is something bootable?
|
||||
In either case this information isn't available so this variable returns True
|
||||
In either case this information is not available so this variable returns True
|
||||
for the root file system (which is not necessarily correct) and False for
|
||||
all others.
|
||||
.It Va hrFSLastFullBackupDate
|
||||
|
@ -163,8 +163,8 @@ Running
|
||||
.Cm update
|
||||
from
|
||||
.Xr cron 8
|
||||
is a bad idea -- if you're ever installing or updating a
|
||||
port at the time the cron job runs, you'll probably end up
|
||||
is a bad idea -- if you are ever installing or updating a
|
||||
port at the time the cron job runs, you will probably end up
|
||||
in a mess when
|
||||
.Nm
|
||||
updates or removes files which are being used by the port
|
||||
|
Loading…
x
Reference in New Issue
Block a user