X-Git-Url: https://code.wpia.club/?a=blobdiff_plain;f=lib%2Fopenssl%2Fcrypto%2Fengine%2FREADME;h=41baa184c3ec77df4c91562be03731ff5a92cb75;hb=HEAD;hp=6b69b70f576a3bea61973f3f2d653be67e651ea4;hpb=156855b7e12c3a0254590da514b0d0e8efe469f4;p=cassiopeia.git

diff --git a/lib/openssl/crypto/engine/README b/lib/openssl/crypto/engine/README
index 6b69b70..41baa18 100644
--- a/lib/openssl/crypto/engine/README
+++ b/lib/openssl/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.