aboutsummaryrefslogtreecommitdiff
path: root/doc/guide.tex
diff options
context:
space:
mode:
authorAlexey Shchepin <alexey@process-one.net>2003-07-14 18:06:03 +0000
committerAlexey Shchepin <alexey@process-one.net>2003-07-14 18:06:03 +0000
commit1834fb3a724365d804f5c863a27b720ac9bf45b9 (patch)
treed92dc73da4838b5bd2bd6e22fe4f21ca423f4874 /doc/guide.tex
parent* doc/guide.tex: Updated (thanks to Sergei Golovan) (diff)
* src/ejabberd_s2s_out.erl: Close connection after key
verification * src/ejabberd_c2s.erl: start replaced with start_link * src/ejabberd_s2s_in.erl: Likewise * src/ejabberd_s2s_out.erl: Likewise * src/ejabberd_service.erl: Likewise * src/ejabberd_listener.erl: Now uses proc_lib to spawn listeners, removed 3rd parameter in listener configuration (assumed to equal start_link) * src/ejabberd.rel: Updated * doc/guide.tex: Small changes * doc/Makefile: Added implicit charset specification to hevea SVN Revision: 124
Diffstat (limited to 'doc/guide.tex')
-rw-r--r--doc/guide.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/guide.tex b/doc/guide.tex
index 0142437d4..0c0a6d0fe 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -64,9 +64,9 @@ The main features of \ejabberd{} is:
\begin{itemize}
\item Works on most of popular platforms: *nix (tested on Linux and FreeBSD)
and Win32
-\item Distributed: You may run \ejabberd{} on a cluster of machines and all of
+\item Distributed: You can run \ejabberd{} on a cluster of machines and all of
them will serve one Jabber domain.
-\item Fault-tolerance: You may setup an \ejabberd{} cluster so that all the
+\item Fault-tolerance: You can setup an \ejabberd{} cluster so that all the
information required for a properly working service will be stored
permanently on more than one node. This means that if one of the nodes
crashes, then the others will continue working without disruption.