From: Marc Fournier <marc.fournier@camptocamp.com>
Date: Sat, 4 Apr 2015 20:34:41 +0000 (+0200)
Subject: doc & comments: s/mili/milli/
X-Git-Tag: collectd-5.5.0~12^2~8^2~1
X-Git-Url: https://git.verplant.org/?a=commitdiff_plain;h=254878cea0e2b6f5c32298a7d26406f62c4b7f7c;p=collectd.git

doc & comments: s/mili/milli/
---

diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index f5130307..b59d1f42 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -4634,7 +4634,7 @@ that numerical port numbers must be given as a string, too.
 
 Use I<Password> to authenticate when connecting to I<Redis>.
 
-=item B<Timeout> I<Timeout in miliseconds>
+=item B<Timeout> I<Milliseconds>
 
 The B<Timeout> option set the socket timeout for node response. Since the Redis
 read function is blocking, you should keep this value as low as possible. Keep
@@ -5732,7 +5732,7 @@ Hostname or address to connect to. Defaults to C<localhost>.
 
 Service name or port number to connect to. Defaults to C<27017>.
 
-=item B<Timeout> I<Timeout>
+=item B<Timeout> I<Milliseconds>
 
 Set the timeout for each operation on I<MongoDB> to I<Timeout> milliseconds.
 Setting this option to zero means no timeout, which is the default.
@@ -5868,7 +5868,7 @@ The B<Port> option is the TCP port on which the Redis instance accepts
 connections. Either a service name of a port number may be given. Please note
 that numerical port numbers must be given as a string, too.
 
-=item B<Timeout> I<Timeout in miliseconds>
+=item B<Timeout> I<Milliseconds>
 
 The B<Timeout> option sets the socket connection timeout, in milliseconds.
 
diff --git a/src/powerdns.c b/src/powerdns.c
index f3d40830..81e253bf 100644
--- a/src/powerdns.c
+++ b/src/powerdns.c
@@ -84,10 +84,10 @@ typedef struct statname_lookup_s statname_lookup_t;
 
 /* Description of statistics returned by the recursor: {{{
 all-outqueries      counts the number of outgoing UDP queries since starting
-answers0-1          counts the number of queries answered within 1 milisecond
+answers0-1          counts the number of queries answered within 1 millisecond
 answers100-1000     counts the number of queries answered within 1 second
-answers10-100       counts the number of queries answered within 100 miliseconds
-answers1-10         counts the number of queries answered within 10 miliseconds
+answers10-100       counts the number of queries answered within 100 milliseconds
+answers1-10         counts the number of queries answered within 10 milliseconds
 answers-slow        counts the number of queries answered after 1 second
 cache-entries       shows the number of entries in the cache
 cache-hits          counts the number of cache hits since starting