diff --git a/docs/cluster-submariner.md b/docs/cluster-submariner.md
index ec525606148..5d1741c0080 100644
--- a/docs/cluster-submariner.md
+++ b/docs/cluster-submariner.md
@@ -99,7 +99,7 @@ ports:
   protocol: TCP
 ```
 
-`11.16.0.12`  is the IP address of the pod for this service `nginx` in another cluster. When this pod from another cluster is rebuilt, the new pod IP should be passed to this cluster, So that the new correct data path could be established. This whole process may takes some time, depending on your network and load.
+`11.16.0.12`  is the IP address of the pod for this service `nginx` in another cluster. When this pod from another cluster is rebuilt, the new pod IP should be passed to this cluster, so that the new correct data path could be established. This whole process may takes some time, depending on your network and load.
 
 Besides, submariner now **do not** support the existence of multiple service CIDR or pod CIDR in a cluster.
 
@@ -107,7 +107,7 @@ Besides, submariner now **do not** support the existence of multiple service CID
 
 Submariner supports custom build handlers for different CNIs. 
 
-Currently the default data path is is used in this doc. Between the gateway nodes of clusters, traffic is encapsulated in a IPsec tunnel.  For a work node, the traffic destined to a remote cluster will be transited through VXLAN tunnel(if `vx-submarine`) to the gateway node first.
+Currently the default data path is used in this doc. Between the gateway nodes of clusters, traffic is encapsulated in a IPsec tunnel.  For a work node, the traffic destined to a remote cluster will be transited through VXLAN tunnel(if `vx-submarine`) to the gateway node first.
 
 #### operations:
 
diff --git a/docs/multi-nic.md b/docs/multi-nic.md
index 3924020afe1..73719d23653 100644
--- a/docs/multi-nic.md
+++ b/docs/multi-nic.md
@@ -5,7 +5,7 @@ From v1.1, the IPAM part of Kube-OVN can provide subnet and static ip allocation
 ## How it works
 
 By using [Intel Multus CNI](https://github.com/intel/multus-cni), we can attach multiple network interfaces into a Kubernetes Pod.
-However, we still need some cluster-wide IPAM utilities to manage IP addresses for multi network to better mange other CNI plugins.
+However, we still need some cluster-wide IPAM utilities to manage IP addresses for multi network to better manage other CNI plugins.
 In Kube-OVN, we already have CRDs like Subnet and IP and functions for advanced IPAM like ip reservation, random allocation, static allocation and so on.
 We extend the Subnet to network providers other than ovn, so other CNI plugins can take use all the IPAM functions already exist in Kube-OVN.