From 242bc150fe44fbeda7645d7432a3abfa716e996b Mon Sep 17 00:00:00 2001
From: caicancai <77189278+caicancai@users.noreply.github.com>
Date: Wed, 29 Nov 2023 00:13:21 +0800
Subject: [PATCH] chore/docs: fix broken link (#812)

Signed-off-by: caicancai <77189278+caicancai@users.noreply.github.com>
---
 docs/03-architecture-overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/03-architecture-overview.md b/docs/03-architecture-overview.md
index 2549067e9..98a52b6d7 100644
--- a/docs/03-architecture-overview.md
+++ b/docs/03-architecture-overview.md
@@ -251,7 +251,7 @@ Another example is the *filter scan* rule. In RisingLight, the storage layer sup
 
 The *filter scan* rule will automatically merge a filter plan node and a table scan node, apply the filter condition to the table scan node, and produce a single `TableScan` node.
 
-In a nutshell, in RisingLight, the optimizer will transform while optimizing the logical plan into a physical plan. See [`src/optimizer`](../src/optimizer) for more information. The example SQL will produce the following physical plan: `PhysicalProjection <- PhysicalHashAgg <- PhysicalTableScan`. Note that as physical nodes have almost identical information to logical nodes, we store information of logical nodes inside physical nodes as `logical` variable. Despite their existence inside physical plans, after all, the following tree only contain physical nodes.
+In a nutshell, in RisingLight, the optimizer will transform while optimizing the logical plan into a physical plan. See [`src/optimizer`](../src/planner/optimizer.rs) for more information. The example SQL will produce the following physical plan: `PhysicalProjection <- PhysicalHashAgg <- PhysicalTableScan`. Note that as physical nodes have almost identical information to logical nodes, we store information of logical nodes inside physical nodes as `logical` variable. Despite their existence inside physical plans, after all, the following tree only contain physical nodes.
 
 ```rust
 PhysicalProjection {