Development, remove monitor event from the list as discussed with @fichtner

source/development/backend/legacy.rst

@@ -100,7 +100,6 @@ bootup                       Bootup, normal legacy service configuration, when n
                              (for example: unbound, ntpd)
 newwanip                     Triggered after configuration of a new interface address, expects a maximum of two positional
                              parameters (:code:`$verbose` and :code:`$interface`).
-monitor                      Executed when there are changes that involve (dpinger) gateway monitoring.
 ===========================  =================================================================================
 
 
@@ -111,6 +110,7 @@ monitor                      Executed when there are changes that involve (dping
     pluginctl -c monitor
 
 
+
 ------------------
 Firewall
 ------------------

source/development/backend/overview.rst

@@ -20,11 +20,10 @@ in sequence:
     our end to make sure :code:`tun` and :code:`tap` devices exist before doing further configuration.
 3.  :doc:`plugins/configure/early </development/backend/legacy>`, configure :code:`early` event in bootup process, before normal services are being started (things like ssh and the webconfigurator use this spot)
 4.  :doc:`plugins/firewall </development/backend/legacy>` allows for automatic firewall (nat) rule registration in cases where the service is able to ship its own rules. (some do this optionally for easy setup)
-5.  :doc:`plugins/configure/monitor </development/backend/legacy>`, configure :code:`monitor` event, with the network stack ready, signal the monitor (dpinger) for startup
-6.  :doc:`plugins/configure/vpn </development/backend/legacy>`, configure :code:`vpn` event, vpn type services are being configured here (e.g. IPsec, OpenVPN)
-7.  :doc:`plugins/configure/bootup </development/backend/legacy>`, configure :code:`bootup` event, normal legacy service configuration, when not using the rc(8) system (for example: unbound, ntpd)
-8.  :doc:`syshook/start </development/backend/autorun>`, simple shell scripts to run after all networking has been setup.
-9.  :doc:`rc(8) </development/backend/autorun>`, regular `rc(8)` scripts (executed using the above :code:`the rc.syshook.d/start``)
+5.  :doc:`plugins/configure/vpn </development/backend/legacy>`, configure :code:`vpn` event, vpn type services are being configured here (e.g. IPsec, OpenVPN)
+6.  :doc:`plugins/configure/bootup </development/backend/legacy>`, configure :code:`bootup` event, normal legacy service configuration, when not using the rc(8) system (for example: unbound, ntpd)
+7.  :doc:`syshook/start </development/backend/autorun>`, simple shell scripts to run after all networking has been setup.
+8.  :doc:`rc(8) </development/backend/autorun>`, regular `rc(8)` scripts (executed using the above :code:`the rc.syshook.d/start``)
 
 
 .. Tip::