1 files changed, 5 insertions, 5 deletions

diff --git a/secure/lib/libcrypto/man/man3/SSL_accept.3 b/secure/lib/libcrypto/man/man3/SSL_accept.3
index dbcf96a53806..ea3014a636a9 100644
--- a/secure/lib/libcrypto/man/man3/SSL_accept.3
+++ b/secure/lib/libcrypto/man/man3/SSL_accept.3
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 4.11 (Pod::Simple 3.40)
+.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.40)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -133,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "SSL_ACCEPT 3"
-.TH SSL_ACCEPT 3 "2020-04-21" "1.1.1g" "OpenSSL"
+.TH SSL_ACCEPT 3 "2020-09-22" "1.1.1h" "OpenSSL"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -159,14 +159,14 @@ The behaviour of \fBSSL_accept()\fR depends on the underlying \s-1BIO.\s0
 If the underlying \s-1BIO\s0 is \fBblocking\fR, \fBSSL_accept()\fR will only return once the
 handshake has been finished or an error occurred.
 .PP
-If the underlying \s-1BIO\s0 is \fBnon-blocking\fR, \fBSSL_accept()\fR will also return
+If the underlying \s-1BIO\s0 is \fBnonblocking\fR, \fBSSL_accept()\fR will also return
 when the underlying \s-1BIO\s0 could not satisfy the needs of \fBSSL_accept()\fR
 to continue the handshake, indicating the problem by the return value \-1.
 In this case a call to \fBSSL_get_error()\fR with the
 return value of \fBSSL_accept()\fR will yield \fB\s-1SSL_ERROR_WANT_READ\s0\fR or
 \&\fB\s-1SSL_ERROR_WANT_WRITE\s0\fR. The calling process then must repeat the call after
 taking appropriate action to satisfy the needs of \fBSSL_accept()\fR.
-The action depends on the underlying \s-1BIO.\s0 When using a non-blocking socket,
+The action depends on the underlying \s-1BIO.\s0 When using a nonblocking socket,
 nothing is to be done, but \fBselect()\fR can be used to check for the required
 condition. When using a buffering \s-1BIO,\s0 like a \s-1BIO\s0 pair, data must be written
 into or retrieved out of the \s-1BIO\s0 before being able to continue.
@@ -186,7 +186,7 @@ established.
 The \s-1TLS/SSL\s0 handshake was not successful because a fatal error occurred either
 at the protocol level or a connection failure occurred. The shutdown was
 not clean. It can also occur if action is needed to continue the operation
-for non-blocking BIOs. Call \fBSSL_get_error()\fR with the return value \fBret\fR
+for nonblocking BIOs. Call \fBSSL_get_error()\fR with the return value \fBret\fR
 to find out the reason.
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"