* doc/guide.tex: Typos

SVN Revision: 795

diff --git a/ChangeLog b/ChangeLog
index 2a4ccf0afc9f1172f0e113468158ceacf0366077..cc33ee84f34e9bea8648991a1427b11f2f8b1283 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2007-06-25  Mickael Remond  <mickael.remond@process-one.net>
 
+       * doc/guide.tex: Typos
+
        * src/mod_muc/mod_muc_room.erl: New anti-abuse options:
        min_presence_interval and min_message_interval
        * doc/guide.tex: Likewise 

diff --git a/doc/guide.tex b/doc/guide.tex
index 4b117ba00b35091fde1a3a4a744b22a6fc98e115..69a62eb4b5274f66410ace23e45f1ac4db982d12 100644 (file)
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -1949,7 +1949,7 @@ describing the reason why the message is not acceptable.
 This option defines the minimum of time between presence changes
 coming from a given user in seconds. This option is global and valid
 for all chat rooms. A decimal value can be used. When this option is
-not defined, no restriction are applied. This option can be used to
+not defined, no restriction is applied. This option can be used to
 protect a MUC service for users abuses, as fastly changing a user
 presence will result in possible large presence packet broadcast. If a
 user tries to change its presence more often than the specified
@@ -2039,7 +2039,7 @@ The Multi-Users Chat module now supports clustering and load
 balancing. One module can be started per cluster node. Rooms are
 distributed at creation time on all available MUC module
 instances. The multi-user chat module is clustered but the room
-themselves are not clustered nor fault-tolerant: If the not managing a
+themselves are not clustered nor fault-tolerant: If the node managing a
 set of rooms goes down, the rooms disappear and they will be recreated
 on an available node on first connection attempt.