summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2016-10-26 20:59:49 +0100
committerMatt Caswell <matt@openssl.org>2016-11-04 12:09:46 +0000
commited9fa2c74bbb9da312aa82865aeb3f9b75a8167b (patch)
tree5fa17cf5a4faf14052f77848d4568bf4a2403b25
parent54105ddd230c0d77fab91dd3f423b58b2a976de7 (diff)
Tweak the SSL_read()/SSL_write() text based on feedback received.
Reviewed-by: Rich Salz <rsalz@openssl.org>
-rw-r--r--doc/man3/SSL_read.pod4
-rw-r--r--doc/man3/SSL_write.pod2
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/man3/SSL_read.pod b/doc/man3/SSL_read.pod
index c87024ad90..7c175bfb7c 100644
--- a/doc/man3/SSL_read.pod
+++ b/doc/man3/SSL_read.pod
@@ -92,8 +92,8 @@ Success means that 1 or more application data bytes have been read from the SSL
connection. Failure means that no bytes could be read from the SSL connection.
Failures can be retryable (e.g. we are waiting for more bytes to
be delivered by the network) or non-retryable (e.g. a fatal network error). In
-the event of a failure call L<SSL_get_error(3)> to find out the reason and if
-the call is retryable or not.
+the event of a failure call L<SSL_get_error(3)> to find out the reason which
+indicates whether the call is retryable or not.
For SSL_read() and SSL_peek() the following return values can occur:
diff --git a/doc/man3/SSL_write.pod b/doc/man3/SSL_write.pod
index 6c9b28832e..c860ed7978 100644
--- a/doc/man3/SSL_write.pod
+++ b/doc/man3/SSL_write.pod
@@ -80,7 +80,7 @@ no bytes could be written to the SSL connection (if
SSL_MODE_ENABLE_PARTIAL_WRITE is in use). Failures can be retryable (e.g. the
network write buffer has temporarily filled up) or non-retryable (e.g. a fatal
network error). In the event of a failure call L<SSL_get_error(3)> to find out
-the reason and if the call is retryable or not.
+the reason which indicates whether the call is retryable or not.
For SSL_write() the following return values can occur: