Typo fix

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Paul Dale <ppzgs1@gmail.com>
(Merged from https://github.com/openssl/openssl/pull/26813)

diff --git a/doc/man3/SSL_CONF_cmd.pod b/doc/man3/SSL_CONF_cmd.pod
index ed4c2c083c724caabe817625461245ad94555f9d..acc8808cca6c84507e671fb80edb8d50c3361a53 100644 (file)
--- a/doc/man3/SSL_CONF_cmd.pod
+++ b/doc/man3/SSL_CONF_cmd.pod
@@ -127,7 +127,7 @@ in TLSv1.3, specified using the IETF name, e.g., B<ecdsa_secp256r1_sha256>,
 B<ed25519>, or B<rsa_pss_pss_sha256>. Additional providers may make available
 further algorithms via the TLS-SIGALG capability.
 Signature scheme names and public key algorithm names (but not the hash names)
-in the B<algoirithm+hash> form are case-insensitive.
+in the B<algorithm+hash> form are case-insensitive.
 See L<provider-base(7)>.
 
 If this option is not set then all signature algorithms supported by all
@@ -421,7 +421,7 @@ B<signature_scheme> is one of the signature schemes defined in TLSv1.3,
 specified using the IANA name, e.g., B<ecdsa_secp256r1_sha256>, B<ed25519>,
 or B<rsa_pss_pss_sha256>.
 Signature scheme names and public key algorithm names (but not the hash names)
-in the B<algoirithm+hash> form are case-insensitive.
+in the B<algorithm+hash> form are case-insensitive.
 Additional providers may make available further signature schemes via the
 TLS_SIGALG capability. See L<provider-base(7)/CAPABILITIES>.
 

diff --git a/doc/man3/SSL_CTX_set1_sigalgs.pod b/doc/man3/SSL_CTX_set1_sigalgs.pod
index e6380aac2b99b84ff3860317e50b33a7c34dee84..895556bdc5790050a7bfd78fb9f1b10073469e71 100644 (file)
--- a/doc/man3/SSL_CTX_set1_sigalgs.pod
+++ b/doc/man3/SSL_CTX_set1_sigalgs.pod
@@ -35,7 +35,7 @@ elements, where each element is either a combination of a public key
 algorithm and a digest separated by B<+>, or a TLS 1.3-style named
 SignatureScheme such as rsa_pss_pss_sha256.
 Signature scheme names and public key algorithm names (but not the digest
-names) in the B<algoirithm+hash> form are case-insensitive.
+names) in the B<algorithm+hash> form are case-insensitive.
 If a list entry is preceded with the C<?> character, it will be ignored if an
 implementation is missing.