docs: remove timer unit from description

the user input has time unit. e.g. "5s" for 5 seconds etc.

apps/emqx/i18n/emqx_schema_i18n.conf

@@ -46,8 +46,8 @@ emqx_schema {
 
   overload_protection_backoff_delay {
     desc {
-        en: "When at high load, some unimportant tasks could be delayed for execution, here set the duration in milliseconds precision."
-        zh: "高负载时，一些不重要的任务可能会延迟执行，在这里设置允许延迟的时间。单位为毫秒。"
+        en: "When at high load, some unimportant tasks could be delayed for execution, here set the duration."
+        zh: "高负载时，一些不重要的任务可能会延迟执行，在这里设置允许延迟的时间。"
     }
     label {
         en: "Delay Time"

apps/emqx_conf/i18n/emqx_conf_schema.conf

@@ -1255,7 +1255,7 @@ Supervisor 报告的类型。默认为 error 类型。
 
   log_overload_kill_restart_after {
     desc {
-      en: """If the handler is terminated, it restarts automatically after a delay specified in milliseconds. The value `infinity` prevents restarts."""
+      en: """If the handler is terminated, it restarts automatically after a delay. The value `infinity` prevents restarts."""
       zh: """如果处理进程终止，它会在以指定的时间后后自动重新启动。 `infinity` 不自动重启。"""
     }
     label {

apps/emqx_management/i18n/emqx_mgmt_api_alarms_i18n.conf

@@ -62,7 +62,7 @@ The default is false."""
 
     duration {
         desc {
-            en: """Indicates how long the alarm has lasted, in milliseconds."""
+            en: """Indicates how long the alarm has been active in milliseconds."""
             zh: """表明告警已经持续了多久，单位：毫秒。"""
         }
     }

apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf

@@ -58,8 +58,8 @@ For bridges only have ingress direction data flow, it can be set to 0 otherwise
 
   start_timeout {
     desc {
-      en: """If 'start_after_created' enabled, how long time do we wait for the resource get started, in milliseconds."""
-      zh: """如果选择了创建后立即启动资源，此选项用来设置等待资源启动的超时时间，单位秒。"""
+      en: """Time interval to wait for an auto-started resource to become healthy before responding resource creation requests."""
+      zh: """在回复资源创建请求前等待资源进入健康状态的时间。"""
     }
     label {
       en: """Start Timeout"""

apps/emqx_resource/src/emqx_resource_buffer_worker.erl

@@ -865,7 +865,7 @@ call_query(QM0, Id, Index, Ref, Query, QueryOpts) ->
     end.
 
 do_call_query(QM, Id, Index, Ref, Query, #{is_buffer_supported := true} = QueryOpts, Resource) ->
-    %% The connector supprots buffer, send even in disconnected state
+    %% The connector supports buffer, send even in disconnected state
     #{mod := Mod, state := ResSt, callback_mode := CBM} = Resource,
     CallMode = call_mode(QM, CBM),
     apply_query_fun(CallMode, Mod, Id, Index, Ref, Query, ResSt, QueryOpts);

lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf

@@ -220,7 +220,7 @@ emqx_ee_bridge_kafka {
         desc {
             en: "When set to 'true', TCP buffer sent as soon as possible. "
                 "Otherwise, the OS kernel may buffer small TCP packets for a while (40 ms by default)."
-            zh: "设置 ‘true' 让系统内核立即发送。否则当需要发送当内容很少时，可能会有一定延迟（默认 40 毫秒）。"
+            zh: "设置‘true’让系统内核立即发送。否则当需要发送的内容很少时，可能会有一定延迟（默认 40 毫秒）。"
         }
         label {
             en: "No Delay"