From ef37a703f3e48e34bf4a45c2a4a9f2f20926e022 Mon Sep 17 00:00:00 2001 From: Robert Haken Date: Fri, 29 Nov 2024 01:06:30 +0100 Subject: [PATCH] [Blazor] webassembly-lazy-load-assemblies - code --- aspnetcore/blazor/webassembly-lazy-load-assemblies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/webassembly-lazy-load-assemblies.md b/aspnetcore/blazor/webassembly-lazy-load-assemblies.md index 966d788c6ab6..19dca5b0b42e 100644 --- a/aspnetcore/blazor/webassembly-lazy-load-assemblies.md +++ b/aspnetcore/blazor/webassembly-lazy-load-assemblies.md @@ -71,7 +71,7 @@ Blazor's component designa Logic is implemented inside to determine the assemblies to load with . Options for how to structure the logic include: * Conditional checks inside the method. -* A lookup table that maps routes to assembly names, either injected into the component or implemented within the [`@code`](xref:mvc/views/razor#code) block. +* A lookup table that maps routes to assembly names, either injected into the component or implemented within the component's code. In the following example: