[openssl-commits] [openssl] OpenSSL_1_1_1-stable update

[nic.tuv at gmail.com]

The branch OpenSSL_1_1_1-stable has been updated
       via  9b977afc0b25f57021f9e4721cb56bd63548c838 (commit)
      from  00f561ab9c70dec128467fb2b4f3eb952829c4c4 (commit)


- Log -----------------------------------------------------------------
commit 9b977afc0b25f57021f9e4721cb56bd63548c838
Author: Matt Eaton <agnosticdev at gmail.com>
Date:   Thu Sep 13 21:11:14 2018 -0500

    Update RAND_DRBG.pod
    
    Fixed a minor typo while reading the documentation.
    I agree that this contribution is trivial can be freely used.
    
    CLA: trivial
    
    Reviewed-by: Nicola Tuveri <nic.tuv at gmail.com>
    Reviewed-by: Kurt Roeckx <kurt at roeckx.be>
    (Merged from https://github.com/openssl/openssl/pull/7221)

-----------------------------------------------------------------------

Summary of changes:
 doc/man7/RAND_DRBG.pod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/man7/RAND_DRBG.pod b/doc/man7/RAND_DRBG.pod
index b89c30d..ba457f0 100644
--- a/doc/man7/RAND_DRBG.pod
+++ b/doc/man7/RAND_DRBG.pod
@@ -189,7 +189,7 @@ In addition to automatic reseeding, the caller can request an immediate
 reseeding of the DRBG with fresh entropy by setting the
 I<prediction resistance> parameter to 1 when calling L<RAND_DRBG_generate(3)>.
 
-The dcoument [NIST SP 800-90C] describes prediction resistance requests
+The document [NIST SP 800-90C] describes prediction resistance requests
 in detail and imposes strict conditions on the entropy sources that are
 approved for providing prediction resistance.
 Since the default DRBG implementation does not have access to such an approved