From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Date: Fri, 12 Aug 2011 14:59:07 +0000 (+0200)
Subject: correct typos
X-Git-Tag: gnutls_3_0_1~15^2~2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=317f8a832b1d685e7a785ced7f9741278084e243;p=thirdparty%2Fgnutls.git

correct typos
---

diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi
index 2b250b2301..3a9f5dfef1 100644
--- a/doc/cha-gtls-app.texi
+++ b/doc/cha-gtls-app.texi
@@ -672,13 +672,13 @@ In user authentication protocols (e.g., EAP or SASL mechanisms) it is
 useful to have a unique string that identifies the secure channel that
 is used, to bind together the user authentication with the secure
 channel.  This can protect against man-in-the-middle attacks in some
-situations.  The unique strings is a ``channel bindings''.  For
-background and more discussion see @xcite{RFC5056}.
+situations.  That unique string is called a ``channel binding''.  For
+background and discussion see @xcite{RFC5056}.
 
-You can extract a channel bindings using the
+In @acronym{GnuTLS} you can extract a channel binding using the
 @funcref{gnutls_session_channel_binding} function.  Currently only the
-@code{GNUTLS_CB_TLS_UNIQUE} type is supported, which corresponds to
-the @code{tls-unique} channel bindings for TLS defined in
+type @code{GNUTLS_CB_TLS_UNIQUE} is supported, which corresponds to
+the @code{tls-unique} channel binding for TLS defined in
 @xcite{RFC5929}.
 
 The following example describes how to print the channel binding data.