From 2ae04c3c1d8d139dc8f964fb26cf52c037bc84c6 Mon Sep 17 00:00:00 2001 From: Camila Belo Date: Thu, 11 Jan 2024 17:46:00 +0100 Subject: [PATCH] docs(frontend-system): fix dialogue on external routes binding Signed-off-by: Camila Belo --- docs/frontend-system/architecture/07-routes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/frontend-system/architecture/07-routes.md b/docs/frontend-system/architecture/07-routes.md index 52edea5de9..2bc2792e89 100644 --- a/docs/frontend-system/architecture/07-routes.md +++ b/docs/frontend-system/architecture/07-routes.md @@ -96,7 +96,7 @@ We have completed our journey of creating a plugin page route. This is what the - [2] We associate our route reference with our page by providing it as an option during creation of the page extension. - [3] Finally, our plugin provides both routes and extensions. -It's a smart question, and the answer can be found in the (Binding External Route References)[#building-external-route-references] section, wait a bit, keep reading and you'll understand why. +It may be unclear why we need to pass the route to the plugin once it has already been passed to the extension. It's a good point, and the explanation can be found in the (Binding External Route References)[#building-external-route-references] section, wait a bit, keep reading and you'll understand why. ### Using a Route Reference