X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=crypto%2Fengine%2FREADME;h=41baa184c3ec77df4c91562be03731ff5a92cb75;hb=fda29b6db038716e4409068798646c6db042e552;hp=6b69b70f576a3bea61973f3f2d653be67e651ea4;hpb=f185e725a00a76cee0bcd0a3beb92a257d2b6325;p=oweals%2Fopenssl.git

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.