diff --git a/readme.md b/readme.md
index 2daf1cd..65df0ad 100644
--- a/readme.md
+++ b/readme.md
@@ -43,7 +43,7 @@ Since most of websites in the world now support HTTPS, SpoofDPI doesn't bypass D
 ### HTTPS
  Although TLS 1.3 encrypts every handshake process, the domain names are still shown as plaintext in the Client hello packet. 
  In other words, when someone else looks on the packet, they can easily guess where the packet is headed to. 
- The domain name can offer a significant information while DPI is being processed, And we can actually see that the connection is blocked right after sending Client hello packet.
+ The domain name can offer a significant information while DPI is being processed, and we can actually see that the connection is blocked right after sending Client hello packet.
  I had tried some ways to bypass this, and found out that it seemed like only the first chunk gets inspected when we send the Client hello packet splited in chunks. 
  What SpoofDPI does to bypass this is to send the first 1 byte of a request to the server, 
  and then send the rest.