From 09389cbef5d50a9611a8dc3be416c80c9becd5eb Mon Sep 17 00:00:00 2001 From: =?utf8?q?Lutz=20J=C3=A4nicke?= Date: Mon, 1 Oct 2001 14:39:23 +0000 Subject: [PATCH] Typos (Chris Pepper ) --- INSTALL.MacOS | 8 ++++---- README.ENGINE | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/INSTALL.MacOS b/INSTALL.MacOS index a8c4f7f1da..43b5581cb3 100644 --- a/INSTALL.MacOS +++ b/INSTALL.MacOS @@ -1,7 +1,7 @@ -OpenSSL - Port To The Macintosh -=============================== +OpenSSL - Port To The Macintosh OS 9 or Earlier +=============================================== -Thanks to Roy Wood initial support for MacOS (pre +Thanks to Roy Wood initial support for Mac OS (pre X) is now provided. "Initial" means that unlike other platforms where you get an SDK and a "swiss army" openssl application, on Macintosh you only get one sample application which fetches a page over HTTPS(*) and dumps it @@ -42,7 +42,7 @@ Installation procedure: BSD sockets and some other POSIX APIs. The GUSI distribution is expected to be found in the same directory as openssl source tree, i.e. in the parent directory to the one where this very file, - namely INSTALL.MacOS. For more informations about GUSI, see + namely INSTALL.MacOS. For more information about GUSI, see http://www.iis.ee.ethz.ch/~neeri/macintosh/gusi-qa.html Finally some essential comments from our generous contributor:-) diff --git a/README.ENGINE b/README.ENGINE index 3d88ed152f..43e39d5b09 100644 --- a/README.ENGINE +++ b/README.ENGINE @@ -5,7 +5,7 @@ With OpenSSL 0.9.6, a new component has been added to support external crypto devices, for example accelerator cards. The component is called ENGINE, and has still a pretty experimental status and almost no - documentation. It's designed to be faily easily extensible by the + documentation. It's designed to be fairly easily extensible by the calling programs. There's currently built-in support for the following crypto devices: @@ -48,7 +48,7 @@ No external crypto device is chosen unless you say so. You have actively tell the openssl utility commands to use it through a new command line switch called "-engine". And if you want to use the ENGINE library to - do something similar, you must also explicitely choose an external crypto + do something similar, you must also explicitly choose an external crypto device, or the built-in crypto routines will be used, just as in the default OpenSSL distribution. @@ -56,7 +56,7 @@ PROBLEMS ======== - It seems like the ENGINE part doesn't work too well with Cryptoswift on + It seems like the ENGINE part doesn't work too well with CryptoSwift on Win32. A quick test done right before the release showed that trying "openssl speed -engine cswift" generated errors. If the DSO gets enabled, an attempt is made to write at memory address 0x00000002. -- 2.25.1