kmesh-net · ravindra-RKB · Jun 14, 2026
diff --git a/build/docker/README.md b/build/docker/README.md
@@ -2,7 +2,7 @@
 
 由于kmesh的部分能力对于内核版本有着较强的依赖，我们提供了两种kmesh的镜像：
 
-一种是可直接在指定环境上使用的镜像，该镜像可提供kemsh的七层网络流量治理；
+一种是可直接在指定环境上使用的镜像，该镜像可提供kmesh的七层网络流量治理；
 
 另一种是兼容模式的镜像，可根据当前宿主机的内核能力去选择编译kmesh的可用部分，该镜像不依赖于内核版本。
 

diff --git a/docs/cn/zh/kmesh_commands-zh.md b/docs/cn/zh/kmesh_commands-zh.md
@@ -16,7 +16,7 @@ Flags:
   -h, --help                   help for kmesh-daemon
       --mode string            controller plane mode, valid values are [kernel-native, dual-engine] (default "dual-engine")
       --monitoring string      enable kmesh traffic monitoring in daemon process(default "true")  
-      --profiliing string      whether to enable profiling or not (default "false")
+      --profiling string       whether to enable profiling or not (default "false")
       --enable-ipsec string    enable ipsec encryption and authentication between nodes(default false)
 
 # example

diff --git a/docs/cn/zh/multiple_dataplane_CN.md b/docs/cn/zh/multiple_dataplane_CN.md
@@ -169,7 +169,7 @@ flannel的conflist格式如下：
 
 daemon变更如下：
 
-- 在kmesh使能时写入kemsh plugin配置到cni conflist中
+- 在kmesh使能时写入kmesh plugin配置到cni conflist中
 
  在kmesh-daemon启动时，自动将cni plugin配置`{"type":"kmesh-cni"}`写入到/etc/cni/net.d/目录中的配置文件(.conflist结尾)中去
 

diff --git a/docs/en/Startup_process_of_eBPF_programs.md b/docs/en/Startup_process_of_eBPF_programs.md
@@ -33,7 +33,7 @@ Three main eBPF programs involved in ads mode have different attach points. The
 #### Startup process in dual engine mode (StartworkloadMode)
 
 - NewWorkloadBpf: Create the file system directory required by eBPF according to the configuration, including the file path of BPF map and prog
-- Load: Load the e BPF program of Kmesh, obtain the type and additional type of the program, and update the tail call program to implement the routing forwarding function
+- Load: Load the eBPF program of Kmesh, obtain the type and additional type of the program, and update the tail call program to implement the routing forwarding function
 - Attach: Attach the eBPF program of Kmesh to the specified cgroup and manage the eBPF program using bpflink
 The four main eBPF programs involved in dual engine mode, the eBPF programs of sockconn and sockops types are mounted on cgroup2, and the path is /mnt/kmesh_cgroup2. The eBPF program of sendmsg type is mounted on the eBPF program of sockops type, and the xdpauth eBPF program is mounted in the network card driver of the pod managed by Kmesh.
 

diff --git a/docs/en/kmesh_commands.md b/docs/en/kmesh_commands.md
@@ -16,7 +16,7 @@ Flags:
   -h, --help                   help for kmesh-daemon
       --mode string            controller plane mode, valid values are [kernel-native, dual-engine] (default "dual-engine")
       --monitoring string      enable kmesh traffic monitoring in daemon process(default "true")  
-      --profiliing string      whether to enable profiling or not (default "false")
+      --profiling string       whether to enable profiling or not (default "false")
       --enable-ipsec string    enable ipsec encryption and authentication between nodes(default false)
 
 # example

diff --git a/docs/en/kmesh_deploy_and_develop_in_kind.md b/docs/en/kmesh_deploy_and_develop_in_kind.md
@@ -20,7 +20,7 @@ Let's start from setting up the required environment. You can follow the steps b
 
     You can take reference from the [istio official document](https://istio.io/latest/docs/setup/platform-setup/kind/).
 
-    If you want to specified multiple workers or node image, you can:
+    If you want to specify multiple workers or node image, you can:
 
     ```shell
     kind create cluster --image=kindest/node:v1.23.17 --config=- <<EOF

diff --git a/docs/en/multiple_dataplane_EN.md b/docs/en/multiple_dataplane_EN.md
@@ -169,7 +169,7 @@ The format of flannel's conflist is as follows:
 
 The daemon changes are as follows:
 
-- When kmesh is enabled, write the Kemsh plugin configuration to the CNI conflist
+- When kmesh is enabled, write the Kmesh plugin configuration to the CNI conflist
 
  When kmesh-daemon starts, it automatically writes the cni plugin configuration `{"type":"kmesh-cni"}` to the configuration file (.conflist) in the /etc/cni/net.d/ directory
 

diff --git a/docs/proposal/observability.md b/docs/proposal/observability.md
@@ -179,7 +179,7 @@ The "Design Details" section below is for the real
 nitty-gritty.
 -->
 
-Kmesh needs to collect metrics through the kernel and pass them on to the user mode. In the user mode, accesslog is generated from metrics. And support querying metrics through kemsh localhost:15020.
+Kmesh needs to collect metrics through the kernel and pass them on to the user mode. In the user mode, accesslog is generated from metrics. And support querying metrics through kmesh localhost:15020.
 
 ### Design Details