chore: Update code snipped Line numbers, highlight and match Englisch Model ViewModel setup guide to German Localized

Author: DevTKSS

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

@@ -18,11 +18,11 @@ Bevor du mit der Routen Registrierung beginnst, brauchst du noch zwei Dinge:
 
    - [Neue Klasse oder Record Definitionen für ein ViewModel oder Model hinzufügen](xref:DevTKSS.Uno.Setup.HowTo-AddingNew-VM-Class-Record.de)
 
-## RegisterRoutes Methode
+## `RegisterRoutes` Methode in `App.xaml.cs` entdecken
 
 Füge die dafür benötigte Methode wie folgt in deine App Klasse unterhalb der `OnLaunched` Methode ein:
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L82)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L80)]
 
 ## Definieren der `ViewMap`'s
 
@@ -43,7 +43,7 @@ Wenn zusätzliche Daten Objekte bei der Navigation dieser Route erforderlich sin
 
 So sieht das zum Beispiel dann in der XamlNavigationApp aus, wo ich `Entity` nicht mehr benötigt habe und diese Route entsprechend zurück konvertiert habe:
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L83-L89?highlight=L5)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L82-L87?highlight=5)]
 
 ## Hierarchisch aufgebaute `RoutesMap`'s
 
@@ -68,7 +68,7 @@ Nun wollen wir aber auf der `MainPage` vielleicht eine TabBar, NavigationBar, ei
 
 **Das machen wir beispielsweise so:**
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L88-L103)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L89-L103)]
 
 Hier siehst du, dass ich:
 

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

@@ -64,6 +64,10 @@ public partial class DashboardViewModel : ObservableObject
 }
 ```
 
+With this code, you can bind the `Name` property in the View and use the `NavigateSecondAsyncCommand` to navigate to the `SecondViewModel`.
+
+You can use a button or another control in the View to trigger navigation, but by binding the `IsEnabled` property of the control to the `CanExecute` status of the command, you can only execute navigation when the name is not empty.
+
 ### [Mvux](#tab/mvux)
 
 ```csharp
@@ -92,8 +96,12 @@ public partial record MainModel
 }
 ```
 
-With this code, you can bind the `Name` property in the View and use the `NavigateSecondAsyncCommand` to navigate to the `SecondViewModel`.
+Here you can define a button in the View that calls the `NavigateSecondAsync` method to navigate to the `SecondModel`, retrieve the `Name` value, and pass it as data to the next page.
 
-You can use a button or another control in the View to trigger navigation, but by binding the `IsEnabled` property of the control to the `CanExecute` status of the command, you can only execute navigation when the name is not empty.
+If you compare how this looks in MVVM and MVUX, you'll notice it's fundamentally quite similar, but in MVUX the whole thing is somehow more organized and you need less "boilerplate" code to achieve the same result.
+
+To create a TwoWay binding directly on the `IState<string> Name` in the View, you don't even need a `PropertyChanged` notification like you would in MVVM. Instead, you simply attach a `.ForEach(...)` to the `.Value(...)`, create a method that receives the new value, and you can work with it directly. No more tedious implementation of `INotifyPropertyChanged`.
+
+Learn more about this in the [Guide: React to Route Changes](xref:DevTKSS.Uno.ExtensionsNavigation.HowTo-ChangeRoutes.en).
 
 ---

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

@@ -18,11 +18,11 @@ Before you start with route registration, you need two things:
 
    - [Add new class or record definitions for a ViewModel or Model](xref:DevTKSS.Uno.Setup.HowTo-AddingNew-VM-Class-Record.en)
 
-## RegisterRoutes Method
+## Discovering `RegisterRoutes` Method in `App.xaml.cs`
 
 Add the required method to your App class below the `OnLaunched` method as follows:
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L82)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L80)]
 
 ## Defining the `ViewMap`'s
 
@@ -40,7 +40,7 @@ If additional data objects are required when navigating this route, you convert
 
 For example, this is what it looks like in the XamlNavigationApp, where I no longer needed `Entity` and converted this route back accordingly:
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L83-L89)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L82-L87?highlight=5)]
 
 ## Hierarchically Structured `RoutesMap`'s
 
@@ -65,7 +65,7 @@ Now, on the `MainPage`, we might want to use a TabBar, NavigationBar, a Frame wi
 
 **We do this, for example, like this:**
 
-[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L88-L103)]
+[!code-csharp[](../../../../src/DevTKSS.Uno.XamlNavigationApp/App.xaml.cs#L89-L103)]
 
 Here you can see that I added another page, the `DashboardPage`, and created a Model for it named `DashboardModel`. I also nested the `Second` route into the `RouteMap` of the `Main` route.