diff --git a/EN_Home.md b/EN_Home.md
index 38c9a29..612fdd6 100644
--- a/EN_Home.md
+++ b/EN_Home.md
@@ -1,6 +1,6 @@
 # Introduction
 
-KCP is a fast and reliable ARQ protocol, which can decrease the latency 30%-40%(2/3 in the best situation), by using FEC/ARQ which costs about 10%-20% bandwidth. As KCP consists of a series of application-level algorithms, the under-layer transport is not specified, so user must provide the concrete protocol such as UDP, or choose any protocol preferred; KCP provides API to set the callback to send packets, update the received bytes and update the wall clock. There is no `syscalls` in KCP, it's well defined library to integrated to any applications.
+KCP is a fast and reliable ARQ protocol, which decrease the latency about 30%-40%(2/3 in the best situation), by using FEC/ARQ which costs about 10%-20% bandwidth. As KCP consists of a series of application-level algorithms, the under-layer transport is not specified, so user must provide the concrete protocol such as UDP, or choose any protocol preferred; KCP provides API to set the callback to send packets, update the received bytes and update the wall clock. There is no `syscalls` in KCP, it's well defined library to integrated to any applications.
 
 There are only two source files, the `ikcp.h` and `ikcp.c`, which can be easily integrated to your protocol stack. For example, if your application works without ARQ/FEC mechenism, such as a P2P system or RTMP/RTSP/HTTP server, KCP can help you to take advantage of ARQ or FEC by few lines(maybe < 10) of codes.