From 1cd5683bb2cb81c1a534160d3d73b56f5e490311 Mon Sep 17 00:00:00 2001 From: skywind3000 Date: Mon, 16 Jan 2017 13:02:02 +0800 Subject: [PATCH] new document --- README.en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.en.md b/README.en.md index 90cfe32..5e8244f 100644 --- a/README.en.md +++ b/README.en.md @@ -131,8 +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---EN) -- [Integration with the Existing TCP Server](https://github.com/skywind3000/kcp/wiki/KCP---Best-Practice---EN) +- [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)