Fix incorrect usage of 'assure' and 'insure'.
Approved by: rrs (mentor)
This commit is contained in:
parent
4e5833219a
commit
e7f8dd75b3
@ -302,7 +302,7 @@ manual page.
|
||||
The
|
||||
.Nm
|
||||
grammar is inherently ambiguous.
|
||||
In order to assure a degree of consistency,
|
||||
In order to ensure a degree of consistency,
|
||||
the cases described in the
|
||||
.St -p1003.2 ,
|
||||
section D11.2/4.62.4, standard
|
||||
|
@ -189,7 +189,7 @@ unable to find a match in the
|
||||
.Pa /etc/ethers
|
||||
database.
|
||||
.Sh NOTES
|
||||
The user must insure that the hostname strings passed to the
|
||||
The user must ensure that the hostname strings passed to the
|
||||
.Fn ether_line ,
|
||||
.Fn ether_ntohost
|
||||
and
|
||||
|
@ -189,7 +189,7 @@ unable to find a match in the
|
||||
.Pa /etc/eui64
|
||||
database.
|
||||
.Sh NOTES
|
||||
The user must insure that the hostname strings passed to the
|
||||
The user must ensure that the hostname strings passed to the
|
||||
.\" .Fn eui64_line ,
|
||||
.Fn eui64_ntohost
|
||||
and
|
||||
|
@ -191,7 +191,7 @@ If that many milliseconds elapse
|
||||
and the peer has not acknowledged the data, the data will be
|
||||
skipped and no longer transmitted.
|
||||
Note that this policy does
|
||||
not even assure that the data will ever be sent.
|
||||
not even ensure that the data will ever be sent.
|
||||
In times of a congestion
|
||||
with large amounts of data being queued, the
|
||||
.Fa sinfo->sinfo_timetolive
|
||||
@ -218,7 +218,7 @@ policy transforms the
|
||||
.Fa sinfo->sinfo_timetolive
|
||||
into a number of retransmissions to allow.
|
||||
This policy
|
||||
always assures that at a minimum one send attempt is
|
||||
always ensures that at a minimum one send attempt is
|
||||
made of the data.
|
||||
After which no more than
|
||||
.Fa sinfo->sinfo_timetolive
|
||||
|
@ -203,7 +203,7 @@ If that many milliseconds elapse
|
||||
and the peer has not acknowledged the data, the data will be
|
||||
skipped and no longer transmitted.
|
||||
Note that this policy does
|
||||
not even assure that the data will ever be sent.
|
||||
not even ensure that the data will ever be sent.
|
||||
In times of a congestion
|
||||
with large amounts of data being queued, the
|
||||
.Fa timetolive
|
||||
@ -230,7 +230,7 @@ policy transforms the
|
||||
.Fa timetolive
|
||||
into a number of retransmissions to allow.
|
||||
This policy
|
||||
always assures that at a minimum one send attempt is
|
||||
always ensures that at a minimum one send attempt is
|
||||
made of the data.
|
||||
After which no more than
|
||||
.Fa timetolive
|
||||
|
@ -849,7 +849,7 @@ and
|
||||
.Fn vsprintf
|
||||
assume an infinitely long string,
|
||||
callers must be careful not to overflow the actual space;
|
||||
this is often hard to assure.
|
||||
this is often hard to ensure.
|
||||
For safety, programmers should use the
|
||||
.Fn snprintf
|
||||
interface instead.
|
||||
|
@ -266,7 +266,7 @@ options are enabled, the allocator prefers anonymous mappings over the DSS,
|
||||
but allocation only fails if memory cannot be acquired via either method.
|
||||
If neither option is enabled, then the
|
||||
.Dq M
|
||||
option is implicitly enabled in order to assure that there is a method for
|
||||
option is implicitly enabled in order to ensure that there is a method for
|
||||
acquiring memory.
|
||||
.It N
|
||||
Double/halve the number of arenas.
|
||||
@ -437,7 +437,7 @@ rounded up to the nearest multiple of the chunk size.
|
||||
.Pp
|
||||
Allocations are packed tightly together, which can be an issue for
|
||||
multi-threaded applications.
|
||||
If you need to assure that allocations do not suffer from cacheline sharing,
|
||||
If you need to ensure that allocations do not suffer from cacheline sharing,
|
||||
round your allocation requests up to the nearest multiple of the cacheline
|
||||
size.
|
||||
.Sh DEBUGGING MALLOC PROBLEMS
|
||||
|
@ -222,7 +222,7 @@ When a process
|
||||
exits, either voluntarily or involuntarily, the adjust on exit value
|
||||
for each semaphore is added to the semaphore's value.
|
||||
This can
|
||||
be used to insure that a resource is released if a process terminates
|
||||
be used to ensure that a resource is released if a process terminates
|
||||
unexpectedly.
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std semop
|
||||
|
@ -70,7 +70,7 @@ trailing
|
||||
.Ql H
|
||||
appended.
|
||||
.Pp
|
||||
An effort has been made to insure that
|
||||
An effort has been made to ensure that
|
||||
.Fn ipx_addr
|
||||
be compatible with most formats in common use.
|
||||
It will first separate an address into 1 to 3 fields using a single delimiter
|
||||
|
@ -234,7 +234,7 @@ Specify the name of the host from which to copy the
|
||||
.Tn NIS
|
||||
maps.
|
||||
This option
|
||||
is used to insure that
|
||||
is used to ensure that
|
||||
.Nm
|
||||
only copies maps from the
|
||||
.Tn NIS
|
||||
|
@ -2303,7 +2303,7 @@ Information necessary to route link-local packets to an
|
||||
interface is not available after processing by
|
||||
.Nm dummynet
|
||||
so those packets are dropped in the output path.
|
||||
Care should be taken to insure that link-local packets are not passed to
|
||||
Care should be taken to ensure that link-local packets are not passed to
|
||||
.Nm dummynet .
|
||||
.Sh CHECKLIST
|
||||
Here are some important points to consider when designing your
|
||||
|
@ -317,7 +317,7 @@ find out, how many bytes must be written into the buffer before the
|
||||
.IX Header "WARNING"
|
||||
As the data is buffered, \fISSL_operation()\fR may return with a \s-1ERROR_SSL_WANT_READ\s0
|
||||
condition, but there is still data in the write buffer. An application must
|
||||
not rely on the error value of \fISSL_operation()\fR but must assure that the
|
||||
not rely on the error value of \fISSL_operation()\fR but must ensure that the
|
||||
write buffer is always flushed first. Otherwise a deadlock may occur as
|
||||
the peer might be waiting for the data before being able to continue.
|
||||
.SH "SEE ALSO"
|
||||
|
@ -243,7 +243,7 @@ based systems
|
||||
Please remember that in order to use UDMA4/ATA66 and above modes you
|
||||
.Em must
|
||||
use 80 conductor cables.
|
||||
Please assure that ribbon cables are no longer than 45cm.
|
||||
Please ensure that ribbon cables are no longer than 45cm.
|
||||
In case of rounded ATA cables, the length depends on the
|
||||
quality of the cables.
|
||||
SATA cables can be up to 1m long according to the specification.
|
||||
|
@ -683,7 +683,7 @@ padding between the header and the link level protocol.
|
||||
The purpose here is to guarantee proper alignment of the packet
|
||||
data structures, which is required on alignment sensitive
|
||||
architectures and improves performance on many other architectures.
|
||||
The packet filter insures that the
|
||||
The packet filter ensures that the
|
||||
.Vt bpf_xhdr ,
|
||||
.Vt bpf_hdr
|
||||
and the network layer
|
||||
|
@ -892,7 +892,7 @@ by returning
|
||||
Each type should have an include file that defines the commands,
|
||||
argument format, and cookie for its own messages.
|
||||
The typecookie
|
||||
insures that the same header file was included by both sender and
|
||||
ensures that the same header file was included by both sender and
|
||||
receiver; when an incompatible change in the header file is made,
|
||||
the typecookie
|
||||
.Em must
|
||||
|
@ -108,7 +108,7 @@ piconet.
|
||||
Both asynchronous and isochronous services are supported.
|
||||
Between a master and a slave only a single ACL link can exist.
|
||||
For most ACL packets,
|
||||
packet retransmission is applied to assure data integrity.
|
||||
packet retransmission is applied to ensure data integrity.
|
||||
.Sh HOST CONTROLLER INTERFACE (HCI)
|
||||
The HCI provides a command interface to the baseband controller and link
|
||||
manager, and access to hardware status and control registers.
|
||||
|
@ -248,7 +248,7 @@ be echoed back unmodified.
|
||||
If the echoed data is corrupt, the driver
|
||||
will print an error message on the console and abort the device attach.
|
||||
The
|
||||
user should insure the NIC is installed in a 32-bit PCI slot to
|
||||
user should ensure the NIC is installed in a 32-bit PCI slot to
|
||||
avoid this problem.
|
||||
.Pp
|
||||
The RealTek 8169, 8169S and 8110S chips appear to only be capable of
|
||||
|
@ -437,7 +437,7 @@ There may be a need for
|
||||
.Fn spl
|
||||
protection around some of the
|
||||
.Nm
|
||||
list manipulation code to insure, for example, that the list of devices
|
||||
list manipulation code to ensure, for example, that the list of devices
|
||||
is not changed while someone is fetching the
|
||||
.Va kern.devstat.all
|
||||
.Nm sysctl
|
||||
|
@ -101,7 +101,7 @@ Node table entries are reference counted.
|
||||
That is, there is a count of all long term references that determines
|
||||
when an entry may be reclaimed.
|
||||
References are held by every in-flight frame sent to a station to
|
||||
insure the entry is not reclaimed while the frame is queued or otherwise
|
||||
ensure the entry is not reclaimed while the frame is queued or otherwise
|
||||
held by a driver.
|
||||
Routines that lookup a table entry return a
|
||||
.Dq held reference
|
||||
|
@ -198,7 +198,7 @@ also periodically checks the routing table entries.
|
||||
If an entry has not been updated for 3 minutes, the entry's metric
|
||||
is set to infinity and marked for deletion.
|
||||
Deletions are delayed
|
||||
an additional 60 seconds to insure the invalidation is propagated
|
||||
an additional 60 seconds to ensure the invalidation is propagated
|
||||
to other routers.
|
||||
.Pp
|
||||
Hosts acting as internetwork routers gratuitously supply their
|
||||
|
@ -123,7 +123,7 @@ domain and group of NIS servers.
|
||||
Up to ten servers can be specified.
|
||||
There must not be any spaces between the commas in the domain/server
|
||||
specification.
|
||||
This option is used to insure that the system binds
|
||||
This option is used to ensure that the system binds
|
||||
only to one domain and only to one of the specified servers, which
|
||||
is useful for systems that are both NIS servers and NIS
|
||||
clients: it provides a way to restrict what machines the system can
|
||||
|
Loading…
x
Reference in New Issue
Block a user