From 98a37d8e5d8fa096175d19b3c8757f2ee7bf1930 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Sun, 18 May 2025 10:56:53 +1000 Subject: [PATCH] New Crowdin translations - ko (#24873) Co-authored-by: Crowdin Bot --- docs/ko/concept/events_interface.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/ko/concept/events_interface.md b/docs/ko/concept/events_interface.md index a50ec95473..559ccb7da7 100644 --- a/docs/ko/concept/events_interface.md +++ b/docs/ko/concept/events_interface.md @@ -94,12 +94,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`. - ``` + 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.