From 855d42718295172d88edc917c2cab822f7ab1fae Mon Sep 17 00:00:00 2001
From: Badlop <badlop@process-one.net>
Date: Tue, 12 Jan 2010 23:57:44 +0000
Subject: Fix explanation of access_max_user_messages.

SVN Revision: 2895
---
 doc/guide.html | 2 +-
 doc/guide.tex  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guide.html b/doc/guide.html
index eabd4312e..f5a39904a 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -2636,7 +2636,7 @@ sent to an offline user will be stored on the server until that user comes
 online again. Thus it is very similar to how email works. Note that
 <TT>ejabberdctl</TT> has a command to delete expired messages
 (see section&#XA0;<A HREF="#ejabberdctl">4.1</A>).</P><DL CLASS="description"><DT CLASS="dt-description">
-<B><TT>{access_max_user_messages, Number}</TT></B></DT><DD CLASS="dd-description">
+<B><TT>{access_max_user_messages, AccessName}</TT></B></DT><DD CLASS="dd-description">
 This option defines which access rule will be enforced to limit
 the maximum number of offline messages that a user can have (quota).
 When a user has too many offline messages, any new messages that he receive are discarded,
diff --git a/doc/guide.tex b/doc/guide.tex
index 54ed750f9..3fb7a7622 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -3387,7 +3387,7 @@ online again. Thus it is very similar to how email works. Note that
 (see section~\ref{ejabberdctl}).
 
 \begin{description}
-  \titem{\{access\_max\_user\_messages, Number\}}\ind{options!access\_max\_user\_messages}
+  \titem{\{access\_max\_user\_messages, AccessName\}}\ind{options!access\_max\_user\_messages}
   This option defines which access rule will be enforced to limit
   the maximum number of offline messages that a user can have (quota).
   When a user has too many offline messages, any new messages that he receive are discarded,
-- 
cgit v1.2.3