[openssl] master update

[tomas at openssl.org]

The branch master has been updated
       via  1ee1a169c310f3dc735a3d83298686cf70aa427a (commit)
      from  53d85372caac7a81eb14bea2eb06464778ed163c (commit)


- Log -----------------------------------------------------------------
commit 1ee1a169c310f3dc735a3d83298686cf70aa427a
Author: Nan Xiao <nan at chinadtrace.org>
Date:   Sat Mar 27 18:23:59 2021 +0800

    Fix typos in bio.pod
    
    CLA: trivial
    
    Reviewed-by: Kurt Roeckx <kurt at roeckx.be>
    Reviewed-by: Shane Lontis <shane.lontis at oracle.com>
    Reviewed-by: Tomas Mraz <tomas at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/14706)

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

Summary of changes:
 doc/man7/bio.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/man7/bio.pod b/doc/man7/bio.pod
index 092bdde184..e2c11665b9 100644
--- a/doc/man7/bio.pod
+++ b/doc/man7/bio.pod
@@ -17,7 +17,7 @@ details from an application. If an application uses a BIO for its
 I/O it can transparently handle SSL connections, unencrypted network
 connections and file I/O.
 
-There are two type of BIO, a source/sink BIO and a filter BIO.
+There are two types of BIO, a source/sink BIO and a filter BIO.
 
 As its name implies a source/sink BIO is a source and/or sink of data,
 examples include a socket BIO and a file BIO.
@@ -31,7 +31,7 @@ BIO will encrypt data if it is being written to and decrypt data
 if it is being read from.
 
 BIOs can be joined together to form a chain (a single BIO is a chain
-with one component). A chain normally consist of one source/sink
+with one component). A chain normally consists of one source/sink
 BIO and one or more filter BIOs. Data read from or written to the
 first BIO then traverses the chain to the end (normally a source/sink
 BIO).