diff --git a/_data/instruments/assetguard.yaml b/_data/instruments/assetguard.yaml
index 5856a113..21e26223 100644
--- a/_data/instruments/assetguard.yaml
+++ b/_data/instruments/assetguard.yaml
@@ -1,7 +1,7 @@
 ---
-name: Asset Guard
+name: AssetGuard
 developer: SensorFleet Oy
-title: Asset Guard Instrument
+title: AssetGuard Instrument
 categories:
   - Integrity Monitoring
   - Asset Tracking
@@ -11,7 +11,7 @@ description:
 has_ui: true
 public: true
 data_retention_desc:
-  The Asset Guard Instrument retains the collected information until the
+  The AssetGuard Instrument retains the collected information until the
   Instrument is removed.
 performance_desc: Does not generate significant CPU or IO load
 network_access_type: passive
@@ -22,7 +22,7 @@ required_interfaces:
     type: mirror-bridge
 relations:
   - description:
-      Asset Guard needs to find AssetProbe Instruments in order to receive their
+      AssetGuard needs to find AssetProbe Instruments in order to receive their
       events
     instrument_name: AssetProbe
     instrument_type: assetprobe
@@ -38,3 +38,9 @@ produced_event_types:
   - match: instruments.assetguard.asset.moved
     type: exact
     title: Asset moved alert
+  - match: instruments.assetguard.asset.updated
+    type: exact
+    title: Asset updated
+  - match: instruments.assetguard.assets.details
+    type: exact
+    title: All assets and their details
diff --git a/_data/instruments/logforwarder.yaml b/_data/instruments/logforwarder.yaml
index 47df3e05..280c39ba 100644
--- a/_data/instruments/logforwarder.yaml
+++ b/_data/instruments/logforwarder.yaml
@@ -28,6 +28,9 @@ produced_event_types:
   - match: instruments.logforwarder.stats
     type: exact
     title: Logforwarder statistics event
+  - match: instruments.logforwarder.input_ev.
+    type: prefix
+    title: Events from the input event pipeline
 network_access_type: active
 required_interfaces:
   - type: any
diff --git a/_data/instruments/rmgr.yaml b/_data/instruments/rmgr.yaml
index 946e7fa0..fe7e1fc4 100644
--- a/_data/instruments/rmgr.yaml
+++ b/_data/instruments/rmgr.yaml
@@ -34,6 +34,9 @@ produced_event_types:
   - match: instruments.rmgr.suricata_ruleset_sent
     type: exact
     title: New Suricata ruleset was sent
+  - match: instruments.rmgr.download_processing_status
+    type: exact
+    title: Ruleset or IOC processing status update
 relations:
   - description:
       Rule Manager needs at least one Suricata IDS instrument to function. It
@@ -51,3 +54,11 @@ relations:
       - find
       - direct_message
     required: false
+  - description:
+      A Downloader instrument must be present for external rulesources and ioc
+      feeds to be updated. A health warning will be raised if downloads are
+      scheduled but no Downloader is available.
+    instrument_name: Downloader
+    instrument_type: downloader
+    permissions:
+      - find
diff --git a/instruments/assetguard/index.html b/instruments/assetguard/index.html
index 853d888e..00633580 100644
--- a/instruments/assetguard/index.html
+++ b/instruments/assetguard/index.html
@@ -1,6 +1,6 @@
 ---
 layout: datasheet
-title: Asset Guard Instrument
+title: AssetGuard Instrument
 description: Automated inventory of the network's assets and alerts about unexpected assets entering the network.
 ---
 
@@ -61,7 +61,7 @@ <h2 id="properties">Properties</h2>
     <tr class="odd">
       <td>Data retention</td>
       <td>
-        The Asset Guard Instrument retains the collected information until the
+        The AssetGuard Instrument retains the collected information until the
         Instrument is removed.
       </td>
     </tr>
diff --git a/instruments/netflow/index.html b/instruments/netflow/index.html
index 4d01f49c..c51a3f28 100644
--- a/instruments/netflow/index.html
+++ b/instruments/netflow/index.html
@@ -7,15 +7,17 @@
 <!-- File is generated automatically, do not edit directly. -->
 
 <p>
-  Netflow can be used to collect NetFlow information from network traffic. For
-  introduction to NetFlow, see
+  Netflow is used to create NetFlow information from listened network traffic.
+  For introduction to NetFlow, see
   <a href="https://en.wikipedia.org/wiki/NetFlow">Wikipedia</a>.
 </p>
 <p>
-  The Instrument will listen traffic on mirror-bridge interface and store the
-  traffic flows (as identified by source and destination IP addresses and
-  protocol -specific ports) in NetFlow records. These NetFlow records can then
-  be downloaded from the Instrument using the provided HTTP API.
+  The Instrument will listen captured traffic on mirror-bridge interface and
+  store information about observed traffic flows (as identified by source and
+  destination IP addresses and protocol -specific ports) in NetFlow records.
+  These NetFlow records can then be downloaded from the Instrument using the
+  provided HTTP API. The Instrument also provides UI which can be used to view
+  stored NetFlow records.
 </p>
 <p>
   NetFlow records are stored in NetFlow format version 9 and they are stored in
diff --git a/instruments/rmgr/index.html b/instruments/rmgr/index.html
index 18d4a5e3..268fd418 100644
--- a/instruments/rmgr/index.html
+++ b/instruments/rmgr/index.html
@@ -65,7 +65,7 @@ <h2 id="properties">Properties</h2>
     </tr>
     <tr class="even">
       <td>Related Instruments</td>
-      <td>Zeek</td>
+      <td>Zeek, Downloader</td>
     </tr>
     <tr class="odd">
       <td>Data retention</td>