aboutsummaryrefslogtreecommitdiff
path: root/secure/lib
diff options
context:
space:
mode:
authorRebecca Cran <brucec@FreeBSD.org>2010-08-28 16:32:01 +0000
committerRebecca Cran <brucec@FreeBSD.org>2010-08-28 16:32:01 +0000
commite7f8dd75b3c11bd606a3a4fa82a3bd7834f65421 (patch)
tree63ce23a3afd66a826b4c91820bd78ab505f92089 /secure/lib
parent4e5833219ab708ca2c6b6e626ee2079f2edcf9a3 (diff)
Notes
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 34345d112a8f..956f3f6d13e3 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 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"