Update prerendering propagation remarks (#35762)

Author: guardrex

aspnetcore/blazor/components/render-modes.md

@@ -221,11 +221,10 @@ Prerendering is enabled by default for interactive components.
 
 Internal navigation for interactive routing doesn't involve requesting new page content from the server. Therefore, prerendering doesn't occur for internal page requests, including for [enhanced navigation](xref:blazor/fundamentals/routing#enhanced-navigation-and-form-handling). For more information, see [Static versus interactive routing](xref:blazor/fundamentals/routing#static-versus-interactive-routing), [Interactive routing and prerendering](xref:blazor/components/prerender#interactive-routing-and-prerendering), and [Enhanced navigation and form handling](xref:blazor/fundamentals/routing#enhanced-navigation-and-form-handling).
 
-<!-- UPDATE 10.0 Tracking https://github.com/dotnet/aspnetcore/issues/55635
-                 for .NET 10 work in this area. Update the following remark
-                 if changes are made to the framework. -->
+<!-- UPDATE 11.0 Tracking https://github.com/dotnet/aspnetcore/issues/55635
+                 for .NET 11 work in this area. -->
 
-Disabling prerendering using the following techniques only takes effect for top-level render modes. If a parent component specifies a render mode, the prerendering settings of its children are ignored. This behavior is under investigation for possible changes with the release of .NET 10 in November, 2025.
+Disabling prerendering using the following techniques only takes effect for top-level render modes. If a parent component specifies a render mode, the prerendering settings of its children are ignored.
 
 To disable prerendering for a *component instance*, pass the `prerender` flag with a value of `false` to the render mode: