From 194b03c40455d03ff3c71e81cf22f946dc35ef9e Mon Sep 17 00:00:00 2001
From: skywind3000 <skywind3000@163.com>
Date: Mon, 16 Jan 2017 12:59:16 +0800
Subject: [PATCH] new readme

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

diff --git a/README.en.md b/README.en.md
index 1092f39..90cfe32 100644
--- a/README.en.md
+++ b/README.en.md
@@ -131,10 +131,8 @@ The protocol default mode is a standard ARQ, and various acceleration switches c
 
 Both the use and configuration of the protocol is very simple, in most cases, after you read the above contents, basically you will be able to use it. If you need further fine control, such as changing the KCP memory allocator, or if you need more efficient large-scale scheduling of KCP links (such as more than 3,500 links), or to better combine with TCP, you can continue the extensive reading:
 
-- [KCP Best Practice](https://github.com/skywind3000/kcp/wiki/KCP-Best-Practice)
-- [Integration with the Existing TCP Server](https://github.com/skywind3000/kcp/wiki/Cooperate-With-Tcp-Server)
-- [Transmission Data Encryption](https://github.com/skywind3000/kcp/wiki/Network-Encryption)
-- [Application Layer Flow Control](https://github.com/skywind3000/kcp/wiki/Flow-Control-for-Users)
+- [KCP Best Practice](https://github.com/skywind3000/kcp/wiki/KCP---Best-Practice---EN)
+- [Integration with the Existing TCP Server](https://github.com/skywind3000/kcp/wiki/KCP---Best-Practice---EN)
 - [Benchmarks](https://github.com/skywind3000/kcp/wiki/KCP-Benchmark)