refactor: Remove unnecessary Blazor web app configuration from localization examples

docs/en/Community-Articles/2026-03-29-Url-Based-Localization/POST.md

@@ -143,11 +143,6 @@ Normal page-to-page navigation (within the same language) remains client-side an
 ### Example module configuration
 
 ```csharp
-PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
-{
-    options.IsBlazorWebApp = true;
-});
-
 Configure<AbpRequestLocalizationOptions>(options =>
 {
     options.UseRouteBasedCulture = true;

docs/en/framework/fundamentals/url-based-localization.md

@@ -143,11 +143,6 @@ Blazor Server uses SignalR (WebSocket) for the interactive circuit. The HTTP mid
 ### Example module configuration
 
 ````csharp
-PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
-{
-    options.IsBlazorWebApp = true;
-});
-
 Configure<AbpRequestLocalizationOptions>(options =>
 {
     options.UseRouteBasedCulture = true;
@@ -188,11 +183,6 @@ Same as Blazor Server — you must manually add `@page "/{culture}/..."` routes
 
 ````csharp
 // Server project
-PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
-{
-    options.IsBlazorWebApp = true;
-});
-
 Configure<AbpRequestLocalizationOptions>(options =>
 {
     options.UseRouteBasedCulture = true;