From 4a3daaafd67242d7e09d42caf2f23f128dc4a853 Mon Sep 17 00:00:00 2001
From: Jon Person <person.jon@gmail.com>
Date: Fri, 15 Nov 2024 16:09:53 -0700
Subject: [PATCH] Fixed incorrect .NET version in welcome message

---
 src/mudblazor/MudBlazor.Template/Components/Pages/Home.razor | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/mudblazor/MudBlazor.Template/Components/Pages/Home.razor b/src/mudblazor/MudBlazor.Template/Components/Pages/Home.razor
index 9087cb4..ecd96d1 100644
--- a/src/mudblazor/MudBlazor.Template/Components/Pages/Home.razor
+++ b/src/mudblazor/MudBlazor.Template/Components/Pages/Home.razor
@@ -40,7 +40,7 @@
 
 <MudText Typo="Typo.h6" GutterBottom="true">Prerendering</MudText>
 <MudText Typo="Typo.body2" GutterBottom="true">
-    If you're exploring the features of .NET 8 Blazor,<br /> you might be pleasantly surprised to learn that each page is prerendered on the server,<br /> regardless of the selected render mode.<br /><br />
+    If you're exploring the features of .NET 9 Blazor,<br /> you might be pleasantly surprised to learn that each page is prerendered on the server,<br /> regardless of the selected render mode.<br /><br />
     This means that you'll need to inject all necessary services on the server,<br /> even when opting for the wasm (WebAssembly) render mode.<br /><br />
     This prerendering functionality is crucial to ensuring that WebAssembly mode feels fast and responsive,<br /> especially when it comes to initial page load times.<br /><br />
     For more information on how to detect prerendering and leverage the RenderContext, you can refer to the following link: