6 files changed, 14 insertions, 14 deletions

diff --git a/src/lib/libcrypto/engine/README b/src/lib/libcrypto/engine/README
index 6b69b70f57..bc4a9041ff 100644
--- a/src/lib/libcrypto/engine/README
+++ b/src/lib/libcrypto/engine/README
@@ -122,7 +122,7 @@ use by EVP_MD code. Ditto for tb_rsa.c, tb_dsa.c, etc. These instantiations of
 ENGINE_TABLE essentially provide linker-separation of the classes so that even
 if ENGINEs implement *all* possible algorithms, an application using only
 EVP_CIPHER code will link at most code relating to EVP_CIPHER, tb_cipher.c, core
-ENGINE code that is independant of class, and of course the ENGINE
+ENGINE code that is independent of class, and of course the ENGINE
 implementation that the application loaded. It will *not* however link any
 class-specific ENGINE code for digests, RSA, etc nor will it bleed over into
 other APIs, such as the RSA/DSA/etc library code.
@@ -188,7 +188,7 @@ state will be unchanged. Thus, no cleanup is required unless registration takes
 place. ENGINE_cleanup() will simply iterate across a list of registered cleanup
 callbacks calling each in turn, and will then internally delete its own storage
 (a STACK). When a cleanup callback is next registered (eg. if the cleanup() is
-part of a gracefull restart and the application wants to cleanup all state then
+part of a graceful restart and the application wants to cleanup all state then
 start again), the internal STACK storage will be freshly allocated. This is much
 the same as the situation in the ENGINE_TABLE instantiations ... NULL is the
 initialised state, so only modification operations (not queries) will cause that
diff --git a/src/lib/libcrypto/engine/eng_aesni.c b/src/lib/libcrypto/engine/eng_aesni.c
index 586f74792a..cce4203bc4 100644
--- a/src/lib/libcrypto/engine/eng_aesni.c
+++ b/src/lib/libcrypto/engine/eng_aesni.c
@@ -1,6 +1,6 @@
-/* $OpenBSD: eng_aesni.c,v 1.11 2018/04/14 07:18:37 tb Exp $ */
+/* $OpenBSD: eng_aesni.c,v 1.12 2022/12/26 07:18:51 jmc Exp $ */
 /*
- * Support for Intel AES-NI intruction set
+ * Support for Intel AES-NI instruction set
  *   Author: Huang Ying <ying.huang@intel.com>
  *
  * Intel AES-NI is a new set of Single Instruction Multiple Data
diff --git a/src/lib/libcrypto/engine/eng_list.c b/src/lib/libcrypto/engine/eng_list.c
index b29b4102e4..451c8616ef 100644
--- a/src/lib/libcrypto/engine/eng_list.c
+++ b/src/lib/libcrypto/engine/eng_list.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: eng_list.c,v 1.24 2019/01/19 01:07:00 tb Exp $ */
+/* $OpenBSD: eng_list.c,v 1.25 2022/12/26 07:18:51 jmc Exp $ */
 /* Written by Geoff Thorpe (geoff@geoffthorpe.net) for the OpenSSL
  * project 2000.
  */
@@ -223,7 +223,7 @@ ENGINE_get_next(ENGINE *e)
         CRYPTO_w_lock(CRYPTO_LOCK_ENGINE);
         ret = e->next;
         if (ret) {
-                /* Return a valid structural refernce to the next ENGINE */
+                /* Return a valid structural reference to the next ENGINE */
                 ret->struct_ref++;
                 engine_ref_debug(ret, 0, 1)
         }
