*** empty log message ***

SVN Revision: 51

2 files changed, 16 insertions, 18 deletions

diff --git a/doc/guide.html b/doc/guide.html
index 94649871d..7356258cb 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -17,7 +17,7 @@
 
 <H3 ALIGN=center>Alexey Shchepin<BR><A HREF="mailto:alexey@sevcom.net"><TT>mailto:alexey@sevcom.net</TT></A><BR><A HREF="xmpp:aleksey@jabber.ru"><TT>xmpp:aleksey@jabber.ru</TT></A></H3>
 
-<H3 ALIGN=center>January 23, 2003</H3> <DIV ALIGN=center><IMG SRC="logo.png">
+<H3 ALIGN=center>January 26, 2003</H3> <DIV ALIGN=center><IMG SRC="logo.png">
  
  </DIV><BR>
 <BR>
@@ -115,8 +115,8 @@ runned on them. Each element of list is a tuple with following elements:
 
 <LI> <TT>ejabberd_s2s_in</TT>: serves incoming S2S connections;
 
-<LI> <TT>ejabberd_service</TT>: serves connections to Jabber services (i.e.
- that use <TT>jabber:component:accept</TT> namespace).
+<LI> <TT>ejabberd_service</TT>: serves connections to Jabber services
+ (i.&nbsp;e. that use <TT>jabber:component:accept</TT> namespace).
 </UL>For example, following configuration defines that C2S connections listened on
 port 5222, S2S on port 5269 and that service <TT>conference.jabber.org</TT>
 must be connected to port 8888 with password ``<TT>secret</TT>''.<BR>
@@ -171,15 +171,13 @@ Example:
 {access, configure, [{allow, admin}]}.
 {access, something, [{deny, badmans},
                      {allow, all}]}.
-</PRE>TBD<BR>
-<BR>
-<!--TOC subsubsection Modules-->
+</PRE><!--TOC subsubsection Modules-->
 
 <H4>3.1.4&nbsp;&nbsp; Modules</H4><!--SEC END -->
 
 <A NAME="sec:configmodules"></A>Option <TT>modules</TT> defines list of modules that will be loaded after
 <TT>ejabberd</TT> startup. Each list element is a tuple where first element is a
-name of module and second is list of options to this module. Refer to
+name of module and second is list of options to this module. See
 section&nbsp;<A HREF="#sec:modules">5</A> for detailed information on each module.<BR>
 <BR>
 Example:
@@ -205,7 +203,7 @@ Example:
 <TT>mod_configure</TT> loaded (see section&nbsp;<A HREF="#sec:modconfigure">5.4</A>). Also highly
 recommended to load <TT>mod_disco</TT> (see section&nbsp;<A HREF="#sec:moddisco">5.5</A>), because
 <TT>mod_configure</TT> highly integrates with it. Also recommended to use
-disco-capable client.<BR>
+disco- and xdata-capable client.<BR>
 <BR>
 TBD<BR>
 <BR>
diff --git a/doc/guide.tex b/doc/guide.tex
index 1559cc9f3..c9be15708 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -30,7 +30,7 @@
 \author{Alexey Shchepin \\
   \ahrefurl{mailto:alexey@sevcom.net} \\
   \ahrefurl{xmpp:aleksey@jabber.ru}}
-\date{January 23, 2003}
+\date{January 26, 2003}
 
 \begin{document}
 \begin{titlepage}
@@ -78,7 +78,7 @@ To compile \ejabberd{}, you need following packages:
 
 Currently no stable version released.
 
-Latest alpha version can be retrieved via CVS.  Do following steps:
+Latest alpha version can be retrieved via CVS\@.  Do following steps:
 \begin{itemize}
 \item \texttt{export CVSROOT=:pserver:cvs@www.jabber.ru:/var/spool/cvs}
 \item \texttt{cvs login}
@@ -119,7 +119,7 @@ values.
 \label{sec:confighostname}
 
 Option \texttt{hostname} defines name of \Jabber{} domain that \ejabberd{}
-serves.  E.\,g. to use \texttt{jabber.org} domain add following line in config:
+serves.  E.\,g.\ to use \texttt{jabber.org} domain add following line in config:
 \begin{verbatim}
 {host, "jabber.org"}.
 \end{verbatim}
@@ -144,8 +144,8 @@ Currently three modules implemented:
 \begin{itemize}
 \item \texttt{ejabberd\_c2s}: serves C2S connections;
 \item \texttt{ejabberd\_s2s\_in}: serves incoming S2S connections;
-\item \texttt{ejabberd\_service}: serves connections to \Jabber{} services (i.e.
-  that use \texttt{jabber:component:accept} namespace).
+\item \texttt{ejabberd\_service}: serves connections to \Jabber{} services
+  (i.\,e.\ that use \texttt{jabber:component:accept} namespace).
 \end{itemize}
 
 For example, following configuration defines that C2S connections listened on
@@ -218,7 +218,7 @@ Example:
 
 Option \texttt{modules} defines list of modules that will be loaded after
 \ejabberd{} startup.  Each list element is a tuple where first element is a
-name of module and second is list of options to this module.  Refer to
+name of module and second is list of options to this module.  See
 section~\ref{sec:modules} for detailed information on each module.
 
 Example:
@@ -246,7 +246,7 @@ To use facility of online reconfiguration of \ejabberd{} needed to have
 \modconfigure{} loaded (see section~\ref{sec:modconfigure}).  Also highly
 recommended to load \moddisco{} (see section~\ref{sec:moddisco}), because
 \modconfigure{} highly integrates with it.  Also recommended to use
-disco-capable client.
+disco- and xdata-capable client.
 
 TBD
 
@@ -258,12 +258,12 @@ TBD
 \label{sec:howitworks}
 
 \Jabber{} domain is served by one or more \ejabberd{} nodes.  This nodes can be
-runned on different computers that can be connected via network.  They all must
+runned on different machines that can be connected via network.  They all must
 have access to connect to port 4369 of all another nodes, and must have same
 magic cookie (see Erlang/OTP documentation, in short file
 \texttt{\~ejabberd/.erlang.cookie} must be the same on all nodes).  This is
 needed because all nodes exchange information about connected users, S2S
-connection ,registered services, etc...
+connection, registered services, etc\ldots
 
 Each \ejabberd{} node run following modules:
 \begin{itemize}
@@ -322,7 +322,7 @@ Following options used by many modules, so they described in separate section.
 \subsubsection{Option \texttt{iqdisc}}
 
 Many modules define handlers for processing IQ queries of different namespaces
-to this server or to user (e.\,g. to \texttt{myjabber.org} or to
+to this server or to user (e.\,g.\ to \texttt{myjabber.org} or to
 \texttt{user@myjabber.org}).  This option defines processing discipline of this
 queries.  Possible values are:
 \begin{description}