Tweak the SSL_read()/SSL_write() text based on feedback received.

Reviewed-by: Rich Salz <rsalz@openssl.org>

diff --git a/doc/man3/SSL_read.pod b/doc/man3/SSL_read.pod
index c87024ad90ffe1ccd148b9a892de6e91c593cb9e..7c175bfb7c62d93790e11adf10d5536ef8796b30 100644 (file)
--- 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 6c9b28832ee37235fdda1a787057d4e9b47b7156..c860ed7978188d3d747bb40dbf133c16618fe5ba 100644 (file)
--- 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: