diff options
| -rw-r--r-- | bin/test/test.1 | 2 | ||||
| -rw-r--r-- | lib/libc/net/sctp_send.3 | 4 | ||||
| -rw-r--r-- | lib/libc/net/sctp_sendmsg.3 | 4 | ||||
| -rw-r--r-- | lib/libc/stdio/printf.3 | 2 | ||||
| -rw-r--r-- | lib/libc/stdlib/malloc.3 | 4 | ||||
| -rw-r--r-- | secure/lib/libcrypto/man/BIO_s_bio.3 | 2 | ||||
| -rw-r--r-- | share/man/man4/ata.4 | 2 | ||||
| -rw-r--r-- | share/man/man4/ng_hci.4 | 2 |
8 files changed, 11 insertions, 11 deletions
diff --git a/bin/test/test.1 b/bin/test/test.1 index 8cf43d0..5815b12 100644 --- a/bin/test/test.1 +++ b/bin/test/test.1 @@ -302,7 +302,7 @@ manual page. The .Nm grammar is inherently ambiguous. -In order to ensure a degree of consistency, +In order to assure a degree of consistency, the cases described in the .St -p1003.2 , section D11.2/4.62.4, standard diff --git a/lib/libc/net/sctp_send.3 b/lib/libc/net/sctp_send.3 index 8d860df..9acb616 100644 --- a/lib/libc/net/sctp_send.3 +++ b/lib/libc/net/sctp_send.3 @@ -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 ensure that the data will ever be sent. +not even assure 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 ensures that at a minimum one send attempt is +always assures that at a minimum one send attempt is made of the data. After which no more than .Fa sinfo->sinfo_timetolive diff --git a/lib/libc/net/sctp_sendmsg.3 b/lib/libc/net/sctp_sendmsg.3 index 1015558..ddd88b4 100644 --- a/lib/libc/net/sctp_sendmsg.3 +++ b/lib/libc/net/sctp_sendmsg.3 @@ -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 ensure that the data will ever be sent. +not even assure 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 ensures that at a minimum one send attempt is +always assures that at a minimum one send attempt is made of the data. After which no more than .Fa timetolive diff --git a/lib/libc/stdio/printf.3 b/lib/libc/stdio/printf.3 index a0d2613..90a8ed8 100644 --- a/lib/libc/stdio/printf.3 +++ b/lib/libc/stdio/printf.3 @@ -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 ensure. +this is often hard to assure. For safety, programmers should use the .Fn snprintf interface instead. diff --git a/lib/libc/stdlib/malloc.3 b/lib/libc/stdlib/malloc.3 index 90781a1..2f21b6a 100644 --- a/lib/libc/stdlib/malloc.3 +++ b/lib/libc/stdlib/malloc.3 @@ -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 ensure that there is a method for +option is implicitly enabled in order to assure 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 ensure that allocations do not suffer from cacheline sharing, +If you need to assure 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 diff --git a/secure/lib/libcrypto/man/BIO_s_bio.3 b/secure/lib/libcrypto/man/BIO_s_bio.3 index 956f3f6..34345d1 100644 --- a/secure/lib/libcrypto/man/BIO_s_bio.3 +++ b/secure/lib/libcrypto/man/BIO_s_bio.3 @@ -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 ensure that the +not rely on the error value of \fISSL_operation()\fR but must assure 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" diff --git a/share/man/man4/ata.4 b/share/man/man4/ata.4 index 22de1a9..ba67991 100644 --- a/share/man/man4/ata.4 +++ b/share/man/man4/ata.4 @@ -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 ensure that ribbon cables are no longer than 45cm. +Please assure 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. diff --git a/share/man/man4/ng_hci.4 b/share/man/man4/ng_hci.4 index 5d8dab3..28de180 100644 --- a/share/man/man4/ng_hci.4 +++ b/share/man/man4/ng_hci.4 @@ -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 ensure data integrity. +packet retransmission is applied to assure 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. |
