diff --git a/README-CN.md b/README-CN.md
index f989b9bed..84a72912d 100644
--- a/README-CN.md
+++ b/README-CN.md
@@ -60,7 +60,7 @@ EMQX Cloud 文档：[docs.emqx.com/zh/cloud/latest/](https://docs.emqx.com/zh/cl
 - 访问 [EMQ 问答社区](https://askemq.com/) 以获取帮助，也可以分享您的想法或项目。
 - 添加小助手微信号 `emqmkt`，加入 EMQ 微信技术交流群。
 - 加入我们的 [Discord](https://discord.gg/xYGf3fQnES)，参于实时讨论。
-- 关注我们的 [bilibili](https://space.bilibili.com/522222081)，获取最新物联网技术分享。
+- 关注我们的 [Bilibili](https://space.bilibili.com/522222081)，获取最新物联网技术分享。
 - 关注我们的 [微博](https://weibo.com/emqtt) 或 [Twitter](https://twitter.com/EMQTech)，获取 EMQ 最新资讯。
 
 ## 相关资源
diff --git a/README-RU.md b/README-RU.md
index 6cb7fda6a..9f8347e2b 100644
--- a/README-RU.md
+++ b/README-RU.md
@@ -32,7 +32,7 @@ docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8883:8883 -p 8084:8084 -p
 
 Чтобы ознакомиться с функциональностью EMQX, пожалуйста, следуйте [руководству по началу работы](https://www.emqx.io/docs/en/v5.0/getting-started/getting-started.html#start-emqx).
 
-#### Запуск кластера EMQX на kubernetes
+#### Запуск кластера EMQX на Kubernetes
 
 [Документация по EMQX Operator](https://github.com/emqx/emqx-operator/blob/main/docs/en_US/getting-started/getting-started.md).
 
diff --git a/README.md b/README.md
index 3fda5999c..622cbfc99 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p
 
 Next, please follow the [Deploy with Docker](https://www.emqx.io/docs/en/v5.1/deploy/install-docker.html) guide for further instructions.
 
-#### Run EMQX cluster on kubernetes
+#### Run EMQX cluster on Kubernetes
 
 Please consult official [EMQX Operator](https://github.com/emqx/emqx-operator/blob/main/docs/en_US/getting-started/getting-started.md) documentation for details.
 
diff --git a/apps/emqx/src/bpapi/README.md b/apps/emqx/src/bpapi/README.md
index 9c4bef959..3b94c6f50 100644
--- a/apps/emqx/src/bpapi/README.md
+++ b/apps/emqx/src/bpapi/README.md
@@ -137,7 +137,7 @@ to negotiate protocol version:
 protocol version supported by the remote node
 `Node`. `emqx_bpapi:supported_version(ProtocolId)` returns maximum
 protocol version that is supported by all nodes in the cluster. It can
-be useful when the protocol involves multicalls or multicasts.
+be useful when the protocol involves multi-calls or multi-casts.
 
 The business logic can assume that the supported protocol version is
 not going to change on the remote node, while it is running. So it is