[openssl-commits] [openssl] OpenSSL_1_1_0-stable update

[matthias.st.pierre at ncp-e.com]

The branch OpenSSL_1_1_0-stable has been updated
       via  30ecc60ac1fc7012daabc9eda7eacd401ef8e15a (commit)
      from  ea8d9cec4739d6b06d25f3d01a1b7666d5a090ed (commit)


- Log -----------------------------------------------------------------
commit 30ecc60ac1fc7012daabc9eda7eacd401ef8e15a
Author: Ivan Filenko <ivan.filenko at protonmail.com>
Date:   Sun Feb 25 16:49:27 2018 +0300

    Fix typo in ASN1_STRING_length doc
    
    CLA: trivial
    
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre at ncp-e.com>
    (Merged from https://github.com/openssl/openssl/pull/5458)

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

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

diff --git a/doc/crypto/ASN1_STRING_length.pod b/doc/crypto/ASN1_STRING_length.pod
index 26cb176..a774a42 100644
--- a/doc/crypto/ASN1_STRING_length.pod
+++ b/doc/crypto/ASN1_STRING_length.pod
@@ -71,8 +71,8 @@ utility functions should be used instead.
 In general it cannot be assumed that the data returned by ASN1_STRING_data()
 is null terminated or does not contain embedded nulls. The actual format
 of the data will depend on the actual string type itself: for example
-for and IA5String the data will be ASCII, for a BMPString two bytes per
-character in big endian format, UTF8String will be in UTF8 format.
+for an IA5String the data will be ASCII, for a BMPString two bytes per
+character in big endian format, and for an UTF8String it will be in UTF8 format.
 
 Similar care should be take to ensure the data is in the correct format
 when calling ASN1_STRING_set().