diff --git a/src/lib/libcrypto/engine/eng_padlock.c b/src/lib/libcrypto/engine/eng_padlock.c
index 0281ab810c..50b5fb780d 100644
--- a/src/lib/libcrypto/engine/eng_padlock.c
+++ b/src/lib/libcrypto/engine/eng_padlock.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: eng_padlock.c,v 1.16 2018/04/14 07:18:37 tb Exp $ */
+/* $OpenBSD: eng_padlock.c,v 1.17 2022/12/26 07:18:51 jmc Exp $ */
 /*
  * Support for VIA PadLock Advanced Cryptography Engine (ACE)
  * Written by Michal Ludvig <michal@logix.cz>
@@ -285,7 +285,7 @@ struct padlock_cipher_data {
  * Essentially this variable belongs in thread local storage.
  * Having this variable global on the other hand can only cause
  * few bogus key reloads [if any at all on single-CPU system],
- * so we accept the penatly...
+ * so we accept the penalty...
  */
 static volatile struct padlock_cipher_data *padlock_saved_context;
 #endif
@@ -872,7 +872,7 @@ padlock_aes_cipher(EVP_CIPHER_CTX *ctx, unsigned char *out_arg,
                 chunk = PADLOCK_CHUNK;
 
         if (out_misaligned) {
-                /* optmize for small input */
+                /* optimize for small input */
                 allocated = (chunk < nbytes ? PADLOCK_CHUNK : nbytes);
                 out = alloca(0x10 + allocated);
                 out = NEAREST_ALIGNED(out);
diff --git a/src/lib/libcrypto/engine/eng_table.c b/src/lib/libcrypto/engine/eng_table.c
index a8aded5aaf..0e7ea3b698 100644
--- a/src/lib/libcrypto/engine/eng_table.c
+++ b/src/lib/libcrypto/engine/eng_table.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: eng_table.c,v 1.9 2017/01/29 17:49:23 beck Exp $ */
+/* $OpenBSD: eng_table.c,v 1.10 2022/12/26 07:18:52 jmc Exp $ */
 /* ====================================================================
  * Copyright (c) 2001 The OpenSSL Project.  All rights reserved.
  *
@@ -163,7 +163,7 @@ engine_table_register(ENGINE_TABLE **table, ENGINE_CLEANUP_CB *cleanup,
                         fnd->funct = NULL;
                         (void)lh_ENGINE_PILE_insert(&(*table)->piles, fnd);
                 }
-                /* A registration shouldn't add duplciate entries */
+                /* A registration shouldn't add duplicate entries */
                 (void)sk_ENGINE_delete_ptr(fnd->sk, e);
                 /* if 'setdefault', this ENGINE goes to the head of the list */
                 if (!sk_ENGINE_push(fnd->sk, e))
@@ -193,7 +193,7 @@ int_unregister_cb_doall_arg(ENGINE_PILE *pile, ENGINE *e)
 {
         int n;
 
-        /* Iterate the 'c->sk' stack removing any occurance of 'e' */
+        /* Iterate the 'c->sk' stack removing any occurrence of 'e' */
         while ((n = sk_ENGINE_find(pile->sk, e)) >= 0) {
                 (void)sk_ENGINE_delete(pile->sk, n);
                 pile->uptodate = 0;
diff --git a/src/lib/libcrypto/engine/engine.h b/src/lib/libcrypto/engine/engine.h
index 5c21647fe3..41f05d48af 100644
--- a/src/lib/libcrypto/engine/engine.h
+++ b/src/lib/libcrypto/engine/engine.h
@@ -1,4 +1,4 @@
-/* $OpenBSD: engine.h,v 1.34 2022/07/12 14:42:49 kn Exp $ */
+/* $OpenBSD: engine.h,v 1.35 2022/12/26 07:18:52 jmc Exp $ */
 /* Written by Geoff Thorpe (geoff@geoffthorpe.net) for the OpenSSL
  * project 2000.
  */
@@ -631,7 +631,7 @@ typedef struct st_dynamic_MEM_fns {
         dyn_MEM_free_cb                         free_cb;
 } dynamic_MEM_fns;
 /* FIXME: Perhaps the memory and locking code (crypto.h) should declare and use
- * these types so we (and any other dependant code) can simplify a bit?? */
+ * these types so we (and any other dependent code) can simplify a bit?? */
 typedef void (*dyn_lock_locking_cb)(int, int, const char *, int);
 typedef int (*dyn_lock_add_lock_cb)(int*, int, int, const char *, int);
 typedef struct CRYPTO_dynlock_value *(*dyn_dynlock_create_cb)(