docs(ModelDefinition): align English version with german docs

Author: DevTKSS

docs/articles/de/Navigation/HowTo-ModelDefinition-de.md

@@ -23,7 +23,7 @@ Also, dann lass uns das doch mal genauer betrachten. Was bedeutet das denn nun?
   In diesem Fall wären es dann nur zum beispiel die anzuzeigende Eigenschaft, wie die `string`-Property `Title`, die du entsprechend in deiner `Page`, also deiner `View` zum `ViewModel` bzw. `Model` bindest und schon bist du fertig damit!
 
   > [!TIP]
-  > Mit der Attached Property `uen:Navi` kannst du den Titel der Seite in der NavigationView setzen.
+  > Mit der `Attached Property` `uen:Navigation.Request` bzw. `uen:Navigation.Data` kannst du übrigens auch Daten an die Navigation übergeben, wie [in der Uno Dokumentation gut anhand von `Widget`-Elementen erklärt wird](https://platform.uno/docs/articles/external/uno.extensions/doc/Learn/Navigation/HowTo-NavigateInXAML.html#2-navigationdata) hierfür benötigst du dann bspw. aber wieder `DataViewMap`-Definitionen in der Routen Registrierung.
 
 - **Nein:**
 

docs/articles/en/Navigation/HowTo-ModelDefinition-en.md

@@ -4,23 +4,70 @@ uid: DevTKSS.Uno.ExtensionsNavigation.HowTo-DefiningModelOrViewModel.en
 
 # How-To: Navigation in the Model or ViewModel
 
-Now let's take a look at how we need to structure our Model or ViewModel to work with Uno Extensions Navigation.
+Now let's take a look at how we need to structure the connection between the `View` and the `ViewModel` to work with Uno Extensions Navigation.
 
-## Prerequisites
+First, let's ask ourselves the question: **Navigation only in Xaml - Is that even possible?**
+
+*Yes and No.*
+
+So, let's take a closer look. What does this mean?
+
+- **Yes:**
+
+  In fact, you basically don't need either codebehind or code in the ViewModel / Model for navigation if you use the `Attached Properties` in the Xaml of your page.
+
+  **If you're interested in how this works, you can find it directly here:**
+
+  [How-To: Defining the UI with NavigationView for ExtensionsNavigation](xref:DevTKSS.Uno.ExtensionsNavigation.HowTo-Defining-UI.en)
+
+  In this case, it would typically only be the properties to display, like the `string` property `Title`, that you bind from your `Page`, i.e., your `View` to the `ViewModel` or `Model`, and you're done!
+
+  > [!TIP]
+  > By the way, with the `Attached Properties` `uen:Navigation.Request` and `uen:Navigation.Data` you can also pass data to navigation, as [explained well in the Uno documentation using `Widget` elements as examples](https://platform.uno/docs/articles/external/uno.extensions/doc/Learn/Navigation/HowTo-NavigateInXAML.html#2-navigationdata). However, for this you'll need `DataViewMap` definitions in the route registration.
 
-1. First of all, create a Model or ViewModel element.
+- **No:**
 
-    [!INCLUDE [Guide to creating a basic Model or ViewModel](../HowTo-Adding-New-VM-Class-Record-en.md)]
+  1. You still need to register the routes you want to navigate in the `RegisterRoutes` method in the `App.xaml.cs` class, so the `INavigator` knows what belongs together and from where you want to allow navigation to which routes with which "qualifiers".
+  2. If you want to trigger navigation in your Model or ViewModel, then of course you need the `INavigator` there to start the navigation.
 
-2. Now add the `INavigator` as a **DependencyInjection** constructor parameter.
+## Creating the Prerequisites
 
-    [!INCLUDE [Guide: Use Constructor Parameters for DependencyInjection](../HowTo-Using-DI-in-ctor-en.md)]
+Okay, so let's assume we have the second case mentioned above and want to do the following:
 
-## Navigation in Xaml
+1. Our user should be able to trigger a function in our `ViewModel` or `Model` by clicking a `Button`
+2. This function should navigate them to the `SecondPage` that we included in the Uno App template, but it could also be any other page you created and registered yourself.
+
+    Let's assume this is our `App.xaml.cs` with the `RegisterRoutes` method:
+
+    ```csharp
+    {
+        views.Register(
+            new ViewMap(ViewModel: typeof(ShellModel)),
+            new ViewMap<MainPage, MainModel>(),
+            new DataViewMap<SecondPage, SecondViewModel, Entity>()
+        );
+
+    routes.Register(
+        new RouteMap("", View: views.FindByViewModel<ShellModel>(),
+        Nested:
+            [
+                new RouteMap("Main", View: views.FindByViewModel<MainModel>(), IsDefault:true),
+                new RouteMap("Second", View: views.FindByViewModel<SecondModel>())
+            ]
+        )
+    );
+    }
+    ```
+
+But how should our `ViewModel` or `Model` look so we can implement this?
+
+For this we need the following steps:
+
+## Prerequisites
 
-Basically, you don't actually need navigation code in the ViewModel / Model if you use the `Attached Properties` as described in the [Guide: Defining the UI with NavigationView for ExtensionsNavigation](xref:DevTKSS.Uno.ExtensionsNavigation.HowTo-Defining-UI.en)!
+1. [Create a Model or ViewModel](xref:DevTKSS.Uno.Setup.HowTo-AddingNew-VM-Class-Record.en)
 
-In this case, it would typically only be the Title properties or others that you bind from View to ViewModel and you would be done. And that is also a big advantage of this extension in my opinion.
+2. [And get the `INavigator` there as a **`DependencyInjection` Constructor Parameter**](xref:DevTKSS.Uno.Setup.Using-DI-in-ctor.en)
 
 ## Binding View UI Controls to Properties in the ViewModel or Model