Imported upstream version 1.4.2.

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

diff --git a/doc/rrdcreate.html b/doc/rrdcreate.html
index adc0755016ed333275f93346144a3470fcd96ee6..597c16d75f896190607a31e17d553dce6f4c561e 100644 (file)
--- a/doc/rrdcreate.html
+++ b/doc/rrdcreate.html
@@ -406,7 +406,7 @@ an average rate for that PDP. If the total "unknown" time accounts for
 more than <strong>half</strong> the &quot;step&quot;, the entire PDP is marked
 as &quot;unknown&quot;. This means that a mixture of known and &quot;unknown&quot; sample
 times in a single PDP &quot;step&quot; may or may not add up to enough &quot;known&quot;
-time to warrent for a known PDP.</p>
+time to warrant a known PDP.</p>
 <p>The &quot;heartbeat&quot; can be short (unusual) or long (typical) relative to
 the &quot;step&quot; interval between PDPs. A short &quot;heartbeat&quot; means you
 require multiple samples per PDP, and if you don't get them mark the
@@ -472,7 +472,7 @@ together with the time.</p>
 
 <dd>
 <p>Assume you have a method to count the number of messages transported by
-your mailserver in a certain amount of time, giving you data like '5
+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
 <strong>ABSOLUTE</strong> data type you can simply update the RRD with the number 5 and the
 end time of your monitoring period. RRDtool will then record the number of