Imported upstream version 1.4.2.

[pkg-rrdtool.git] / doc / rrdcreate.txt

diff --git a/doc/rrdcreate.txt b/doc/rrdcreate.txt
index 0a82202f8b90692bf854440a7060c4d20af65456..2b24d86af74864c232ff4d4f810a84ef36c7b974 100644 (file)
--- a/doc/rrdcreate.txt
+++ b/doc/rrdcreate.txt
@@ -352,8 +352,8 @@ T\bTh\bhe\be H\bHE\bEA\bAR\bRT\bTB\bBE\bEA\bAT\bT a\ban\bnd\bd t\bth\bhe\be S\bST\bTE\bEP\bP
        average rate for that PDP. If the total "unknown" time accounts for
        more than h\bha\bal\blf\bf the "step", the entire PDP is marked as "unknown". This
        means that a mixture of known and "unknown" sample times in a single
-       PDP "step" may or may not add up to enough "known" time to warrent for
-       a known PDP.
+       PDP "step" may or may not add up to enough "known" time to warrant a
+       known PDP.
 
        The "heartbeat" can be short (unusual) or long (typical) relative to
        the "step" interval between PDPs. A short "heartbeat" means you require
@@ -415,7 +415,7 @@ H\bHO\bOW\bW T\bTO\bO M\bME\bEA\bAS\bSU\bUR\bRE\bE
 
        Mail Messages
            Assume you have a method to count the number of messages
-           transported by your mailserver in a certain amount of time, giving
+           transported by your mail server in a certain amount of time, giving
            you data like '5 messages in the last 65 seconds'. If you look at
            the count of 5 like an A\bAB\bBS\bSO\bOL\bLU\bUT\bTE\bE data type you can simply update the
            RRD with the number 5 and the end time of your monitoring period.
@@ -528,4 +528,4 @@ A\bAU\bUT\bTH\bHO\bOR\bR
 
 
 
-1.3.8                             2008-06-11                      RRDCREATE(1)
+1.4.2                             2009-10-14                      RRDCREATE(1)