diff --git a/doc/project2-RaftKV.md b/doc/project2-RaftKV.md
index 3374c43d..84d5c0f2 100644
--- a/doc/project2-RaftKV.md
+++ b/doc/project2-RaftKV.md
@@ -93,7 +93,7 @@ First, the code that you should take a look at is  `RaftStorage` located in `kv/
 Then, here comes the core of TinyKV — raftstore. The structure is a little complicated, you can read the reference of TiKV to give you a better understanding of the design:
 
 - <https://pingcap.com/blog-cn/the-design-and-implementation-of-multi-raft/#raftstore>  (Chinese Version)
-- <https://pingcap.com/blog/2017-08-15-multi-raft/#raftstore> (English Version)
+- <https://pingcap.com/blog/design-and-implementation-of-multi-raft/#raftstore> (English Version)
 
 The entrance of raftstore is `Raftstore`, see `kv/raftstore/raftstore.go`.  It starts some workers to handle specific tasks asynchronously,  and most of them aren’t used now so you can just ignore them. All you need to focus on is `raftWorker`.(kv/raftstore/raft_worker.go)
 
diff --git a/doc/reading_list.md b/doc/reading_list.md
index 7da3301f..79dfb633 100644
--- a/doc/reading_list.md
+++ b/doc/reading_list.md
@@ -81,9 +81,9 @@
   - Multi-Raft
     - <https://tikv.org/deep-dive/scalability/multi-raft/>
   - Split & Merge
-    - <https://pingcap.com/blog/2017-07-20-tidbinternal3/>
+    - <https://pingcap.com/blog/tidb-internal-scheduling/>
   - Balance
-    - <https://pingcap.com/blog/2017-07-20-tidbinternal3/>
+    - <https://pingcap.com/blog/tidb-internal-scheduling/>
 - Distributed Transactions
   - Reading Materials
     - Database Internals: 5. Transaction Processing and Recovery