diff options
| author | Xiaoyin Liu <xiaoyinl@users.noreply.github.com> | 2017-07-21 16:13:13 -0400 |
|---|---|---|
| committer | Rich Salz <rsalz@openssl.org> | 2017-07-26 23:09:40 -0400 |
| commit | 1d7f3350f8d6651296d5ef9c124439e9b56cf37b (patch) | |
| tree | a65da8948edb1326ad7a83aa453c7a1a628919c6 /doc/HOWTO/certificates.txt | |
| parent | 9f08a1c63efa2205aca4361a830ac04407325597 (diff) | |
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@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/3986)
Diffstat (limited to 'doc/HOWTO/certificates.txt')
| -rw-r--r-- | doc/HOWTO/certificates.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/HOWTO/certificates.txt b/doc/HOWTO/certificates.txt index 65f8fc8296..c2efdca8dc 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 |