Fix some spelling errors in man pages

Thanks lintian

diff --git a/doc/librrd.pod b/doc/librrd.pod
index 0e5bdf72631d044b793ac7da1ebefdad19140e98..5c4b997c420bb9b01fddc12895ba331c835fe23e 100644 (file)
--- a/doc/librrd.pod
+++ b/doc/librrd.pod
@@ -84,7 +84,7 @@ the random number generator is seeded exactly once per process.
 
 =item B<rrd_strtodbl>
 
-an rrd aware string to double convertor which sets rrd_error in if there is a problem
+an rrd aware string to double converter which sets rrd_error in if there is a problem
 and uses the return code exclusively for conversion status reporting.
 
 =item B<rrd_strtod>

diff --git a/doc/rrd-beginners.pod b/doc/rrd-beginners.pod
index 7a0601ac777706ff5bf0ff3590d6b8d0e33e73c2..9a55811d2e22b8da3e6ded72c78a9a5ae757b4cb 100644 (file)
--- a/doc/rrd-beginners.pod
+++ b/doc/rrd-beginners.pod
@@ -27,7 +27,7 @@ databases as listed below:
 =item *
 
 RRDtool stores data; that makes it a back-end tool. The RRDtool command set
-allows the creation of graphs; that makes it a front-end tool as well. Other
+allows one to create graphs; that makes it a front-end tool as well. Other
 databases just store data and can not create graphs.
 
 =item *

diff --git a/doc/rrdcached.pod b/doc/rrdcached.pod
index fad3607ed3042b41a5af8944eb1ce56821efa1c7..2852ec9f000264dd415d72b735ed904d81bac796 100644 (file)
--- a/doc/rrdcached.pod
+++ b/doc/rrdcached.pod
@@ -648,7 +648,7 @@ Example:
 
 =item B<PING>
 
-PING-PONG, this is very usefull when using connection pool between user client and RRDCACHED.
+PING-PONG, this is very useful when using connection pool between user client and RRDCACHED.
 
 Example:
 

diff --git a/doc/rrdcreate.pod b/doc/rrdcreate.pod
index 2ab5b492b58f1b333420a52b40b2f1edaaf0c889..f2e545d436deb1f95372bb085794f438cc874f74 100644 (file)
--- a/doc/rrdcreate.pod
+++ b/doc/rrdcreate.pod
@@ -62,8 +62,8 @@ the B<-l> option in the L<rrdcached> manual.
 
 =head2 S<[B<--template>|B<-t> I<template-file>]>
 
-Specifies a template B<RRD> file to take step, DS and RRA definitions from. This allows to 
-base the structure of a new file on some existing file. The data of the template
+Specifies a template B<RRD> file to take step, DS and RRA definitions from. This allows one
+to base the structure of a new file on some existing file. The data of the template
 file is NOT used for pre-filling, but it is possible to specify the same file as a 
 source file (see below).
 
@@ -104,8 +104,8 @@ will have been used for pre-filling. However, data from multiple sources may be
 combined if it refers to different times or an earlier named source file holds 
 unknown data for a time where a later one holds known data.
 
-If this automatic data selection is not desired, the DS syntax allows to specify
-a mapping of target and source data sources for prefilling. This syntax allows to 
+If this automatic data selection is not desired, the DS syntax allows one to specify
+a mapping of target and source data sources for prefilling. This syntax allows one to 
 rename data sources and to restrict prefilling for a DS to only use data from a 
 single source file.
 

diff --git a/doc/rrdfetch.pod b/doc/rrdfetch.pod
index 98cc679338a72cd08e247abf99212b9e23c91bc8..e9e9677ab553c1bb54903a4006f91dbe8bf82e22 100644 (file)
--- a/doc/rrdfetch.pod
+++ b/doc/rrdfetch.pod
@@ -189,7 +189,7 @@ relative to the start (end) time for those tools that use these
 categories (B<rrdfetch>, L<rrdgraph>) and B<epoch> indicates the 
 *IX epoch (*IX timestamp 0 = 1970-01-01 00:00:00 UTC). B<epoch> is
 useful to disambiguate between a timestamp value and some forms
