From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Date: Mon, 4 Mar 2002 17:16:46 +0000 (+0000)
Subject: updated
X-Git-Tag: gnutls_0_3_92~55
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0d92a39ffa2f99088ea3dbd7837cc4422b7a1e11;p=thirdparty%2Fgnutls.git

updated
---

diff --git a/doc/tex/errors.tex b/doc/tex/errors.tex
index dbc6758308..ef9f24c7ff 100644
--- a/doc/tex/errors.tex
+++ b/doc/tex/errors.tex
@@ -8,7 +8,7 @@ or not.
 \par 
 Fatal errors terminate the connection immediately and
 further sends ard receives will be disallowed. An example of
-a fatal error code is GNUTLS\_E\_MAC\_FAILED. Non-fatal errors
+a fatal error code is GNUTLS\_E\_DECRYPTION\_FAILED. Non-fatal errors
 may warn about something (ie a warning alert was received), or
 indicate the some action has to be taken. This is the case with
 the error code GNUTLS\_E\_REHANDSHAKE returned by 
@@ -18,7 +18,7 @@ may ignore this request, or may reply with an alert.
 You can test if an error code is a fatal one by using the
 \hyperref{gnutls\_error\_is\_fatal()}{gnutls\_error\_is\_fatal() (see Section }{)}{gnutls_error_is_fatal}.
 \par
-If any non fatal errors, that require reaction, are to be returned by a
+If any non fatal errors, that require an action, are to be returned by a
 function, these error codes will be documented
 in the function's reference.
 
diff --git a/lib/gnutls.h.in.in b/lib/gnutls.h.in.in
index e0d4e5fe1f..89d58233c6 100644
--- a/lib/gnutls.h.in.in
+++ b/lib/gnutls.h.in.in
@@ -101,6 +101,7 @@ typedef struct {
 int gnutls_init(GNUTLS_STATE * state, GNUTLS_ConnectionEnd con_end);
 void gnutls_deinit(GNUTLS_STATE state);
 int gnutls_bye( GNUTLS_STATE state, GNUTLS_CloseRequest how);
+#define gnutls_close gnutls_bye
 
 int gnutls_handshake( GNUTLS_STATE state);
 int gnutls_rehandshake( GNUTLS_STATE state);