From 1a90c1654cc565b4fb38d5a953240eb99e5dcd90 Mon Sep 17 00:00:00 2001 From: Zhongwen Deng Date: Thu, 2 Feb 2023 11:43:04 +0800 Subject: [PATCH] chore: bad typo --- apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf | 6 +++--- lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf b/apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf index 7e9fcd9e7..8e349f4aa 100644 --- a/apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf +++ b/apps/emqx_resource/i18n/emqx_resource_schema_i18n.conf @@ -59,7 +59,7 @@ 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: """如果选择了创建后立即启动资源，此选项用来设置等待资源启动的超时时间，单位毫秒。""" + zh: """如果选择了创建后立即启动资源，此选项用来设置等待资源启动的超时时间，单位秒。""" } label { en: """Start Timeout""" @@ -80,8 +80,8 @@ For bridges only have ingress direction data flow, it can be set to 0 otherwise query_mode { desc { - en: """Query mode. Optional 'sync/async', default 'sync'.""" - zh: """请求模式。可选 '同步/异步'，默认为'同步'模式。""" + en: """Query mode. Optional 'sync/async', default 'async'.""" + zh: """请求模式。可选 '同步/异步'，默认为'异步'模式。""" } label { en: """Query mode""" diff --git a/lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf b/lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf index be1e581bd..cb3d6618d 100644 --- a/lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf +++ b/lib-ee/emqx_ee_bridge/i18n/emqx_ee_bridge_kafka.conf @@ -303,7 +303,7 @@ emqx_ee_bridge_kafka { "When a single message is over the limit, it is still sent (as a single element batch)." zh: "最大消息批量字节数。" "大多数 Kafka 环境的默认最低值是 1 MB，EMQX 的默认值比 1 MB 更小是因为需要" - "补偿 Kafka 消息编码索需要的额外字节（尤其是当每条消息都很小的情况下）。" + "补偿 Kafka 消息编码所需要的额外字节（尤其是当每条消息都很小的情况下）。" "当单个消息的大小超过该限制时，它仍然会被发送，（相当于该批量中只有单个消息）。" } label { @@ -371,7 +371,7 @@ emqx_ee_bridge_kafka { "Greater value typically means better throughput. However, there can be a risk of message reordering when this " "value is greater than 1." zh: "设置 Kafka 生产者（每个分区一个）在收到 Kafka 的确认前最多发送多少个请求（批量）。" - "调大这个值通常可以增加吞吐量，但是，当该值设置大于 1 是存在消息乱序的风险。" + "调大这个值通常可以增加吞吐量，但是，当该值设置大于 1 时存在消息乱序的风险。" } label { en: "Max Inflight" @@ -395,14 +395,14 @@ emqx_ee_bridge_kafka { desc { en: "Message buffer mode.\n\n" "memory: Buffer all messages in memory. The messages will be lost in case of EMQX node restart\n" - "disc: Buffer all messages on disk. The messages on disk are able to survive EMQX node restart.\n" + "disk: Buffer all messages on disk. The messages on disk are able to survive EMQX node restart.\n" "hybrid: Buffer message in memory first, when up to certain limit " "(see segment_bytes config for more information), then start offloading " "messages to disk, Like memory mode, the messages will be lost in case of " "EMQX node restart." zh: "消息缓存模式。\n" "memory: 所有的消息都缓存在内存里。如果 EMQX 服务重启，缓存的消息会丢失。\n" - "disc: 缓存到磁盘上。EMQX 重启后会继续发送重启前未发送完成的消息。\n" + "disk: 缓存到磁盘上。EMQX 重启后会继续发送重启前未发送完成的消息。\n" "hybrid: 先将消息缓存在内存中，当内存中的消息堆积超过一定限制" "（配置项 segment_bytes 描述了该限制）后，后续的消息会缓存到磁盘上。" "与 memory 模式一样，如果 EMQX 服务重启，缓存的消息会丢失。"