From d038ff66059b9a969e4146ebe900ad60f5ae047d Mon Sep 17 00:00:00 2001
From: Marco Collovati <marco@vaadin.com>
Date: Wed, 3 Apr 2024 13:25:55 +0200
Subject: [PATCH] fix: fix interface name in navigation docs (CP: latest)

HasRouteParameters interface does not exist, the correct name is HasUrlParameter.
---
 articles/routing/navigation.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/routing/navigation.asciidoc b/articles/routing/navigation.asciidoc
index 06ecfa52ae..2c38e09219 100644
--- a/articles/routing/navigation.asciidoc
+++ b/articles/routing/navigation.asciidoc
@@ -54,7 +54,7 @@ If deep linking is required, the target view must <<updating-url-parameters#,mai
 
 === Passing Data Using Route Parameters
 
-If your target view implements [interfacename]`HasRouteParameters`, you can submit trivial data to the target view as route parameters.
+If your target view implements [interfacename]`HasUrlParameter`, you can submit trivial data to the target view as route parameters.
 Compared to directly interacting with the target views Java API, this method automatically maintains the URL, which is beneficial for deep linking.
 However, you can't pass more complex objects as route parameters as such, and you always need to consider data safety parameters that end up in URLs.