Several documentation fixes. Suggestions and patch by Paul Wujek <pwujek@xp2telecom.com>

5 files changed, 12 insertions, 11 deletions

diff --git a/doc/tex/auth.tex b/doc/tex/auth.tex
index 6be4f29603..edce440600 100644
--- a/doc/tex/auth.tex
+++ b/doc/tex/auth.tex
@@ -18,13 +18,13 @@ The certificate must allow the key to be used for encryption.
 \\
 \hline
 DHE\_RSA & The RSA algorithm is used to sign Ephemeral Diffie Hellman
-parameters which are send to the peer. The key in the certificate must allow
+parameters which are sent to the peer. The key in the certificate must allow
 the key to be used for signing. Note that key exchange algorithms which use
 Ephemeral Diffie Hellman parameters, offer perfect forward secrecy.
 \\
 \hline
 DHE\_DSS & The DSS\footnote{DSS stands for Digital Signature Standard} algorithm is used to sign Ephemeral Diffie Hellman
-parameters which are send to the peer. 
+parameters which are sent to the peer. 
 \\
 \hline
 \end{tabular}
@@ -42,8 +42,9 @@ parameters which are send to the peer.
 
 
 \section{Anonymous authentication\index{Anonymous authentication}}
-The anonymous key exchange perform encryption but there is no indication of the 
-identity of the peer. This kind of authentication is vulnerable to man in the middle attack, 
+The anonymous key exchange perform encryption but there is no indication of 
+the identity of the peer. This kind of authentication is vulnerable to a
+man in the middle attack, 
 but this protocol can be used even if there is no prior communication or common trusted
 parties with the peer. Unless really required, do not use anonymous authentication.
 Available key exchange methods are shown in \hyperref{figure}{figure }{}{fig:anon}.
@@ -103,7 +104,7 @@ SRP & Authentication using the SRP protocol.
 The ``gnutls-srpcrypt'' is a very simple program that emulates the programs in the libsrp 
 found in \htmladdnormallink{http://srp.stanford.edu}{http://srp.stanford.edu}.
 It is intended for use in places where you don't expect srp
-authentication to be the performed to system users.
+authentication to be the performed for system users.
 
 Traditionaly libsrp used two files. One called 'tpasswd' which holds usernames 
 and verifiers, and 'tpasswd.conf' which holds generators and primes.
diff --git a/doc/tex/errors.tex b/doc/tex/errors.tex
index 08c127c76a..9d41fc7d3e 100644
--- a/doc/tex/errors.tex
+++ b/doc/tex/errors.tex
@@ -7,13 +7,13 @@ action has to be taken. Thus negative error codes may be fatal
 or not. 
 \par 
 Fatal errors terminate the connection immediately and
-further sends ard receives will be disallowed. An example of
+further sends and receives will be disallowed. An example of
 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 
 \printfunc{gnutls_record_recv}{gnutls\_record\_recv}.
-This error code indicates that the server requests a rehandshake. The client
+This error code indicates that the server requests a re-handshake. The client
 may ignore this request, or may reply with an alert.
 You can test if an error code is a fatal one by using the
 \printfunc{gnutls_error_is_fatal}{gnutls\_error\_is\_fatal}.
diff --git a/doc/tex/howto.tex b/doc/tex/howto.tex
index d3406f651f..6e7221b4d2 100644
--- a/doc/tex/howto.tex
+++ b/doc/tex/howto.tex
@@ -3,7 +3,7 @@
 
 \section{Introduction}
 This chapter is intended to provide some hints on how to use the \tls{}
-over a simple custom made application protocols. 
+over simple custom made application protocols. 
 The discussion below mainly refers to the \emph{TCP/IP} transport layer
 but may be extended to other ones too.
 
diff --git a/doc/tex/openpgp.tex b/doc/tex/openpgp.tex
index 54760e4526..c8a6a68511 100644
--- a/doc/tex/openpgp.tex
+++ b/doc/tex/openpgp.tex
@@ -39,7 +39,7 @@ actual owner.
 
 \subsubsection{GnuTLS functions}
 
-First we've to differ between owerntrust and validity. Sometimes trust
+First we've to differentiate between ownertrust and validity. Sometimes trust
 and validity is used as a synonym but this is not correct.
 \par
 The ownertrust describes how trustworthy the signature of a special
@@ -54,7 +54,7 @@ the signature he made. There are different ownertrust levels:
 \item I trust ulitmately.
 \end{enumerate}
 
-For example we need three marginal trusted signature to make a key
+For example we need three marginally trusted signature to make a key
 valid or one full trusted signature. The ultimate trust is only used
 when we are the owner of a key and we also have the secret key.
 \par
diff --git a/doc/tex/record.tex b/doc/tex/record.tex
index d6c4292cdd..bae3bbda9c 100644
--- a/doc/tex/record.tex
+++ b/doc/tex/record.tex
@@ -6,7 +6,7 @@ The following functions are available:
 \par
 \begin{itemize}
 \item \printfunc{gnutls_record_send}{gnutls\_record\_send}:
-to send an record packet (with application data).
+to send a record packet (with application data).
 \item \printfunc{gnutls_record_recv}{gnutls\_record\_recv}:
 to receive a record packet (with application data).
 \end{itemize}