From df65e5bced2c96ce14df81f43be794c242651340 Mon Sep 17 00:00:00 2001 From: Matthias Grob Date: Fri, 16 May 2025 00:40:21 +0200 Subject: [PATCH] docs events_interface: fix entire paragraph being declared code by accident (#24860) --- docs/en/concept/events_interface.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/en/concept/events_interface.md b/docs/en/concept/events_interface.md index 3eb0dfe81e..0cdddc6c04 100644 --- a/docs/en/concept/events_interface.md +++ b/docs/en/concept/events_interface.md @@ -92,12 +92,10 @@ Explanations and requirements: Disabled, ``` - ``` - Above we specify a separate external and internal log level, which are the levels displayed to GCS users and in the log file, respectively: `{events::Log::Error, events::LogInternal::Info}`. For the majority of cases you can pass a single log level, and this will be used for both exernal and internal cases. There are cases it makes sense to have two different log levels. For example an RTL failsafe action: the user should see it as Warning/Error, whereas in the log, it is an expected system response, so it can be set to `Info`. - ``` - **Event Message**: - Single-line, short message of the event.