Skip to content

Commit 6dbb541

Browse files
authored
Merge pull request #35542 from erhanalankus/patch-2
1 parent 6b8c008 commit 6dbb541

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

aspnetcore/blazor/tooling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -544,7 +544,7 @@ Detailed guidance on render modes is provided by the <xref:blazor/components/ren
544544
* To enable both interactive rendering modes and the ability to automatically switch between them at runtime, use the **Auto (Server and WebAssembly)** (automatic) render mode option.
545545
* If interactivity is set to `None`, the generated app has no interactivity. The app is only configured for static server-side rendering.
546546

547-
The Interactive Auto render mode initially uses interactive SSR while the .NET app bundle and runtime are download to the browser. After the .NET WebAssembly runtime is activated, the render mode switches to Interactive WebAssembly rendering.
547+
The Interactive Auto render mode initially uses interactive SSR while the .NET app bundle and runtime are downloaded to the browser. After the .NET WebAssembly runtime is activated, the render mode switches to Interactive WebAssembly rendering.
548548

549549
The Blazor Web App template enables both static and interactive SSR using a single project. If you also enable CSR, the project includes an additional client project (`.Client`) for your WebAssembly-based components. The built output from the client project is downloaded to the browser and executed on the client. Any components using the WebAssembly or automatic render modes must be built from the client project.
550550

0 commit comments

Comments
 (0)