small cosmetics: align title with the other similar manual page

[openssl.git] / doc / ssleay.txt

diff --git a/doc/ssleay.txt b/doc/ssleay.txt
index 094e28ce48dc5e5be7d33fe2b1c352f2a70fc981..c75312911f96339753fc123ee90725d08106a9ad 100644 (file)
--- a/doc/ssleay.txt
+++ b/doc/ssleay.txt
@@ -1,6 +1,22 @@
 
 Bundle of old SSLeay documentation files [OBSOLETE!]
 
 
 Bundle of old SSLeay documentation files [OBSOLETE!]
 

+*** WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! ***
+
+OBSOLETE means that nothing in this document should be trusted.  This
+document is provided mostly for historical purposes (it wasn't even up
+to date at the time SSLeay 0.8.1 was released) and as inspiration.  If
+you copy some snippet of code from this document, please _check_ that
+it really is correct from all points of view.  For example, you can
+check with the other documents in this directory tree, or by comparing
+with relevant parts of the include files.
+
+People have done the mistake of trusting what's written here.  Please
+don't do that.
+
+*** WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! ***
+
+

 ==== readme ========================================================
 
 This is the old 0.6.6 docuementation.  Most of the cipher stuff is still
 ==== readme ========================================================
 
 This is the old 0.6.6 docuementation.  Most of the cipher stuff is still


@@ -4279,7 +4295,7 @@ X-Status:
 Loading client certs into MSIE 3.01
 ===================================
 
 Loading client certs into MSIE 3.01
 ===================================
 

-This document conatains all the information necessary to succesfully set up 
+This document contains all the information necessary to successfully set up 

 some scripts to issue client certs to Microsoft Internet Explorer. It 
 includes the required knowledge about the model MSIE uses for client 
 certification and includes complete sample scripts ready to play with. The 
 some scripts to issue client certs to Microsoft Internet Explorer. It 
 includes the required knowledge about the model MSIE uses for client 
 certification and includes complete sample scripts ready to play with. The 


@@ -5743,7 +5759,7 @@ strucutre but also the private key and certificate associated with
 
 EXAMPLES.
 
 
 EXAMPLES.
 

-So lets play at being a wierd SSL server.
+So lets play at being a weird SSL server.

 
 /* setup a context */
 ctx=SSL_CTX_new();
 
 /* setup a context */
 ctx=SSL_CTX_new();


@@ -6229,7 +6245,7 @@ SSL_get_app_data
 void SSL_CTX_set_default_verify
 
 /* This callback, if set, totaly overrides the normal SSLeay verification
 void SSL_CTX_set_default_verify
 
 /* This callback, if set, totaly overrides the normal SSLeay verification

- * functions and should return 1 on sucesss and 0 on failure */
+ * functions and should return 1 on success and 0 on failure */

 void SSL_CTX_set_cert_verify_callback
 
 /* The following are the same as the equivilent SSL_xxx functions.
 void SSL_CTX_set_cert_verify_callback
 
 /* The following are the same as the equivilent SSL_xxx functions.


@@ -6710,8 +6726,8 @@ CRYPTO_set_locking_callback(locking_function);
 before any multithreading is started.
 id_function does not need to be defined under Windows NT or 95, the
 correct function will be called if it is not.  Under unix, getpid()
 before any multithreading is started.
 id_function does not need to be defined under Windows NT or 95, the
 correct function will be called if it is not.  Under unix, getpid()

-is call if the id_callback is not defined, for solaris this is wrong
-(since threads id's are not pid's) but under IRIX it is correct
+is call if the id_callback is not defined, for Solaris this is wrong
+(since threads id's are not pid's) but under Linux it is correct

 (threads are just processes sharing the data segement).
 
 The locking_callback is used to perform locking by the SSLeay library.
 (threads are just processes sharing the data segement).
 
 The locking_callback is used to perform locking by the SSLeay library.