From 1e74bb66c61d965c4aa261adfaf058f3356cff09 Mon Sep 17 00:00:00 2001
From: Florian Forster <octo@collectd.org>
Date: Tue, 18 Jun 2013 17:25:46 +0200
Subject: [PATCH] collectd-threshold(5): Correct the description of the
 "Interesting" config option.

---
 src/collectd-threshold.pod | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/collectd-threshold.pod b/src/collectd-threshold.pod
index e340f1ac..35f8a9fc 100644
--- a/src/collectd-threshold.pod
+++ b/src/collectd-threshold.pod
@@ -186,10 +186,12 @@ state will be keep.
 
 =item B<Interesting> B<true>|B<false>
 
-If set to B<true> (the default), the threshold must be treated as interesting
-and, when a number of B<Timeout> values will lost, then a missing notification
-will be dispatched. On the other hand, if set to B<false>, the missing
-notification will never dispatched for this threshold.
+If set to B<true> (the default), a notification with severity C<FAILURE> will
+be created when a matching value list is no longer updated and purged from the
+internal cache. When this happens depends on the I<interval> of the value list
+and the global B<Timeout> setting. See the B<Interval> and B<Timeout> settings
+in L<collectd.conf(5)> for details. If set to B<false>, this event will be
+ignored.
 
 =back
 
-- 
2.30.2