diff --git a/meeting-notes/20190613.md b/meeting-notes/20190613.md
index ffcd7a09da09ad26a7f41ce5de28c28e39a20e54..a227b585e9bb5b41266ac7f34c34b5b739c3c844 100644
--- a/meeting-notes/20190613.md
+++ b/meeting-notes/20190613.md
@@ -21,8 +21,8 @@
 * What are typical filter usage patterns?
   ** switched on for a while, then deactivated and never activated again?: 81 (bad charts), 167 (two brief disables underway), 302 (switched off on the grounds of insufficient activity)
      ** switched on for a short while and then powered down: mostly stuff merged to other filters; or for which the community decides filter is not an appropriate solution (308); or decides to not implement the thing (that way); 290 (disabled, since relevant pages were protected)
-     ** or switched off after a short while because there were no hits: 304
-     ** or switched off after a longer while, because it was not tripped frequently, in order to save conditions from the condition limit
+     ** or switched off after a short while because there were no hits: 304, 67, 122
+     ** or switched off after a longer while, because it was not tripped frequently, in order to save conditions from the condition limit: 211 ("Disable, appears to be inactive (log only filter). If you are using this filter, please let me know, and I'll reenable it -Prodego")
      ** switched off bc merged to another filter 440 was merged in 345
   ** switched on and still on: 11 (verify), 79 (with brief periods of being disabled for couple of minutes/hours, probably in order to update the pattern), 164, 642 (if we ignore the 2min period it was disabled on 13.4.2018), 733 (2.11.2015-present)
   ** switched on for a while, deactivated for a while, activated again?: 61, 98 (was deactivated briefly since an editor found the "warn" action unfounded; re-enabled to tag), 148 ("20160213 - disabled - possible technical issue - see edit filter noticeboard - xaosflux")