docs: fix a few zh version change log wording

changes/v5.0.21.en.md

@@ -13,7 +13,7 @@
 
 - [#9986](https://github.com/emqx/emqx/pull/9986) For helm charts, add MQTT ingress bridge; and removed stale `mgmt` references.
 
-- [#10123](https://github.com/emqx/emqx/pull/10123) Improve the performance of `/bridegs` API.
+- [#10123](https://github.com/emqx/emqx/pull/10123) Improve the performance of `/bridges` API.
   Earlier, when the number of nodes in the cluster was large or the node was busy, the API may have a request timeout.
 
 - [#9998](https://github.com/emqx/emqx/pull/9998) Redact the HTTP request body in the authentication error logs for security reasons.
@@ -21,7 +21,7 @@
 ## Bug Fixes
 
 - [#10013](https://github.com/emqx/emqx/pull/10013) Fix return type structure for error case in API schema for `/gateways/:name/clients`.
-
+u
 - [#10014](https://github.com/emqx/emqx/pull/10014) In dashboard API for `/monitor(_current)/nodes/:node` return `404` instead of `400` if node does not exist.
 
 - [#10026](https://github.com/emqx/emqx/pull/10026) Metrics are now only exposed via the /bridges/:id/metrics endpoint. Metrics are no longer returned in other API operations such as getting the list of all bridges, or in the response when a bridge has been created.
@@ -44,7 +44,7 @@
   * If the node is found to be running but not responding to pings, the user is advised to check if the host name is resolvable and reachable.
   * If the node is responding to pings, but the EMQX app is not running, it is likely a bug. In this case, the user is advised to report a Github issue.
 
-- [#10055](https://github.com/emqx/emqx/pull/10055) Fix `mqtt.max_awaiting_rel` change does not work.
+- [#10055](https://github.com/emqx/emqx/pull/10055) Fix: configuration parameter `mqtt.max_awaiting_rel` had no effect.
 
 - [#10056](https://github.com/emqx/emqx/pull/10056) Fix `/bridges` API status code.
   - Return `400` instead of `403` in case of removing a data bridge that is dependent on an active rule.
@@ -89,7 +89,8 @@
   For example, `env EMQX_STATSD__SERVER='127.0.0.1:8124' . /bin/emqx start` results in unreadable string (not '127.0.0.1:8124') displayed in Dashboard's Statsd settings page.
   Related PR: [HOCON#234](https://github.com/emqx/hocon/pull/234).
 
-- [#10132](https://github.com/emqx/emqx/pull/10132) Fix some error logs generated by `systemctl stop emqx` command. The command havn't stopping jq, os_mon application properly.
+- [#10132](https://github.com/emqx/emqx/pull/10132) Fix some error logs generated by `systemctl stop emqx` command.
+  Prior to the fix, the command was not stopping jq and os_mon applications properly.
 
 - [#10144](https://github.com/emqx/emqx/pull/10144) Add `-setcookie` emulator flag when invoking `emqx ctl` to prevent problems with emqx cli when home directory is read only. Fixes [#10142](https://github.com/emqx/emqx/issues/10142).
 

changes/v5.0.21.zh.md

@@ -2,18 +2,18 @@
 
 ## 增强
 
-- [#10022](https://github.com/emqx/emqx/pull/10022) 开始发布Rocky Linux 9（与Enterprise Linux 9兼容）和MacOS 12软件包。
+- [#10022](https://github.com/emqx/emqx/pull/10022) 开始发布Rocky Linux 9（与Enterprise Linux 9兼容）和 MacOS 12 软件包。
 
 - [#10139](https://github.com/emqx/emqx/pull/10139) 将 `extraVolumeMounts` 添加到 EMQX Helm Chart 中，它将能够挂载用户自己的文件到 EMQX 实例中，例如在 [#9052](https://github.com/emqx/emqx/issues/9052) 中提到的 ACL 规则文件。
 
-  完成了 [#10116](https://github.com/emqx/emqx/issues/10116)
+  修复了 issue [#10116](https://github.com/emqx/emqx/issues/10116)
 
 - [#9893](https://github.com/emqx/emqx/pull/9893) 当使用 `clean_start=false` 标志连接时，EMQX 将会从消息队列中过滤出被封禁客户端发出的消息，使它们不能被下发给订阅者。
   此前被封禁客户端发出的消息仍可能在这一场景下被下发给订阅者。
 
 - [#9986](https://github.com/emqx/emqx/pull/9986) 在 helm chart 中新增了 MQTT 桥接 ingress 的配置参数；并删除了旧版本遗留的 `mgmt` 配置。
 
-- [#10123](https://github.com/emqx/emqx/pull/10123) 改进 `/bridegs` API 的性能。
+- [#10123](https://github.com/emqx/emqx/pull/10123) 改进 `/bridges` API 的性能。
   此前，当集群中节点数目较多或节点忙时，该 API 可能出现请求超时的情况。
 
 - [#9998](https://github.com/emqx/emqx/pull/9998) 出于安全原因，在身份验证错误日志中模糊 HTTP 请求正文。
@@ -43,7 +43,7 @@
   * 如果发现节点正在运行但不响应 ping，则建议用户检查节点主机名是否有效并可达。
   * 如果节点响应 ping 但 EMQX 应用程序未运行，则很可能是一个错误。在这种情况下，建议用户报告一个Github issue。
 
-- [#10055](https://github.com/emqx/emqx/pull/10055) 修复 `mqtt.max_awaiting_rel` 更新不生效问题。
+- [#10055](https://github.com/emqx/emqx/pull/10055) 修复配置项 `mqtt.max_awaiting_rel` 更新不生效问题。
 
 - [#10056](https://github.com/emqx/emqx/pull/10056) 修复 `/bridges` API 的 HTTP 状态码。
   - 当删除被活动中的规则依赖的数据桥接时，将返回 `400` 而不是 `403` 。