Skip to content

Commit b8c88e1

Browse files
authored
Add context to introductory remarks (#34826)
1 parent 6fbabbb commit b8c88e1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

aspnetcore/blazor/components/render-components-outside-of-aspnetcore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ uid: blazor/components/render-outside-of-aspnetcore
1212

1313
[!INCLUDE[](~/includes/not-latest-version-without-not-supported-content.md)]
1414

15-
Razor components can be rendered outside of the context of an HTTP request. You can render Razor components as HTML directly to a string or stream independently of the ASP.NET Core hosting environment. This is convenient for scenarios where you want to generate HTML fragments, such as for generating email content, generating static site content, or for building a content templating engine.
15+
[Razor components](xref:blazor/components/index), which are self-contained portions of user interface (UI) with processing logic used in [ASP.NET Core Blazor](xref:blazor/index), can be rendered outside of the context of an HTTP request. You can render Razor components as HTML directly to a string or stream independently of the ASP.NET Core hosting environment. This is convenient for scenarios where you want to generate HTML fragments, such as for generating email content, generating static site content, or for building a content templating engine.
1616

1717
In the following example, a Razor component is rendered to an HTML string from a console app:
1818

0 commit comments

Comments
 (0)