From 1f4b9e9620ffaa928f805378015c68c420aa6dba Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Tue, 9 Feb 2021 06:07:47 -0600
Subject: [PATCH] Clarify Blazor Server's C# execution location (#21481)

---
 aspnetcore/blazor/index.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/aspnetcore/blazor/index.md b/aspnetcore/blazor/index.md
index 44a998e90c..edab211b72 100644
--- a/aspnetcore/blazor/index.md
+++ b/aspnetcore/blazor/index.md
@@ -131,8 +131,9 @@ The size of the published app, its *payload size*, is a critical performance fac
 
 Blazor decouples component rendering logic from how UI updates are applied. *Blazor Server* provides support for hosting Razor components on the server in an ASP.NET Core app. UI updates are handled over a [SignalR](xref:signalr/introduction) connection.
 
-The runtime handles:
+The runtime stays on the server and handles:
 
+* Executing the app's C# code.
 * Sending UI events from the browser to the server.
 * Applying UI updates to the rendered component that are sent back by the server.