summaryrefslogtreecommitdiff
path: root/deps/openssl/openssl/doc/HOWTO/certificates.txt
diff options
context:
space:
mode:
Diffstat (limited to 'deps/openssl/openssl/doc/HOWTO/certificates.txt')
-rw-r--r--deps/openssl/openssl/doc/HOWTO/certificates.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/deps/openssl/openssl/doc/HOWTO/certificates.txt b/deps/openssl/openssl/doc/HOWTO/certificates.txt
index 65f8fc8296..c2efdca8dc 100644
--- a/deps/openssl/openssl/doc/HOWTO/certificates.txt
+++ b/deps/openssl/openssl/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