[openssl-commits] [openssl] master update

Rich Salz rsalz at openssl.org
Thu Jul 27 03:09:54 UTC 2017


The branch master has been updated
       via  1d7f3350f8d6651296d5ef9c124439e9b56cf37b (commit)
      from  9f08a1c63efa2205aca4361a830ac04407325597 (commit)


- Log -----------------------------------------------------------------
commit 1d7f3350f8d6651296d5ef9c124439e9b56cf37b
Author: Xiaoyin Liu <xiaoyinl at users.noreply.github.com>
Date:   Fri Jul 21 16:13:13 2017 -0400

    Various doc fixes.
    
    Fix typo in NOTES.WIN: this -> these
    
    Fix wrong capital letter in certificates.txt
    
    Make number of characters in each line more even
    Remove redundant empty line
    
    Reviewed-by: Richard Levitte <levitte at openssl.org>
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/3986)

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

Summary of changes:
 NOTES.WIN                        | 2 +-
 doc/HOWTO/certificates.txt       | 2 +-
 doc/HOWTO/proxy_certificates.txt | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/NOTES.WIN b/NOTES.WIN
index c31aed9..ac215c3 100644
--- a/NOTES.WIN
+++ b/NOTES.WIN
@@ -6,7 +6,7 @@
  --------------------------------------------------
 
  In addition to the requirements and instructions listed in INSTALL,
- this are required as well:
+ these are required as well:
 
  - You need Perl.  We recommend ActiveState Perl, available from
    https://www.activestate.com/ActivePerl. Another viable alternative
diff --git a/doc/HOWTO/certificates.txt b/doc/HOWTO/certificates.txt
index 65f8fc8..c2efdca 100644
--- a/doc/HOWTO/certificates.txt
+++ b/doc/HOWTO/certificates.txt
@@ -90,7 +90,7 @@ Your key most definitely is if you have followed the examples above.
 However, some (most?) certificate authorities will encode them with
 things like PKCS7 or PKCS12, or something else.  Depending on your
 applications, this may be perfectly OK, it all depends on what they
-know how to decode.  If not, There are a number of OpenSSL tools to
+know how to decode.  If not, there are a number of OpenSSL tools to
 convert between some (most?) formats.
 
 So, depending on your application, you may have to convert your
diff --git a/doc/HOWTO/proxy_certificates.txt b/doc/HOWTO/proxy_certificates.txt
index 642bec9..18b3e03 100644
--- a/doc/HOWTO/proxy_certificates.txt
+++ b/doc/HOWTO/proxy_certificates.txt
@@ -18,7 +18,7 @@ rights to some other entity (a computer process, typically, or sometimes to the
 user itself).  This allows the entity to perform operations on behalf of the
 owner of the EE certificate.
 
-See http://www.ietf.org/rfc/rfc3820.txt for more information.
+See https://www.ietf.org/rfc/rfc3820.txt for more information.
 
 
 2. A warning about proxy certificates


More information about the openssl-commits mailing list