fixes in documentation

4 files changed, 11 insertions, 10 deletions

diff --git a/doc/tex/gnutls.tex b/doc/tex/gnutls.tex
index 3fdf5b29d2..47d2a83fed 100644
--- a/doc/tex/gnutls.tex
+++ b/doc/tex/gnutls.tex
@@ -19,19 +19,19 @@
 \chapter{The Library}
 \section{Introduction}
 \par
-\gnutls is a portable library which implements the {\emph TLS 1.0} and 
-{\emph SSL 3.0} protocols.
+\gnutls is a portable library which implements the \tls 1.0 and 
+\ssl 3.0 protocols.
 TLS stands for 'Transport Layer Security' and is the sucessor of SSL\footnote{
 SSL or Secure Sockets Layer is a protocol designed by Netscape. TLS 1.0 is based on
-{\emph SSL 3.0} protocol. {\emph SSL 2.0} is a very old protocol which is 
-not considered secure today. SSL 2.0 is not implemented in \gnutls}.
-{\emph TLS 1.0}\footnote{described in {\it RFC 2246}} is an Internet protocol,
+\ssl 3.0 protocol. \ssl 2.0 is a very old protocol which is 
+not considered secure today. \ssl 2.0 is not implemented in \gnutls}.
+\tls 1.0\footnote{described in {\it RFC 2246}} is an Internet protocol,
 defined by IETF\footnote{IETF or Internet Engineering Task Force 
 is a large open international community of network
 designers, operators, vendors, and researchers concerned with the evolution of 
 the Internet architecture and the smooth operation of the Internet. It is open to any interested individual.}
 that provides confidentiality, and authentication layers over a {reliable
-transport layer}\footnote{TLS is mostly used over {\emph TCP/IP} although this is not restrictive, you may
+transport layer}\footnote{TLS is mostly used over {\emph{TCP/IP}} although this is not restrictive, you may
 use it over any reliable transport layer.}. \gnutls implements the
 above protocols in reentrant way in order to be used in multiple threads of 
 execution (without the need for Critical Sections and locks).
diff --git a/doc/tex/macros.tex b/doc/tex/macros.tex
index 30614541b0..58fcfcf33a 100644
--- a/doc/tex/macros.tex
+++ b/doc/tex/macros.tex
@@ -1,3 +1,4 @@
-\newcommand{\gnutls}{{\emph GNUTLS} }
-\newcommand{\tls}{{\emph TLS} }
+\newcommand{\gnutls}{{\emph{GNUTLS}} }
+\newcommand{\tls}{{\emph{TLS}} }
+\newcommand{\ssl}{{\emph{SSL}} }
 \newcommand{\HRule}{\rule{\linewidth}{0.4mm}}
diff --git a/doc/tex/resumedb.tex b/doc/tex/resumedb.tex
index 244f6f7e59..f4d2cca74e 100644
--- a/doc/tex/resumedb.tex
+++ b/doc/tex/resumedb.tex
@@ -39,7 +39,7 @@ only one thread can write at a time. The current behaviour of gnutls is
 not to block and wait for the DB to be ready for writing, but continue the
 process normally (and do not save the parameters).  
 \par
- After version {\emph 0.2.10} \gnutls provides callback functions such as:
+ After version {\emph{0.2.10}} \gnutls provides callback functions such as:
 \hyperref{gnutls\_db\_set\_remove\_function()}{gnutls\_db\_set\_remove\_function() (see Section }{ for more
 information)}{gnutls_db_set_remove_function},
 \hyperref{gnutls\_db\_set\_store\_function()}{gnutls\_db\_set\_store\_function() (see Section }{ for more
diff --git a/doc/tex/translayer.tex b/doc/tex/translayer.tex
index fd73623f24..299403196f 100644
--- a/doc/tex/translayer.tex
+++ b/doc/tex/translayer.tex
@@ -17,6 +17,6 @@ can be resumed (called again), if any of these values is returned.
 By default (if none of the above functions are not called), gnutls will use
 the berkeley sockets functions recv() and send(). In this case
 gnutls will use some hacks in order for select() to work, thus
-making easy to add {\emph TLS} support to existing servers.
+making easy to add \tls support to existing servers.