-of abbreviated date/time specifications, because it allows to use 
+of abbreviated date/time specifications, because it allows one to use 
 time offset specifications using units, eg. B<epoch>+19711205s unambiguously
 denotes timestamp 19711205 and not 1971-12-05 00:00:00 UTC.
 

diff --git a/doc/rrdgraph.pod b/doc/rrdgraph.pod
index c56ded3001e0f05262e026e8a29bb2db4c539953..5281b6609b3454f086a89ac60951d2941bf900a6 100644 (file)
--- a/doc/rrdgraph.pod
+++ b/doc/rrdgraph.pod
@@ -477,7 +477,7 @@ no text is rendered bitmapped.
 [B<-P>|B<--pango-markup>]
 
 All text in RRDtool is rendered using Pango. With the B<--pango-markup> option, all
-text will be processed by pango markup. This allows to embed some simple html
+text will be processed by pango markup. This allows one to embed some simple html
 like markup tags using 
 
  <span key="value">text</span>

diff --git a/doc/rrdgraph_libdbi.pod b/doc/rrdgraph_libdbi.pod
index 839e46674fc9b1513e90781026abe0f37bc512ce..0c3f8eec0a19bf71ec12d6b6bdc6751d1585d4ac 100644 (file)
--- a/doc/rrdgraph_libdbi.pod
+++ b/doc/rrdgraph_libdbi.pod
@@ -147,7 +147,7 @@ values you retrieve from the database.
 For example, it would take more than 2 seconds to graph 5DS on 150 hours of data with a precision of 5 minutes 
 (against 100ms when data comes from a RRD file). This bug has been fixed on latest version of LibDBI (not release yet). 
 At that time, you would need to compile libdbi and libdbi-drivers from CVS repository to fix it.
-You can find more informations on this libdbi-users mailing list thread : http://sourceforge.net/mailarchive/message.php?msg_id=30320894
+You can find more information on this libdbi-users mailing list thread : http://sourceforge.net/mailarchive/message.php?msg_id=30320894
 
 
 =head1 BUGS

diff --git a/doc/rrdrestore.pod b/doc/rrdrestore.pod
index b9b4294898d89ec909db4ec64372e278b539e907..38b7cb616bfd2ed809a50995ff1c47cfe50060eb 100644 (file)
--- a/doc/rrdrestore.pod
+++ b/doc/rrdrestore.pod
@@ -25,7 +25,7 @@ using B<RRDtool> over a network connection), when using "-" as a filename
 the end of the file can be signalled either by closing the data
 channel after the file has transferred (as would be the case when
 using input redirection within a suitable shell) or by sending a
-crtl-Z / newline combination. This allows to send more commands to the
+crtl-Z / newline combination. This allows one to send more commands to the
 B<RRDtool> server after a restore.
 
 =item I<filename.rrd>

diff --git a/doc/rrdtune.pod b/doc/rrdtune.pod
index d6aa63732636b7db9826c638cc5822f45d0ce158..a2ed13d651301059db89c0b6ba6f7cf0a401305b 100644 (file)
--- a/doc/rrdtune.pod
+++ b/doc/rrdtune.pod
@@ -35,7 +35,7 @@ The tune option allows you to alter some of the basic configuration
 values stored in the header area of a Round Robin Database (B<RRD>).
 
 One application of the B<tune> function is to relax the
-validation rules on an B<RRD>. This allows to fill a new B<RRD> with
+validation rules on an B<RRD>. This allows you to fill a new B<RRD> with
 data available in larger intervals than what you would normally want
 to permit. Be very careful with tune operations for COMPUTE data sources.
 Setting the I<min>, I<max>, and  I<heartbeat> for a COMPUTE data source