X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdupdate.pod;h=2d4ee8c7dd4d94dfe7336f205dce1f00cacc5091;hb=f9e5bd6a9d41c4607291cbbd88280129184ab325;hp=394c49cb2e283bc072a1773858e6896f9789fc96;hpb=bf7d0302ab2ff46038f7002a9eab76f4105c3cee;p=rrdtool.git

diff --git a/doc/rrdupdate.pod b/doc/rrdupdate.pod
index 394c49c..2d4ee8c 100644
--- a/doc/rrdupdate.pod
+++ b/doc/rrdupdate.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-rrdtool update - Store a new set of values into the rrd
+rrdtool update - Store a new set of values into the RRD
 
 =for html <div align="right"><a href="rrdupdate.pdf">PDF</a> version.</div>
 
@@ -27,9 +27,9 @@ performs the same function. The I<v> stands for I<verbose>, which
 describes the output returned. B<updatev> returns a list of any and all
 consolidated data points (CDPs) written to disk as a result of the
 invocation of update. The values are indexed by timestamp (time_t),
-RRA (index number), and data source (name). Note that depending
-on the arguments of the current and previous call to update, the
-list may have no entries or a large number of entries.
+RRA (consolidation function and PDPs per CDP), and data source (name).
+Note that depending on the arguments of the current and previous call to
+update, the list may have no entries or a large number of entries.
 
 =item I<filename>
 
@@ -45,7 +45,7 @@ error resistant, as you might be sending the wrong data into a RRD.
 
 The template switch allows you to specify which data sources you are
 going to update and in which order. If the data sources specified in
-the template are not available in the rrd file, the update process
+the template are not available in the RRD file, the update process
 will abort with an error message.
 
 While it appears possible with the template switch to update data sources
@@ -53,7 +53,7 @@ asynchronously, B<RRDtool> implicitly assigns non-COMPUTE data sources missing
 from the template the I<*UNKNOWN*> value. 
 
 Do not specify a value for a COMPUTE B<DST> in the B<update> function. If
-this is done accidently (and this can only be done using the template switch),
+this is done accidentally (and this can only be done using the template switch),
 B<RRDtool> will ignore the value specified for the COMPUTE B<DST>.
 
 =item B<N>|I<timestamp>B<:>I<value>[B<:>I<value>...]
@@ -70,9 +70,9 @@ important when you are working with data-sources of type B<COUNTER>,
 B<DERIVE> or B<ABSOLUTE>. 
 
 The remaining elements of the argument are DS updates. The order of this list is
-the same as the order the data sources were defined in the rra.
+the same as the order the data sources were defined in the RRA.
 If there is no data for a certain data-source, the letter 
-B<U> (eg. N:0.1:U:1) can be defined.
+B<U> (e.g., N:0.1:U:1) can be defined.
 
 The format of the value acquired from the data source is dependent of the
 data source type chosen. Normally it will be numeric, but the data acquisition
@@ -88,7 +88,7 @@ C<rrdtool update demo1.rrd N:3.44:3.15:U:23>
 Update the database file demo1.rrd with 3 known and one I<*UNKNOWN*>
 value. Use the current time as the update time.
 
-C<rrdtool update demo2.rrd 887457267:U 887457521:22 88745790:2.7>
+C<rrdtool update demo2.rrd 887457267:U 887457521:22 887457903:2.7>
 
 Update the database file demo2.rrd which expects data from a single
 data-source, three times. First with an I<*UNKNOWN*> value then with two