From 6e93aa5c53124629115179b39de8a088d910a889 Mon Sep 17 00:00:00 2001 From: axekan <50769262+axekan@users.noreply.github.com> Date: Tue, 21 Feb 2023 15:30:04 +0100 Subject: [PATCH] Fix typo in Blazor error handling docs (#28466) --- aspnetcore/blazor/fundamentals/handle-errors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/fundamentals/handle-errors.md b/aspnetcore/blazor/fundamentals/handle-errors.md index 7f37875f9d..568baaae6f 100644 --- a/aspnetcore/blazor/fundamentals/handle-errors.md +++ b/aspnetcore/blazor/fundamentals/handle-errors.md @@ -593,7 +593,7 @@ In prerendered Blazor WebAssembly, prerendering works by: If a component throws an unhandled exception during prerendering, for example, during a lifecycle method or in rendering logic: -* In Blazor Sever apps, the exception is fatal to the circuit. In prerendered Blazor WebAssembly apps, the exception prevents rendering the component. +* In Blazor Server apps, the exception is fatal to the circuit. In prerendered Blazor WebAssembly apps, the exception prevents rendering the component. * The exception is thrown up the call stack from the . Under normal circumstances when prerendering fails, continuing to build and render the component doesn't make sense because a working component can't be rendered.