summaryrefslogtreecommitdiffstats
path: root/secure/lib
diff options
context:
space:
mode:
authorbrucec <brucec@FreeBSD.org>2010-09-11 10:49:56 +0000
committerbrucec <brucec@FreeBSD.org>2010-09-11 10:49:56 +0000
commit7adc5f91cff836324150e37db070cf854b475e73 (patch)
tree9b0dbb739b35e3d9e69dd5c1d72fd4a2c349c473 /secure/lib
parent6b5a9d0d4bcef5193a4b10feee02073eeb9ec0ff (diff)
downloadFreeBSD-src-7adc5f91cff836324150e37db070cf854b475e73.zip
FreeBSD-src-7adc5f91cff836324150e37db070cf854b475e73.tar.gz
Revert changes of 'assure' to 'ensure' made in r211936.
Approved by: rrs (mentor)
Diffstat (limited to 'secure/lib')
-rw-r--r--secure/lib/libcrypto/man/BIO_s_bio.32
1 files changed, 1 insertions, 1 deletions
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"
OpenPOWER on IntegriCloud