correct spelling errors detected by Debian lintian

CLA: trivial

Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5801)

diff --git a/CHANGES b/CHANGES
index 00b5c4060fdf7dc96bcb091d6e6805eda05fdae9..a13183f9e8f59704da5d88c58b1f1a88fc74eb5b 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -65,7 +65,7 @@
      below. Similarly TLSv1.2 ciphersuites are not compatible with TLSv1.3.
      In order to avoid issues where legacy TLSv1.2 ciphersuite configuration
      would otherwise inadvertently disable all TLSv1.3 ciphersuites the
-     configuraton has been separated out. See the ciphers man page or the
+     configuration has been separated out. See the ciphers man page or the
      SSL_CTX_set_ciphersuites() man page for more information.
      [Matt Caswell]
 

diff --git a/apps/req.c b/apps/req.c
index 4ab636eb7af655e307c3f2132fdf3775cac096c1..ca4b7ec891f5dd4941c29b5826fa06140e892d34 100644 (file)
--- a/apps/req.c
+++ b/apps/req.c
@@ -370,7 +370,7 @@ int req_main(int argc, char **argv)
     if (addext_bio) {
         if (verbose)
             BIO_printf(bio_err,
-                       "Using additional configuraton from command line\n");
+                       "Using additional configuration from command line\n");
         addext_conf = app_load_config_bio(addext_bio, NULL);
     }
     if (template != default_config_file && !app_load_modules(req_conf))

diff --git a/doc/man3/OPENSSL_fork_prepare.pod b/doc/man3/OPENSSL_fork_prepare.pod
index eda83603b1bb9b83b9732748f046b3f06304f8f2..7c4eb1dbfd9f5fec864148bcc7b9c1213b3e23ef 100644 (file)
--- a/doc/man3/OPENSSL_fork_prepare.pod
+++ b/doc/man3/OPENSSL_fork_prepare.pod
@@ -30,7 +30,7 @@ such as Linux that have both functions will normally not need to call these
 functions as the OpenSSL library will do so automatically.
 
 L<OPENSSL_init_crypto(3)> will register these functions with the appropriate
-hander, when the B<OPENSSL_INIT_ATFORK> flag is used. For other
+handler, when the B<OPENSSL_INIT_ATFORK> flag is used. For other
 applications, these functions can be called directly. They should be used
 according to the calling sequence described by the pthreads_atfork(3)
 documentation, which is summarized here.  OPENSSL_fork_prepare() should

diff --git a/doc/man3/SSL_CTX_set_session_ticket_cb.pod b/doc/man3/SSL_CTX_set_session_ticket_cb.pod
index d0df021d511061588eccd598032734e1762ff461..c7b51dd16b85404633be7e88c3a8391347629ec9 100644 (file)
--- a/doc/man3/SSL_CTX_set_session_ticket_cb.pod
+++ b/doc/man3/SSL_CTX_set_session_ticket_cb.pod
@@ -42,7 +42,7 @@ B<dec_cb> is the application defined callback invoked after session ticket
 decryption has been attempted and any session ticket application data is available.
 The application can call SSL_SESSION_get_ticket_appdata() at this time to retrieve
 the application data. The value of B<arg> is the same as that given to
-SSL_CTX_set_session_ticket_cb(). The B<retv> arguement is the result of the ticket
+SSL_CTX_set_session_ticket_cb(). The B<retv> argument is the result of the ticket
 decryption. The B<keyname> and B<keyname_len> identify the key used to decrypt the
 session ticket. The B<dec_cb> callback is defined as type
 B<SSL_CTX_decrypt_session_ticket_fn>.

diff --git a/doc/man3/SSL_CTX_use_certificate.pod b/doc/man3/SSL_CTX_use_certificate.pod
index c553bf1bee1ef482d7126669fa7bc172139dcad3..4dff79cee22c290cf61f19c09e59614899215750 100644 (file)
--- a/doc/man3/SSL_CTX_use_certificate.pod
+++ b/doc/man3/SSL_CTX_use_certificate.pod
@@ -106,7 +106,7 @@ B<x>, B<pkey> and B<chain> are set only if all were not previously set.
 If B<override> is non-0, then the certificate, private key and chain certs
 are always set. If B<pkey> is NULL, then the public key of B<x> is used as
 the private key. This is intended to be used with hardware (via the ENGINE
-inteface) that stores the private key securely, such that it cannot be
+interface) that stores the private key securely, such that it cannot be
 accessed by OpenSSL. The reference count of the public key is incremented
 (twice if there is no private key); it is not copied nor duplicated. This
 allows all private key validations checks to succeed without an actual