From 8b420a5218405330bc2646178e7d0a3beed91c03 Mon Sep 17 00:00:00 2001 From: Robin Mueller Date: Mon, 10 Jul 2023 00:36:35 +0200 Subject: [PATCH] small docs correction --- satrs-core/src/event_man.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/satrs-core/src/event_man.rs b/satrs-core/src/event_man.rs index c3d6182..5c56b85 100644 --- a/satrs-core/src/event_man.rs +++ b/satrs-core/src/event_man.rs @@ -21,7 +21,7 @@ doc = ::embed_doc_image::embed_image!("event_man_arch", "images/event_man_arch.p //! ![Event flow][event_man_arch] //! //! The event manager has a listener table abstracted by the [ListenerTable], which maps -//! listener groups identified by [ListenerKey]s to a [sender ID][SenderId]. +//! listener groups identified by [ListenerKey]s to a [sender ID][ChannelId]. //! It also contains a sender table abstracted by the [SenderTable] which maps these sender IDs //! to a concrete [SendEventProvider]s. A simple approach would be to use one send event provider //! for each OBSW thread and then subscribe for all interesting events for a particular thread