diff options
author | Gustaf Neumann <neumann@wu-wien.ac.at> | 2020-06-29 21:13:07 +0200 |
---|---|---|
committer | Dr. Matthias St. Pierre <matthias.st.pierre@ncp-e.com> | 2020-07-05 01:49:20 +0200 |
commit | 8c1cbc72105ffd493b48e65f8f5fd3657dedb28c (patch) | |
tree | b1437e0210f80d7de45d8d33903a2f28fe1b82da /doc/man3/SSL_get_error.pod | |
parent | 3a19f1a9dd16f5855a7e2a42cd3e7f136f849bd3 (diff) |
Fix typos and repeated words
CLA: trivial
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
(Merged from https://github.com/openssl/openssl/pull/12320)
Diffstat (limited to 'doc/man3/SSL_get_error.pod')
-rw-r--r-- | doc/man3/SSL_get_error.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man3/SSL_get_error.pod b/doc/man3/SSL_get_error.pod index 07466731eb..0f2b10989e 100644 --- a/doc/man3/SSL_get_error.pod +++ b/doc/man3/SSL_get_error.pod @@ -74,7 +74,7 @@ See L<SSL_read(3)> for more information. B<SSL_ERROR_WANT_WRITE> is returned when the last operation was a write to a non-blocking B<BIO> and it was unable to sent all data to the B<BIO>. -When the B<BIO> is writeable again, the same function can be called again. +When the B<BIO> is writable again, the same function can be called again. Note that the retry may again lead to an B<SSL_ERROR_WANT_READ> or B<SSL_ERROR_WANT_WRITE> condition. @@ -84,7 +84,7 @@ protocol level. It is safe to call SSL_read() or SSL_read_ex() when more data is available even when the call that set this error was an SSL_write() or SSL_write_ex(). -However if the call was an SSL_write() or SSL_write_ex(), it should be called +However, if the call was an SSL_write() or SSL_write_ex(), it should be called again to continue sending the application data. For socket B<BIO>s (e.g. when SSL_set_fd() was used), select() or |