Corrected the return values of gnutls_x509_crt_check_hostname().

4 files changed, 7 insertions, 8 deletions

diff --git a/doc/tex/alert.tex b/doc/tex/alert.tex
index 3c1f13df27..58ae1727c1 100644
--- a/doc/tex/alert.tex
+++ b/doc/tex/alert.tex
@@ -14,8 +14,8 @@ and prevent future renegotiations using the current session ID.
 
 \par The alert messages are protected by the record protocol, thus
 the information that is included does not leak. You must take
-extreme care for the alert information not to leak to a possible attacker
-(via public log files etc).
+extreme care for the alert information not to leak to a possible attacker, 
+via public log files etc.
 
 \par
 \begin{itemize}
@@ -26,5 +26,5 @@ to map a gnutls error number to an alert signal.
 \item \printfunc{gnutls_alert_get}{gnutls\_alert\_get}:
 returns the last received alert.
 \item \printfunc{gnutls_alert_get_name}{gnutls\_alert\_get\_name}:
-returns the name (in a character array) of the given alert.
+returns the name, in a character array, of the given alert.
 \end{itemize}
diff --git a/doc/tex/ciphers.tex b/doc/tex/ciphers.tex
index a1d9c30950..bf297e32ac 100644
--- a/doc/tex/ciphers.tex
+++ b/doc/tex/ciphers.tex
@@ -6,7 +6,7 @@ Encryption Standard is actually the RIJNDAEL algorithm. This is the
 algorithm that replaced DES.}}, or
 stream algorithms like {\bf ARCFOUR\_128\footnote{ARCFOUR\_128 is a compatible
 algorithm with RSA's RC4 algorithm, which is considered to be a trade secret.}} See \hyperref{fig:ciphers}{figure }{}{fig:ciphers} for a complete list. 
-Ciphers are encryption algorithms that use a single (secret) key
+Ciphers are encryption algorithms that use a single, secret, key
 to encrypt and decrypt data. Block algorithms in TLS also provide protection
 against statistical analysis of the data. \gnutls{} makes use of this property
 thus, if you're using the \tlsI{} protocol, a random number of blocks will be
diff --git a/doc/tex/howto.tex b/doc/tex/howto.tex
index 19997ace22..365d64cdf1 100644
--- a/doc/tex/howto.tex
+++ b/doc/tex/howto.tex
@@ -26,8 +26,7 @@ That way the \tls{} protocol does not know anything
 about the client, and popular methods like the host advertising in 
 HTTP do not work. There is no way for the client to say ``I connected
 to YYY server'' before the Handshake starts, so the server cannot
-possibly know which certificate to use\footnote{There is some effort to solve
-this problem within \tls{}}.
+possibly know which certificate to use.
 
 \par
 Other than that it requires two separate ports to run a single service, which is 
@@ -117,7 +116,7 @@ CLIENT: BYE
 \par
 This method, if implemented properly, is far better than the
 traditional method, and the security properties remain the same, since only
-denial of service is possible. The benefit is the server may request
+denial of service is possible. The benefit is that the server may request
 additional data before the \tls{} Handshake protocol
 starts, in order to send the correct certificate, use the correct
 password file\footnote{in SRP authentication}, or anything else!
diff --git a/doc/tex/srp.tex b/doc/tex/srp.tex
index f1e15a85ee..e7cbb59b09 100644
--- a/doc/tex/srp.tex
+++ b/doc/tex/srp.tex
@@ -1,7 +1,7 @@
 \section{Authentication using SRP\index{SRP authentication}}
 
 Authentication using the SRP\footnote{SRP stands for Secure Remote Password and 
-is described in \cite{RFC2945}. The SRP key exchange is not a part of the \tlsI{} protocol}
+is described in \cite{RFC2945}. The SRP key exchange is an extension to the \tlsI{} protocol}
 protocol is actually password authentication. The two peers can be identified using a
 single password, or there can be combinations where the client is 
 authenticated using SRP and the server using a certificate.