From dfb1cc2b8821aa7f2dfb1f71083310e964fd3be9 Mon Sep 17 00:00:00 2001
From: Nico Wang <104056727+wangzihao05@users.noreply.github.com>
Date: Thu, 12 Jan 2023 16:55:36 +0800
Subject: [PATCH] fix syntax errors (#2240)

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 1d58701b2fe..6c7df3462bc 100644
--- a/README.md
+++ b/README.md
@@ -86,7 +86,7 @@ We are looking forward to your PR!
    
    A: Different CNI Implementations have different scopes, there is no single implementation that can resolve all network problems. Kube-OVN is aiming to bring SDN to Cloud Native. 
       If you are missing the old day network concepts like VPC, Subnet, customize route, security groups etc. you can not find corresponding functions in any other CNIs. Then Kube-OVN
-      is you only choice when you need these functions to build datacenter or enterprise network fabric.
+      is your only choice when you need these functions to build datacenter or enterprise network fabric.
 
 2. Q: How about the scalability of Kube-OVN?
 
@@ -94,7 +94,7 @@ We are looking forward to your PR!
 
 3. Q: What's the Addressing/IPAM? Node-specific or cluster-wide?
 
-   A: Kube-OVN use a cluster-wide IPAM, Pod address can float to any nodes in the cluster.
+   A: Kube-OVN uses a cluster-wide IPAM, Pod address can float to any nodes in the cluster.
 
 4. Q: What's the encapsulation?