From: Matt Caswell Date: Wed, 26 Oct 2016 19:59:49 +0000 (+0100) Subject: Tweak the SSL_read()/SSL_write() text based on feedback received. X-Git-Tag: OpenSSL_1_1_1-pre1~3190 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=ed9fa2c74bbb9da312aa82865aeb3f9b75a8167b;p=oweals%2Fopenssl.git Tweak the SSL_read()/SSL_write() text based on feedback received. Reviewed-by: Rich Salz --- 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 to find out the reason and if -the call is retryable or not. +the event of a failure call L 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 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: