summaryrefslogtreecommitdiffstats
path: root/doc/man7/evp.pod
diff options
context:
space:
mode:
authorGustaf Neumann <neumann@wu-wien.ac.at>2020-06-29 21:13:07 +0200
committerDr. Matthias St. Pierre <matthias.st.pierre@ncp-e.com>2020-07-05 01:49:20 +0200
commit8c1cbc72105ffd493b48e65f8f5fd3657dedb28c (patch)
treeb1437e0210f80d7de45d8d33903a2f28fe1b82da /doc/man7/evp.pod
parent3a19f1a9dd16f5855a7e2a42cd3e7f136f849bd3 (diff)
Fix typos and repeated words
CLA: trivial Reviewed-by: Shane Lontis <shane.lontis@oracle.com> Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com> (Merged from https://github.com/openssl/openssl/pull/12320)
Diffstat (limited to 'doc/man7/evp.pod')
-rw-r--r--doc/man7/evp.pod12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/man7/evp.pod b/doc/man7/evp.pod
index 3e810f3d3f..2a3a1a91dc 100644
--- a/doc/man7/evp.pod
+++ b/doc/man7/evp.pod
@@ -25,7 +25,7 @@ functions.
Symmetric encryption is available with the L<B<EVP_Encrypt>I<XXX>|EVP_EncryptInit(3)>
functions. The L<B<EVP_Digest>I<XXX>|EVP_DigestInit(3)> functions provide message digests.
-The B<EVP_PKEY>I<XXX> functions provide a high level interface to
+The B<EVP_PKEY>I<XXX> functions provide a high-level interface to
asymmetric algorithms. To create a new EVP_PKEY see
L<EVP_PKEY_new(3)>. EVP_PKEYs can be associated
with a private key of a particular algorithm by using the functions
@@ -43,7 +43,7 @@ The EVP_PKEY functions support the full range of asymmetric algorithm operations
=item For signing and verifying see L<EVP_PKEY_sign(3)>,
L<EVP_PKEY_verify(3)> and L<EVP_PKEY_verify_recover(3)>.
However, note that
-these functions do not perform a digest of the data to be signed. Therefore
+these functions do not perform a digest of the data to be signed. Therefore,
normally you would use the L<EVP_DigestSignInit(3)>
functions for this purpose.
@@ -72,12 +72,12 @@ as defaults, then the various EVP functions will automatically use those
implementations automatically in preference to built in software
implementations. For more information, consult the engine(3) man page.
-Although low level algorithm specific functions exist for many algorithms
+Although low-level algorithm specific functions exist for many algorithms
their use is discouraged. They cannot be used with an ENGINE and ENGINE
-versions of new algorithms cannot be accessed using the low level functions.
+versions of new algorithms cannot be accessed using the low-level functions.
Also makes code harder to adapt to new algorithms and some options are not
-cleanly supported at the low level and some operations are more efficient
-using the high level interface.
+cleanly supported at the low-level and some operations are more efficient
+using the high-level interface.
=head1 SEE ALSO