Imported upstream version 1.4.2.

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

diff --git a/doc/rrdtool.html b/doc/rrdtool.html
index fd28c52009242f0e02cc450d165adc9898434238..5819e66936847b0445b379259d65b86e3cee04fd 100644 (file)
--- a/doc/rrdtool.html
+++ b/doc/rrdtool.html
@@ -170,7 +170,7 @@ uses fetch to retrieve its data from an RRD. Check <a href="././rrdfetch.html">t
 <p>When monitoring the state of a system, it is convenient to have the
 data available at a constant time interval. Unfortunately, you may not
 always be able to fetch data at exactly the time you want
-to. Therefore <strong>RRDtool</strong> lets you update the logfile at any time you
+to. Therefore <strong>RRDtool</strong> lets you update the log file at any time you
 want. It will automatically interpolate the value of the data-source
 (<strong>DS</strong>) at the latest official time-slot (interval) and write this
 interpolated value to the log. The original value you have supplied is
@@ -348,7 +348,7 @@ such a port unless you are sure what you are doing.</p>
 <h1><a name="rrdcached__the_caching_daemon">RRDCACHED, THE CACHING DAEMON</a></h1>
 <p>For very big setups, updating thousands of RRD files often becomes a serious IO
 problem. If you run into such problems, you might want to take a look at
-<a href="././rrdcached.html">the rrdcached manpage</a>, a caching daemon for RRDTool which may help you lessen the
+<a href="././rrdcached.html">the rrdcached manpage</a>, a caching daemon for RRDtool which may help you lessen the
 stress on your disks.</p>
 <p>
 </p>