diff --git a/aspnetcore/blazor/globalization-localization.md b/aspnetcore/blazor/globalization-localization.md
index fed2cced2f2d..8f7d0064d06e 100644
--- a/aspnetcore/blazor/globalization-localization.md
+++ b/aspnetcore/blazor/globalization-localization.md
@@ -1,10 +1,11 @@
 ---
 title: ASP.NET Core Blazor globalization and localization
+ai-usage: ai-assisted
 author: guardrex
 description: Learn how to render globalized and localized content to users in different cultures and languages.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: wpickett
-ms.date: 11/11/2025
+ms.date: 08/26/2026
 uid: blazor/globalization-localization
 ---
 # ASP.NET Core Blazor globalization and localization
@@ -276,6 +277,8 @@ Optionally, add a menu item to the navigation in the `NavMenu` component (`NavMe
 
 ## Dynamically set the culture from the `Accept-Language` header
 
+*This section applies to server-side and client-side Blazor apps.*
+
 Add the [`Microsoft.Extensions.Localization` package](https://www.nuget.org/packages/Microsoft.Extensions.Localization) to the app.
 
 The [`Accept-Language` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Accept-Language) is set by the browser and controlled by the user's language preferences in browser settings. In browser settings, a user sets one or more preferred languages in order of preference. The order of preference is used by the browser to set quality values (`q`, 0-1) for each language in the header. The following example specifies United States English, English, and Costa Rican Spanish with a preference for United States English or English:
@@ -370,6 +373,18 @@ When the culture is Costa Rican Spanish (`es-CR`), the rendered component uses d
 
 ## Statically set the client-side culture
 
+:::moniker range=">= aspnetcore-8.0"
+
+*This section applies to Blazor WebAssembly apps and Blazor Web App components that adopt the Interactive WebAssembly render mode.*
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-8.0"
+
+*This section applies to Blazor WebAssembly apps.*
+
+:::moniker-end
+
 :::moniker range=">= aspnetcore-5.0"
 
 Set the `BlazorWebAssemblyLoadAllGlobalizationData` property to `true` in the app's project file (`.csproj`):
@@ -390,7 +405,7 @@ The Intermediate Language (IL) Linker configuration for client-side rendering st
 
 The app's culture can be set in JavaScript when Blazor starts with the `applicationCulture` Blazor start option. The following example configures the app to launch using the United States English (`en-US`) culture.
 
-Prevent Blazor autostart by adding `autostart="false"` to [Blazor's `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script):
+Prevent Blazor autostart by adding `autostart="false"` to the [Blazor `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script):
 
 ```html
 <script src="{BLAZOR SCRIPT}" autostart="false"></script>
@@ -398,7 +413,7 @@ Prevent Blazor autostart by adding `autostart="false"` to [Blazor's `<script>` t
 
 **In the preceding example, the `{BLAZOR SCRIPT}` placeholder is the Blazor script path and file name.** For the location of the script, see <xref:blazor/project-structure#location-of-the-blazor-script>.
 
-Add the following `<script>` block after [Blazor's `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script) and before the closing `</body>` tag:
+Add the following `<script>` block after the [Blazor `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script) and before the closing `</body>` tag:
 
 :::moniker range=">= aspnetcore-8.0 < aspnetcore-11.0"
 
@@ -466,6 +481,18 @@ Use the `CultureExample1` component shown in the [Demonstration component](#demo
 
 ## Statically set the server-side culture
 
+:::moniker range=">= aspnetcore-8.0"
+
+*This section applies to Blazor Web App components that adopt the Interactive Server render mode and Blazor Server apps.*
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-8.0"
+
+*This section applies to Blazor Server apps.*
+
+:::moniker-end
+
 :::moniker range=">= aspnetcore-6.0"
 
 Server-side apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with <xref:Microsoft.Extensions.DependencyInjection.LocalizationServiceCollectionExtensions.AddLocalization%2A>.
@@ -528,6 +555,18 @@ Use the `CultureExample1` component shown in the [Demonstration component](#demo
 
 ## Dynamically set the client-side culture by user preference
 
+:::moniker range=">= aspnetcore-8.0"
+
+*This section applies to Blazor WebAssembly apps and Blazor Web App components that adopt the Interactive WebAssembly render mode.*
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-8.0"
+
+*This section applies to Blazor WebAssembly apps.*
+
+:::moniker-end
+
 Examples of locations where an app might store a user's preference include in [browser local storage](https://developer.mozilla.org/docs/Web/API/Window/localStorage) (common for client-side scenarios), in a localization cookie or database (common for server-side scenarios), or in an external service attached to an external database and accessed by a [web API](xref:blazor/call-web-api). The following example demonstrates how to use browser local storage.
 
 Add the [`Microsoft.Extensions.Localization` package](https://www.nuget.org/packages/Microsoft.Extensions.Localization) to the app.
@@ -548,7 +587,7 @@ Set the `BlazorWebAssemblyLoadAllGlobalizationData` property to `true` in the pr
 
 The app's culture for client-side rendering is set using the Blazor framework's API. A user's culture selection can be persisted in browser local storage.
 
-Provide JS functions after [Blazor's `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script) to get and set the user's culture selection with browser local storage:
+Provide JS functions after the [Blazor `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script) to get and set the user's culture selection with browser local storage:
 
 ```html
 <script>
@@ -653,9 +692,10 @@ The following `CultureSelector` component shows how to perform the following act
 
     private async Task ApplySelectedCultureAsync()
     {
-        if (CultureInfo.CurrentCulture != selectedCulture)
+        if (selectedCulture is not null &&
+            CultureInfo.CurrentCulture != selectedCulture)
         {
-            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture!.Name);
+            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture.Name);
 
             Navigation.NavigateTo(Navigation.Uri, forceLoad: true);
         }
@@ -703,9 +743,10 @@ The following `CultureSelector` component shows how to perform the following act
     {
         selectedCulture = CultureInfo.GetCultureInfo((string)args.Value!);
 
-        if (CultureInfo.CurrentCulture != selectedCulture)
+        if (selectedCulture is not null &&
+            CultureInfo.CurrentCulture != selectedCulture)
         {
-            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture!.Name);
+            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture.Name);
 
             Navigation.NavigateTo(Navigation.Uri, forceLoad: true);
         }
@@ -718,33 +759,30 @@ The following `CultureSelector` component shows how to perform the following act
 > [!NOTE]
 > For more information on <xref:Microsoft.JSInterop.IJSInProcessRuntime>, see <xref:blazor/js-interop/call-javascript-from-dotnet#invoke-javascript-functions-without-reading-a-returned-value-invokevoidasync>.
 
-Inside the closing tag of the `</main>` element in the `MainLayout` component (`MainLayout.razor`), add the `CultureSelector` component:
+In the header markup of the `MainLayout` component (`MainLayout.razor`), add the `CultureSelector` component:
 
 ```razor
-<article class="bottom-row px-4">
-    <CultureSelector />
-</article>
+<CultureSelector />
 ```
 
 Use the `CultureExample1` component shown in the [Demonstration component](#demonstration-component) section to study how the preceding example works.
 
 ## Dynamically set the server-side culture by user preference
 
-Examples of locations where an app might store a user's preference include in [browser local storage](https://developer.mozilla.org/docs/Web/API/Window/localStorage) (common for client-side scenarios), in a localization cookie or database (common for server-side scenarios), or in an external service attached to an external database and accessed by a [web API](xref:blazor/call-web-api). The following example demonstrates how to use a localization cookie.
-
 :::moniker range=">= aspnetcore-8.0"
 
-> [!NOTE]
-> The following example assumes that the app adopts ***global*** interactivity by specifying the interactive server-side rendering (interactive SSR) on the `Routes` component in the `App` component (`Components/App.razor`):
->
-> ```razor
-> <Routes @rendermode="InteractiveServer" />
-> ```
->
-> If the app adopts ***per-page/component*** interactivity, see the remarks at the end of this section to modify the render modes of the example's components.
+*This section applies to Blazor Web Apps adopting the global Interactive Server render mode and Blazor Server apps. For guidance that covers a Blazor Web App adopting per-page/component interactivity, see the [Dynamically set the culture in a Blazor Web App by user preference](#dynamically-set-the-culture-in-a-blazor-web-app-by-user-preference) section.*
 
 :::moniker-end
 
+:::moniker range="< aspnetcore-8.0"
+
+*This section applies to Blazor Server apps.*
+
+:::moniker-end
+
+Examples of locations where an app might store a user's preference include in [browser local storage](https://developer.mozilla.org/docs/Web/API/Window/localStorage) (common for client-side scenarios), in a localization cookie or database (common for server-side scenarios), or in an external service attached to an external database and accessed by a [web API](xref:blazor/call-web-api). The following example demonstrates how to use a localization cookie.
+
 Add the [`Microsoft.Extensions.Localization` package](https://www.nuget.org/packages/Microsoft.Extensions.Localization) to the app.
 
 [!INCLUDE[](~/includes/package-reference.md)]
@@ -792,7 +830,7 @@ The following namespaces are required for the `App` component:
 * <xref:System.Globalization?displayProperty=fullName>
 * <xref:Microsoft.AspNetCore.Localization?displayProperty=fullName>
 
-Add the following to the top of the `App` component file (`Components/App.razor`):
+Add the <xref:System.Globalization?displayProperty=fullName> and <xref:Microsoft.AspNetCore.Localization?displayProperty=fullName> namespaces to the top of the `App` component file (`Components/App.razor`):
 
 ```razor
 @using System.Globalization
@@ -827,7 +865,7 @@ Modifications to the `Pages/_Host.cshtml` file require the following namespaces:
 * <xref:System.Globalization?displayProperty=fullName>
 * <xref:Microsoft.AspNetCore.Localization?displayProperty=fullName>
 
-Add the following to the file:
+Add the following Razor markup to the file:
 
 ```cshtml
 @using System.Globalization
@@ -846,6 +884,41 @@ Add the following to the file:
 
 For information on ordering the localization middleware in the middleware pipeline, see <xref:fundamentals/middleware/index#middleware-order>.
 
+:::moniker range=">= aspnetcore-6.0"
+
+To provide UI to allow a user to select a culture, use a *redirect-based approach* with a localization cookie. The app persists the user's selected culture via a redirect to a Minimal API endpoint. The endpoint sets the user's selected culture into a cookie and redirects the user back to the original URI. The process is similar to what happens in a web app when a user attempts to access a secure resource, where the user is redirected to a sign-in page and then redirected back to the original resource.
+
+At the top of the `Program` file, add the following `using` statement for the required namespace:
+
+```csharp
+using Microsoft.AspNetCore.Localization;
+```
+
+In the request processing pipeline of the app's `Program` file after the call to <xref:Microsoft.AspNetCore.Builder.ApplicationBuilderExtensions.UseRequestLocalization%2A>:
+
+```csharp
+app.MapGet("/Culture/Set", (string? culture, string redirectUri = "/",
+    HttpContext context) =>
+{
+    if (!string.IsNullOrWhiteSpace(culture))
+    {
+        context.Response.Cookies.Append(
+            CookieRequestCultureProvider.DefaultCookieName,
+            CookieRequestCultureProvider.MakeCookieValue(
+                new RequestCulture(culture, culture)));
+    }
+
+    return Results.LocalRedirect(redirectUri);
+});
+```
+
+> [!WARNING]
+> Use the <xref:Microsoft.AspNetCore.Http.Results.LocalRedirect%2A> result, as shown in the preceding example, to prevent open redirect attacks. For more information, see <xref:security/preventing-open-redirects>.
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-6.0"
+
 If the app isn't configured to process controller actions:
 
 * Add MVC services by calling <xref:Microsoft.Extensions.DependencyInjection.MvcServiceCollectionExtensions.AddControllers%2A> on the service collection in the `Program` file:
@@ -889,9 +962,23 @@ public class CultureController : Controller
 > [!WARNING]
 > Use the <xref:Microsoft.AspNetCore.Mvc.ControllerBase.LocalRedirect%2A> action result, as shown in the preceding example, to prevent open redirect attacks. For more information, see <xref:security/preventing-open-redirects>.
 
-The following `CultureSelector` component shows how to call the `Set` method of the `CultureController` with the new culture. The component is placed in the `Shared` folder for use throughout the app.
+:::moniker-end
 
-`CultureSelector.razor`:
+:::moniker range=">= aspnetcore-8.0"
+
+The following `CultureSelector` component shows how to call the `Set` endpoint with the new culture. The component is placed in the `Components` folder for use throughout the app.
+
+`Components/CultureSelector.razor`:
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-8.0"
+
+The following `CultureSelector` component shows how to call the `Set` endpoint with the new culture. The component is placed in the `Shared` folder for use throughout the app.
+
+`Shared/CultureSelector.razor`:
+
+:::moniker-end
 
 :::moniker range=">= aspnetcore-7.0"
 
@@ -929,7 +1016,8 @@ The following `CultureSelector` component shows how to call the `Set` method of
 
     private async Task ApplySelectedCultureAsync()
     {
-        if (CultureInfo.CurrentCulture != selectedCulture)
+        if (selectedCulture is not null &&
+            CultureInfo.CurrentCulture != selectedCulture)
         {
             var uri = new Uri(Navigation.Uri)
                 .GetComponents(UriComponents.PathAndQuery, UriFormat.Unescaped);
@@ -984,7 +1072,8 @@ The following `CultureSelector` component shows how to call the `Set` method of
     {
         selectedCulture = CultureInfo.GetCultureInfo((string)args.Value!);
 
-        if (CultureInfo.CurrentCulture != selectedCulture)
+        if (selectedCulture is not null &&
+            CultureInfo.CurrentCulture != selectedCulture)
         {
             var uri = new Uri(Navigation.Uri)
                 .GetComponents(UriComponents.PathAndQuery, UriFormat.Unescaped);
@@ -1001,22 +1090,22 @@ The following `CultureSelector` component shows how to call the `Set` method of
 
 :::moniker-end
 
+Add the `CultureSelector` component to the `MainLayout` component. 
+
 :::moniker range=">= aspnetcore-8.0"
 
-Add the `CultureSelector` component to the `MainLayout` component. Place the following markup inside the closing `</main>` tag in the `Components/Layout/MainLayout.razor` file:
+In the header markup of `Components/Layout/MainLayout.razor`:
 
 :::moniker-end
 
 :::moniker range="< aspnetcore-8.0"
 
-Add the `CultureSelector` component to the `MainLayout` component. Place the following markup inside the closing `</main>` tag in the `Shared/MainLayout.razor` file:
+In the header markup of `Shared/MainLayout.razor`:
 
 :::moniker-end
 
 ```razor
-<article class="bottom-row px-4">
-    <CultureSelector />
-</article>
+<CultureSelector />
 ```
 
 Use the `CultureExample1` component shown in the [Demonstration component](#demonstration-component) section to study how the preceding example works.
@@ -1029,7 +1118,7 @@ The preceding example assumes that the app adopts ***global*** interactivity by
 <Routes @rendermode="InteractiveServer" />
 ```
 
-If the app adopts ***per-page/component*** interactivity, make the following changes:
+If the app adopts ***per-page/component*** interactivity and only server-side components provide culture selection UI, make the following changes:
 
 * Add the Interactive Server render mode to the top of the `CultureExample1` component file (`Components/Pages/CultureExample1.razor`):
 
@@ -1049,9 +1138,9 @@ If the app adopts ***per-page/component*** interactivity, make the following cha
 
 ## Dynamically set the culture in a Blazor Web App by user preference
 
-*This section applies to Blazor Web Apps that adopt Auto (Server and WebAssembly) interactivity.*
+*This section applies to Blazor Web Apps that adopt per-page/component interactivity.*
 
-Examples of locations where an app might store a user's preference include in [browser local storage](https://developer.mozilla.org/docs/Web/API/Window/localStorage) (common for client-side scenarios), in a localization cookie or database (common for server-side scenarios), both local storage and a localization cookie (Blazor Web Apps with server and WebAssembly components), or in an external service attached to an external database and accessed by a [web API](xref:blazor/call-web-api). The following example demonstrates how to use browser local storage for client-side rendered (CSR) components and a localization cookie for server-side rendered (SSR) components.
+Examples of locations where an app might store a user's preference include in [browser local storage](https://developer.mozilla.org/docs/Web/API/Window/localStorage) (common for client-side scenarios), in a localization cookie or database (common for server-side scenarios), both local storage and a localization cookie (Blazor Web Apps with server and WebAssembly components), or in an external service attached to an external database and accessed by a [web API](xref:blazor/call-web-api). The following example demonstrates how to use browser local storage for client-side rendered (CSR) components and a localization cookie for server-side rendered (SSR) components. The guidance in this section also works for components in apps that adopt per-page/component rendering and specify the Interactive Auto render mode (`@rendermode InteractiveAuto`).
 
 ### Updates to the `.Client` project
 
@@ -1115,14 +1204,11 @@ await host.RunAsync();
 
 :::moniker range=">= aspnetcore-8.0"
 
-Add the following `CultureSelector` component to the `.Client` project.
-
-The component adopts the following approaches to work for either SSR or CSR components:
+Add the following `CultureSelector` component to the `.Client` project in a `Shared` folder. If a `Shared` folder doesn't exist in the `.Client` project, create one to hold shared components. 
 
-* The display name of each available culture in the dropdown list is provided by a dictionary because client-side globalization data include localized text of culture display names that server-side globalization data provides. For example, server-side localization displays `English (United States)` when `en-US` is the culture and `Ingles ()` when a different culture is used. Because localization of the culture display names isn't available with Blazor WebAssembly globalization, the display name for United States English on the client for any loaded culture is just `en-US`. Using a custom dictionary permits the component to at least display full English culture names.
-* When user changes the culture, JS interop sets the culture in local browser storage and a controller action updates the localization cookie with the culture. The controller is added to the app later in the [Server project updates](#server-project-updates) section.
+When the user changes the culture, JS interop sets the culture in local browser storage and a Minimal API endpoint updates the localization cookie with the culture. The Minimal API endpoint is added to the app later in the [Server project updates](#server-project-updates) section.
 
-`Pages/CultureSelector.razor`:
+`Shared/CultureSelector.razor`:
 
 ```razor
 @using System.Globalization
@@ -1135,7 +1221,7 @@ The component adopts the following approaches to work for either SSR or CSR comp
         <select @bind="@selectedCulture" @bind:after="ApplySelectedCultureAsync">
             @foreach (var culture in supportedCultures)
             {
-                <option value="@culture">@cultureDict[culture.Name]</option>
+                <option value="@culture">@culture.DisplayName</option>
             }
         </select>
     </label>
@@ -1143,13 +1229,6 @@ The component adopts the following approaches to work for either SSR or CSR comp
 
 @code
 {
-    private Dictionary<string, string> cultureDict = 
-        new()
-        {
-            { "en-US", "English (United States)" },
-            { "es-CR", "Spanish (Costa Rica)" }
-        };
-
     private CultureInfo[] supportedCultures = 
         [ 
             new CultureInfo("en-US"), 
@@ -1165,9 +1244,10 @@ The component adopts the following approaches to work for either SSR or CSR comp
 
     private async Task ApplySelectedCultureAsync()
     {
-        if (CultureInfo.CurrentCulture != selectedCulture)
+        if (selectedCulture is not null &&
+            CultureInfo.CurrentCulture != selectedCulture)
         {
-            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture!.Name);
+            await JS.InvokeVoidAsync("blazorCulture.set", selectedCulture.Name);
 
             var uri = new Uri(Navigation.Uri)
                 .GetComponents(UriComponents.PathAndQuery, UriFormat.Unescaped);
@@ -1182,21 +1262,19 @@ The component adopts the following approaches to work for either SSR or CSR comp
 }
 ```
 
-In the `.Client` project's imports file (`_Imports.razor`), add the namespace for the components in the `Pages` folder, updating the namespace to match your `.Client` project's namespace:
+> [!NOTE]
+> For more information on <xref:Microsoft.JSInterop.IJSInProcessRuntime>, see <xref:blazor/js-interop/call-javascript-from-dotnet#invoke-javascript-functions-without-reading-a-returned-value-invokevoidasync>.
+
+In the server project's imports file (`_Imports.razor`), add the namespace for the `.Client` project's `Shared` folder (update the namespace to match your app):
 
 ```razor
-@using BlazorSample.Client.Pages
+@using BlazorSample.Client.Shared
 ```
 
-> [!NOTE]
-> For more information on <xref:Microsoft.JSInterop.IJSInProcessRuntime>, see <xref:blazor/js-interop/call-javascript-from-dotnet#invoke-javascript-functions-without-reading-a-returned-value-invokevoidasync>.
-
-In the `.Client` project, add the `CultureSelector` component to the `MainLayout` component. Place the following markup inside the closing `</main>` tag in the `Layout/MainLayout.razor` file:
+Place the following markup in the header content of the `Components/Layout/MainLayout.razor` file:
 
 ```razor
-<article class="bottom-row px-4">
-    <CultureSelector @rendermode="InteractiveAuto" />
-</article>
+<CultureSelector @rendermode="InteractiveAuto" />
 ```
 
 In the `.Client` project, place the following `CultureClient` component to study how globalization works for CSR components.
@@ -1309,9 +1387,13 @@ In the `.Client` project, place the following `CultureServer` component to study
 }
 ```
 
-Use the `CultureExample1` component shown in the [Demonstration component](#demonstration-component) section to study how globalization works for a component that inherits the global Auto render mode. Add the `CultureExample1` component to the `.Client` project's `Pages` folder.
+Use the `CultureExample1` component shown in the [Demonstration component](#demonstration-component) section to study how globalization works for a component that inherits the global Auto render mode. Add the `CultureExample1` component to the `.Client` project's `Pages` folder. At the top of the component, specify the Interactive Auto render mode:
 
-Add the `CultureClient`, `CultureServer`, and `CultureExample1` components to the sidebar navigation in `Layout/NavMenu.razor`:
+```razor
+@rendermode InteractiveAuto
+```
+
+Add the `CultureClient`, `CultureServer`, and `CultureExample1` components to the sidebar navigation in `Components/Layout/NavMenu.razor` of the server project:
 
 ```razor
 <div class="nav-item px-3">
@@ -1361,12 +1443,7 @@ app.UseRequestLocalization(localizationOptions);
 
 The following example shows how to set the current culture in a cookie that can be read by the localization middleware.
 
-The following namespaces are required for the `App` component:
-
-* <xref:System.Globalization?displayProperty=fullName>
-* <xref:Microsoft.AspNetCore.Localization?displayProperty=fullName>
-
-Add the following to the top of the `App` component file (`Components/App.razor`):
+Add the <xref:System.Globalization?displayProperty=fullName> and <xref:Microsoft.AspNetCore.Localization?displayProperty=fullName> namespaces to the top of the `App` component (`Components/App.razor`):
 
 ```razor
 @using System.Globalization
@@ -1375,7 +1452,7 @@ Add the following to the top of the `App` component file (`Components/App.razor`
 
 The app's culture for client-side rendering is set using the Blazor framework's API. A user's culture selection can be persisted in browser local storage for CSR components.
 
-After the [Blazor's `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script), provide JS functions to get and set the user's culture selection with browser local storage:
+After the [Blazor `<script>` tag](xref:blazor/project-structure#location-of-the-blazor-script), provide JS functions to get and set the user's culture selection with browser local storage:
 
 ```html
 <script>
@@ -1408,56 +1485,34 @@ Add the following `@code` block to the bottom of the `App` component file:
 }
 ```
 
-If the server project isn't configured to process controller actions:
-
-* Add MVC services by calling <xref:Microsoft.Extensions.DependencyInjection.MvcServiceCollectionExtensions.AddControllers%2A> on the service collection in the `Program` file:
-
-  ```csharp
-  builder.Services.AddControllers();
-  ```
-
-* Add controller endpoint routing in the `Program` file by calling <xref:Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.MapControllers%2A> on the <xref:Microsoft.AspNetCore.Routing.IEndpointRouteBuilder> (`app`):
+To provide UI to allow a user to select a culture, use a *redirect-based approach* with a localization cookie. The app persists the user's selected culture via a redirect to a Minimal API endpoint. The endpoint sets the user's selected culture into a cookie and redirects the user back to the original URI. The process is similar to what happens in a web app when a user attempts to access a secure resource, where the user is redirected to a sign-in page and then redirected back to the original resource.
 
-  ```csharp
-  app.MapControllers();
-  ```
-
-To allow a user to select a culture for SSR components, use a *redirect-based approach* with a localization cookie. The app persists the user's selected culture via a redirect to a controller. The controller sets the user's selected culture into a cookie and redirects the user back to the original URI. The process is similar to what happens in a web app when a user attempts to access a secure resource, where the user is redirected to a sign-in page and then redirected back to the original resource.
-
-`Controllers/CultureController.cs`:
+At the top of the `Program` file, add the following `using` statement for the required namespace:
 
 ```csharp
 using Microsoft.AspNetCore.Localization;
-using Microsoft.AspNetCore.Mvc;
+```
 
-[Route("[controller]/[action]")]
-public class CultureController : Controller
+In the request processing pipeline of the app's `Program` file after the call to <xref:Microsoft.AspNetCore.Builder.ApplicationBuilderExtensions.UseRequestLocalization%2A>:
+
+```csharp
+app.MapGet("/Culture/Set", (string? culture, string redirectUri = "/",
+    HttpContext context) =>
 {
-    public IActionResult Set(string culture, string redirectUri)
+    if (!string.IsNullOrWhiteSpace(culture))
     {
-        if (culture != null)
-        {
-            HttpContext.Response.Cookies.Append(
-                CookieRequestCultureProvider.DefaultCookieName,
-                CookieRequestCultureProvider.MakeCookieValue(
-                    new RequestCulture(culture, culture)));
-        }
-
-        return LocalRedirect(redirectUri);
+        context.Response.Cookies.Append(
+            CookieRequestCultureProvider.DefaultCookieName,
+            CookieRequestCultureProvider.MakeCookieValue(
+                new RequestCulture(culture, culture)));
     }
-}
+
+    return Results.LocalRedirect(redirectUri);
+});
 ```
 
 > [!WARNING]
-> Use the <xref:Microsoft.AspNetCore.Mvc.ControllerBase.LocalRedirect%2A> action result, as shown in the preceding example, to prevent open redirect attacks. For more information, see <xref:security/preventing-open-redirects>.
-
-### Interactive Auto components
-
-The guidance in this section also works for components in apps that adopt per-page/component rendering and specify the Interactive Auto render mode:
-
-```razor
-@rendermode InteractiveAuto
-```
+> Use the <xref:Microsoft.AspNetCore.Http.Results.LocalRedirect%2A> result, as shown in the preceding example, to prevent open redirect attacks. For more information, see <xref:security/preventing-open-redirects>.
 
 :::moniker-end
 
diff --git a/aspnetcore/security/preventing-open-redirects.md b/aspnetcore/security/preventing-open-redirects.md
index ec1a11b1db6c..086b687bf6c6 100644
--- a/aspnetcore/security/preventing-open-redirects.md
+++ b/aspnetcore/security/preventing-open-redirects.md
@@ -1,9 +1,10 @@
 ---
 title: Prevent open redirect attacks in ASP.NET Core
+ai-usage: ai-assisted
 author: ardalis
 description: Shows how to prevent open redirect attacks against an ASP.NET Core app
 ms.author: tdykstra
-ms.date: 07/07/2017
+ms.date: 08/26/2026
 uid: security/preventing-open-redirects
 ---
 # Prevent open redirect attacks in ASP.NET Core
@@ -39,7 +40,22 @@ When developing web applications, treat all user-provided data as untrustworthy.
 
 ### LocalRedirect
 
-Use the `LocalRedirect` helper method from the base `Controller` class:
+:::moniker range=">= aspnetcore-6.0"
+
+Use the <xref:Microsoft.AspNetCore.Http.Results.LocalRedirect%2A> result in a Minimal API endpoint:
+
+```csharp
+app.MapGet("/SomeEndpoint", (string redirectUri) =>
+{
+    ...
+    
+    return Results.LocalRedirect(redirectUri);
+});
+```
+
+:::moniker-end
+
+Use the <xref:Microsoft.AspNetCore.Mvc.ControllerBase.LocalRedirect%2A> helper method in MVC actions:
 
 ```csharp
 public IActionResult SomeAction(string redirectUrl)
@@ -48,7 +64,7 @@ public IActionResult SomeAction(string redirectUrl)
 }
 ```
 
-`LocalRedirect` will throw an exception if a non-local URL is specified. Otherwise, it behaves just like the `Redirect` method.
+`LocalRedirect` throws an exception if a non-local URL is specified. Otherwise, it behaves just like the `Redirect` method.
 
 ### IUrlHelper.IsLocalUrl