Replace "a RSA" with "an RSA"

Fixes openssl#19771

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/19787)

diff --git a/CHANGES.md b/CHANGES.md
index d22780d05b782a9bec36d0a3731cbe959b48a973..7e98b0362a402c9547723f889df3415f68fd1417 100644 (file)
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -19468,7 +19468,7 @@ ndif
    *Ralf S. Engelschall*
 
  * Incorporated the popular no-RSA/DSA-only patches
-   which allow to compile a RSA-free SSLeay.
+   which allow to compile an RSA-free SSLeay.
 
    *Andrew Cooke / Interrader Ldt., Ralf S. Engelschall*
 

diff --git a/crypto/rsa/rsa_mp.c b/crypto/rsa/rsa_mp.c
index 45e22809446f32da2daa124072702d3b80931d18..cb2fb7d1e8e91b19d743ee6a66c8968ccd8cf1d3 100644 (file)
--- a/crypto/rsa/rsa_mp.c
+++ b/crypto/rsa/rsa_mp.c
@@ -21,7 +21,7 @@ void ossl_rsa_multip_info_free_ex(RSA_PRIME_INFO *pinfo)
 
 void ossl_rsa_multip_info_free(RSA_PRIME_INFO *pinfo)
 {
-    /* free a RSA_PRIME_INFO structure */
+    /* free an RSA_PRIME_INFO structure */
     BN_clear_free(pinfo->r);
     BN_clear_free(pinfo->d);
     BN_clear_free(pinfo->t);
@@ -32,7 +32,7 @@ RSA_PRIME_INFO *ossl_rsa_multip_info_new(void)
 {
     RSA_PRIME_INFO *pinfo;
 
-    /* create a RSA_PRIME_INFO structure */
+    /* create an RSA_PRIME_INFO structure */
     if ((pinfo = OPENSSL_zalloc(sizeof(RSA_PRIME_INFO))) == NULL)
         return NULL;
     if ((pinfo->r = BN_secure_new()) == NULL)

diff --git a/demos/encode/rsa_encode.c b/demos/encode/rsa_encode.c
index d8d65ddae8c0178f8cb3bf37866cf493737affd8..2bf6d13e6ff504f7eb1b63675b9e1327b9a29f4a 100644 (file)
--- a/demos/encode/rsa_encode.c
+++ b/demos/encode/rsa_encode.c
@@ -93,7 +93,7 @@ cleanup:
 }
 
 /*
- * Store a RSA public or private key to a file using PEM encoding.
+ * Store an RSA public or private key to a file using PEM encoding.
  *
  * If a passphrase is supplied, the file is encrypted, otherwise
  * it is unencrypted.

diff --git a/doc/HOWTO/certificates.txt b/doc/HOWTO/certificates.txt
index cfd2bdabb130c7ed2816621051ab33b20fb2495f..78ab97b4192800d7a0b9aa89f7b77817abf81d58 100644 (file)
--- a/doc/HOWTO/certificates.txt
+++ b/doc/HOWTO/certificates.txt
@@ -30,7 +30,7 @@ keys, so before you create a certificate or a certificate request, you
 need to create a private key.
 
 Private keys are generated with 'openssl genrsa -out privkey.pem' if
-you want a RSA private key, or if you want a DSA private key:
+you want an RSA private key, or if you want a DSA private key:
 'openssl dsaparam -out dsaparam.pem 2048; openssl gendsa -out privkey.pem dsaparam.pem'.
 
 The private keys created by these commands are not passphrase protected;

diff --git a/doc/HOWTO/keys.txt b/doc/HOWTO/keys.txt
index 9f0967cf55778ac847c1eef98a486576c3918be5..c4a74c54fcb8c1af54a8e880e8e3be225e851872 100644 (file)
--- a/doc/HOWTO/keys.txt
+++ b/doc/HOWTO/keys.txt
@@ -14,9 +14,9 @@ algorithms.  The most popular ones associated with certificates are
 RSA and DSA, and this HOWTO will show how to generate each of them.
 
 
-2. To generate a RSA key
+2. To generate an RSA key
 
-A RSA key can be used both for encryption and for signing.
+An RSA key can be used both for encryption and for signing.
 
 Generating a key for the RSA algorithm is quite easy, all you have to
 do is the following:

diff --git a/doc/man3/SSL_CTX_set_cipher_list.pod b/doc/man3/SSL_CTX_set_cipher_list.pod
index 29e4a424f7213d25392b62b628f65b36d1519034..71f399400c2a1276879a6a1958db037c3aacbbcd 100644 (file)
--- a/doc/man3/SSL_CTX_set_cipher_list.pod
+++ b/doc/man3/SSL_CTX_set_cipher_list.pod
@@ -80,7 +80,7 @@ additional restrictions apply. All ciphers have additional requirements.
 ADH ciphers don't need a certificate, but DH-parameters must have been set.
 All other ciphers need a corresponding certificate and key.
 
-A RSA cipher can only be chosen, when a RSA certificate is available.
+An RSA cipher can only be chosen, when an RSA certificate is available.
 RSA ciphers using DHE need a certificate and key and additional DH-parameters
 (see L<SSL_CTX_set_tmp_dh_callback(3)>).
 

diff --git a/doc/man3/SSL_CTX_use_certificate.pod b/doc/man3/SSL_CTX_use_certificate.pod
index 9af0b461024514f00c376dededfd3585ea21f465..0d9ba740426e991b1ff8bd2eb84723fb5992d912 100644 (file)
--- a/doc/man3/SSL_CTX_use_certificate.pod
+++ b/doc/man3/SSL_CTX_use_certificate.pod
@@ -130,7 +130,7 @@ RSA key found to B<ssl>.
 SSL_CTX_check_private_key() checks the consistency of a private key with
 the corresponding certificate loaded into B<ctx>. If more than one
 key/certificate pair (RSA/DSA) is installed, the last item installed will
-be checked. If e.g. the last item was a RSA certificate or key, the RSA
+be checked. If e.g. the last item was an RSA certificate or key, the RSA
 key/certificate pair will be checked. SSL_check_private_key() performs
 the same check for B<ssl>. If no key/certificate was explicitly added for
 this B<ssl>, the last item added into B<ctx> will be checked.

diff --git a/doc/man3/SSL_CTX_use_serverinfo.pod b/doc/man3/SSL_CTX_use_serverinfo.pod
index ece8744d552e4b7233062108da05bb80a6467193..ebdb5c6f7ca13064cb40550258ae943abb1548bf 100644 (file)
--- a/doc/man3/SSL_CTX_use_serverinfo.pod
+++ b/doc/man3/SSL_CTX_use_serverinfo.pod
@@ -59,7 +59,7 @@ SSL_SERVERINFOV2 data or "BEGIN SERVERINFO FOR " for SSL_SERVERINFOV1 data.
 
 If more than one certificate (RSA/DSA) is installed using
 SSL_CTX_use_certificate(), the serverinfo extension will be loaded into the
-last certificate installed.  If e.g. the last item was a RSA certificate, the
+last certificate installed.  If e.g. the last item was an RSA certificate, the
 loaded serverinfo extension data will be loaded for that certificate.  To
 use the serverinfo extension for multiple certificates,
 SSL_CTX_use_serverinfo() needs to be called multiple times, once B<after>

diff --git a/test/keymgmt_internal_test.c b/test/keymgmt_internal_test.c
index 0f2030e61fb729cf051dc5954badc823e2426a25..d553738b3291cf0265b70e8495d9bd920f9b4e26 100644 (file)
--- a/test/keymgmt_internal_test.c
+++ b/test/keymgmt_internal_test.c
@@ -227,7 +227,7 @@ static int test_pass_rsa(FIXTURE *fixture)
     while (dup_pk == NULL) {
         ret = 0;
         km = km3;
-        /* Check that we can't export an RSA key into a RSA-PSS keymanager */
+        /* Check that we can't export an RSA key into an RSA-PSS keymanager */
         if (!TEST_ptr_null(provkey2 = evp_pkey_export_to_provider(pk, NULL,
                                                                   &km,
                                                                   NULL)))

diff --git a/test/sslapitest.c b/test/sslapitest.c
index a26f6286f301fed7efedeb92293bafb9be96109b..074a9575760ac104d9a54cf445eb2d1747d9320b 100644 (file)
--- a/test/sslapitest.c
+++ b/test/sslapitest.c
@@ -401,7 +401,7 @@ static int test_keylog(void)
      * Now we want to test that our output data was vaguely sensible. We
      * do that by using strtok and confirming that we have more or less the
      * data we expect. For both client and server, we expect to see one master
-     * secret. The client should also see a RSA key exchange.
+     * secret. The client should also see an RSA key exchange.
      */
     expected.rsa_key_exchange_count = 1;
     expected.master_secret_count = 1;