diff options
author | Thiago Suchorski <suchorski@ymail.com> | 2022-09-22 08:27:27 -0300 |
---|---|---|
committer | Dr. Matthias St. Pierre <matthias.st.pierre@ncp-e.com> | 2022-10-09 17:40:29 +0200 |
commit | af33b200da8040c78dbfd8405878190980727171 (patch) | |
tree | b2117a3dc945c00ff9b20bd7d0b6675374480ed1 /README-PROVIDERS.md | |
parent | 19b6b5f4791e3531cd6d3aabc8706d590ade14b7 (diff) | |
download | openssl-new-af33b200da8040c78dbfd8405878190980727171.tar.gz |
Fixed some grammar and spelling
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
(Merged from https://github.com/openssl/openssl/pull/19262)
Diffstat (limited to 'README-PROVIDERS.md')
-rw-r--r-- | README-PROVIDERS.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/README-PROVIDERS.md b/README-PROVIDERS.md index 33533f671c..3b5476831b 100644 --- a/README-PROVIDERS.md +++ b/README-PROVIDERS.md @@ -15,7 +15,7 @@ Standard Providers Providers are containers for algorithm implementations. Whenever a cryptographic algorithm is used via the high level APIs a provider is selected. It is that provider implementation that actually does the required work. There are five -providers distributed with OpenSSL. In the future we expect third parties to +providers distributed with OpenSSL. In the future, we expect third parties to distribute their own providers which can be added to OpenSSL dynamically. Documentation about writing providers is available on the [provider(7)] manual page. @@ -31,10 +31,10 @@ explicitly (e.g. in the application or via config), then this is the provider that will be used. It is loaded automatically the first time that we try to get an algorithm from a provider if no other provider has been loaded yet. If another provider has already been loaded then it won't be loaded -automatically. Therefore if you want to use it in conjunction with other -providers then you must load it explicitly. +automatically. Therefore, if you want to use it in conjunction with other +providers, then you must load it explicitly. -This is a "built-in" provider which means that it is compiled and linked +This is a "built-in" provider, which means that it is compiled and linked into the libcrypto library and does not exist as a separate standalone module. The Legacy Provider @@ -58,7 +58,7 @@ The FIPS provider contains a sub-set of the algorithm implementations available from the default provider, consisting of algorithms conforming to FIPS standards. It is intended that this provider will be FIPS140-2 validated. -In some cases there may be minor behavioural differences between algorithm +In some cases, there may be minor behavioural differences between algorithm implementations in this provider compared to the equivalent algorithm in the default provider. This is typically in order to conform to FIPS standards. |