Fix security hole.

[openssl.git] / INSTALL.W32

diff --git a/INSTALL.W32 b/INSTALL.W32
index 8aa40023c50ada65b90f738e92097172484ee09c..61b563c089824d1d155ca9fac4eb8c522d431b27 100644 (file)
--- a/INSTALL.W32
+++ b/INSTALL.W32
@@ -31,9 +31,8 @@ then from the VC++ environment at a prompt do:
 
 nmake -f ms\ntdll.mak
 
-you may get a warning about too many rules but if all is well it should all
-compile and you will have some DLLs and executables in out32dll. If you want
-to try the tests then cd to out32dll and run ..\ms\test
+If all is well it should compile and you will have some DLLs and executables
+in out32dll. If you want to try the tests then cd to out32dll and run ..\ms\test
 
 Troubleshooting.
 
@@ -48,7 +47,7 @@ perl util\mkdef.pl crypto ssl update
 
 then ms\do_ms should not give a warning any more. However the numbers that get
 assigned by this technique may not match those that eventually get assigned
-in the CVS tree: so you anything linked against this version of the library
+in the CVS tree: so anything linked against this version of the library
 may need to be recompiled.
 
 If you get errors about unresolved externals then this means that either you
@@ -86,8 +85,7 @@ to make a debugging version of the library.
 
 If you want to enable the NT specific features of OpenSSL (currently only
 the logging BIO) follow the instructions above but call the batch file
-do_nt.bat instead of do_ms.bat. If you do this then you will no longer be able
-to run the OpenSSL binaries under Windows 95 or 98.
+do_nt.bat instead of do_ms.bat.
 
 You can also build a static version of the library using the Makefile ms\nt.mak