diff options
| author | Veres Lajos <vlajos@gmail.com> | 2013-06-13 00:22:32 +0100 |
|---|---|---|
| committer | Ben Laurie <ben@links.org> | 2013-09-05 21:39:42 +0100 |
| commit | 478b50cf67d6a91fdcd584cff57c58b7e863055d (patch) | |
| tree | 2503e85a768e8bde5edace29c80222b47ea1f0ea /crypto/engine | |
| parent | d2625fd65772ce3de2563e648decd2d1074fd873 (diff) | |
misspellings fixes by https://github.com/vlajos/misspell_fixer
Diffstat (limited to 'crypto/engine')
| -rw-r--r-- | crypto/engine/README | 2 | ||||
| -rw-r--r-- | crypto/engine/eng_table.c | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/crypto/engine/README b/crypto/engine/README index 6b69b70f57..41baa184c3 100644 --- a/crypto/engine/README +++ b/crypto/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. diff --git a/crypto/engine/eng_table.c b/crypto/engine/eng_table.c index 4fde948185..93dc90ec3c 100644 --- a/crypto/engine/eng_table.c +++ b/crypto/engine/eng_table.c @@ -189,7 +189,7 @@ end: static void 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); |