Fixed typos in ossl_ht_new.pod, EVP_PKEY_decrypt.pod, and RSA_public_encrypt.pod

CLA: trivial

Reviewed-by: Paul Dale <ppzgs1@gmail.com>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/24304)
This commit is contained in:
sapph2c 2024-04-29 20:26:54 -04:00 committed by Tomas Mraz
parent ee28152e86
commit f4601b6de7
3 changed files with 5 additions and 5 deletions

View File

@ -151,7 +151,7 @@ ossl_ht_put() on the B<HT_VALUE> to prevent memory leaks.
=item *
ossl_ht_get() preforms a lookup of an B<HT_KEY> in the hashtable, returning
ossl_ht_get() performs a lookup of an B<HT_KEY> in the hashtable, returning
its corresponding value.
=item *
@ -199,12 +199,12 @@ given value.
=item *
HT_SET_KEY_STRING() Preforms a strncpy() of a source string to the destination
HT_SET_KEY_STRING() Performs a strncpy() of a source string to the destination
key field.
=item *
HT_SET_KEY_BLOB() Preforms a memcpy() of a source uint8_t buffer to a
HT_SET_KEY_BLOB() Performs a memcpy() of a source uint8_t buffer to a
destination key field.
=item *

View File

@ -68,7 +68,7 @@ of side-channel secure code from applications using OpenSSL.
If OpenSSL is configured to use a provider that doesn't implement implicit
rejection, the code still needs to handle the returned values
using side-channel free code.
Side-channel free handling of the error stack can be peformed using
Side-channel free handling of the error stack can be performed using
either a pair of unconditional L<ERR_set_mark(3)> and L<ERR_pop_to_mark(3)>
calls or by using the L<ERR_clear_error(3)> call.

View File

@ -102,7 +102,7 @@ a side-channel secure error handling.
Applications that want to be secure against side-channel attacks with
providers that don't implement implicit rejection, still need to
handle the returned values using side-channel free code.
Side-channel free handling of the error stack can be peformed using
Side-channel free handling of the error stack can be performed using
either a pair of unconditional L<ERR_set_mark(3)> and L<ERR_pop_to_mark(3)>
calls or by using the L<ERR_clear_error(3)> call.