primary-code-test
diff --git a/‎README.md‎
Lines changed: 4 additions & 3 deletions b/‎README.md‎
Lines changed: 4 additions & 3 deletions
diff --git a/‎…/distributed-system/rpc/关于Dubbo的重要知识点.md‎ ‎…m-design/distributed-system/rpc/Dubbo.md‎docs/system-design/distributed-system/rpc/关于Dubbo的重要知识点.md renamed to docs/system-design/distributed-system/rpc/Dubbo.md b/‎…/distributed-system/rpc/关于Dubbo的重要知识点.md‎ ‎…m-design/distributed-system/rpc/Dubbo.md‎docs/system-design/distributed-system/rpc/关于Dubbo的重要知识点.md renamed to docs/system-design/distributed-system/rpc/Dubbo.md
@@ -235,9 +235,10 @@ CAP 也就是 Consistency（一致性）、Availability（可用性）、Partiti
 
 RPC 让调用远程服务调用像调用本地方法那样简单。
 
-1. [Dubbo 总结：关于 Dubbo 的重要知识点](docs/system-design/distributed-system/rpc/关于Dubbo的重要知识点.md)
-2. [服务之间的调用为啥不直接用 HTTP 而用 RPC？](docs/system-design/distributed-system/rpc/服务之间的调用为啥不直接用HTTP而用RPC.md)
-3. [一款基于 Netty+Kyro+Zookeeper 实现的自定义 RPC 框架](https://github.com/Snailclimb/guide-rpc-framework)
+Dubbo 是一款国产的 RPC 框架，由阿里开源。相关阅读：
+
+- [Dubbo 常见问题总结](docs/system-design/distributed-system/rpc/Dubbo.md)
+- [服务之间的调用为啥不直接用 HTTP 而用 RPC？](docs/system-design/distributed-system/rpc/服务之间的调用为啥不直接用HTTP而用RPC.md)
 
 #### API 网关