From bdcacd93b14ed7381a922b41d74c481224ef9fa1 Mon Sep 17 00:00:00 2001 From: FdaSilvaYY Date: Sat, 12 Aug 2017 20:02:24 +0200 Subject: Fix some typo and comments [skip ci] Reviewed-by: Andy Polyakov Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/4149) --- doc/man3/SSL_alloc_buffers.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/man3/SSL_alloc_buffers.pod b/doc/man3/SSL_alloc_buffers.pod index de33efb937..94bd05840c 100644 --- a/doc/man3/SSL_alloc_buffers.pod +++ b/doc/man3/SSL_alloc_buffers.pod @@ -20,7 +20,7 @@ The B mode releases read or write buffers whenever the buffers have been drained. These functions allow applications to manually control when buffers are freed and allocated. -After freeing the buffers, the buffers are automatically reallocted upon a +After freeing the buffers, the buffers are automatically reallocated upon a new read or write. The SSL_alloc_buffers() does not need to be called, but can be used to make sure the buffers are pre-allocated. This can be used to avoid allocation during data processing or with CRYPTO_set_mem_functions() @@ -44,7 +44,7 @@ The SSL_free_buffers() function returns 1 if the buffers have been freed. This value is also returned if the buffers had been freed before calling SSL_free_buffers(). The SSL_alloc_buffers() function returns 1 if the buffers have been allocated. -This valus is also returned if the buffers had been allocated before calling +This value is also returned if the buffers had been allocated before calling SSL_alloc_buffers(). =back -- cgit v1.2.3