Blazor UE improvements (#18304)

Author: guardrex

aspnetcore/blazor/components.md

@@ -125,7 +125,7 @@ It's often convenient to close over additional values, such as when iterating ov
 
 ## EventCallback
 
-A common scenario with nested components is the desire to run a parent component's method when a child component event occurs—for example, when an `onclick` event occurs in the child. To expose events across components, use an `EventCallback`. A parent component can assign a callback method to a child component's `EventCallback`.
+A common scenario with nested components is the desire to run a parent component's method when a child component event occurs. An `onclick` event occurring in the child component is a common use case. To expose events across components, use an `EventCallback`. A parent component can assign a callback method to a child component's `EventCallback`.
 
 The `ChildComponent` in the sample app (*Components/ChildComponent.razor*) demonstrates how a button's `onclick` handler is set up to receive an `EventCallback` delegate from the sample's `ParentComponent`. The `EventCallback` is typed with `MouseEventArgs`, which is appropriate for an `onclick` event from a peripheral device:
 

aspnetcore/blazor/event-handling.md

@@ -81,7 +81,7 @@ Blazor Server is a stateful framework. While users interact with an app, they ma
 
 If a user opens the app in multiple browser tabs, they have multiple independent circuits.
 
-Blazor treats most unhandled exceptions as fatal to the circuit where they occur. If a circuit is terminated due to an unhandled exception, the user can only continue to interact with the app by reloading the page to create a new circuit. Circuits outside of the one that's terminated, which are circuits for other users or other browser tabs, aren't affected. This scenario is similar to a desktop app that crashes—the crashed app must be restarted, but other apps aren't affected.
+Blazor treats most unhandled exceptions as fatal to the circuit where they occur. If a circuit is terminated due to an unhandled exception, the user can only continue to interact with the app by reloading the page to create a new circuit. Circuits outside of the one that's terminated, which are circuits for other users or other browser tabs, aren't affected. This scenario is similar to a desktop app that crashes. The crashed app must be restarted, but other apps aren't affected.
 
 A circuit is terminated when an unhandled exception occurs for the following reasons:
 

aspnetcore/blazor/handle-errors.md

@@ -13,7 +13,7 @@ uid: blazor/layouts
 
 By [Rainer Stropek](https://www.timecockpit.com) and [Luke Latham](https://github.com/guardrex)
 
-Some app elements, such as menus, copyright messages, and company logos, are usually part of app's overall layout and used by every component in the app. Copying the code of these elements into all of the components of an app isn't an efficient approach—every time one of the elements requires an update, every component must be updated. Such duplication is difficult to maintain and can lead to inconsistent content over time. *Layouts* solve this problem.
+Some app elements, such as menus, copyright messages, and company logos, are usually part of app's overall layout and used by every component in the app. Copying the code of these elements into all of the components of an app isn't an efficient approach. Every time one of the elements requires an update, every component must be updated. Such duplication is difficult to maintain and can lead to inconsistent content over time. *Layouts* solve this problem.
 
 Technically, a layout is just another component. A layout is defined in a Razor template or in C# code and can use [data binding](xref:blazor/data-binding), [dependency injection](xref:blazor/dependency-injection), and other component scenarios.
 

aspnetcore/blazor/layouts.md

@@ -19,7 +19,7 @@ Blazor Server is a stateful app framework. Most of the time, the app maintains a
 
 Examples of state held for a user's circuit include:
 
-* The rendered UI—the hierarchy of component instances and their most recent render output.
+* The rendered UI: The hierarchy of component instances and their most recent render output.
 * The values of any fields and properties in component instances.
 * Data held in [dependency injection (DI)](xref:fundamentals/dependency-injection) service instances that are scoped to the circuit.
 
@@ -45,7 +45,7 @@ In some scenarios, preserving state across circuits is desirable. An app can ret
 
 In general, maintaining state across circuits applies to scenarios where users are actively creating data, not simply reading data that already exists.
 
-To preserve state beyond a single circuit, *don't merely store the data in the server's memory*. The app must persist the data to some other storage location. State persistence isn't automatic—you must take steps when developing the app to implement stateful data persistence.
+To preserve state beyond a single circuit, *don't merely store the data in the server's memory*. The app must persist the data to some other storage location. State persistence isn't automatic. You must take steps when developing the app to implement stateful data persistence.
 
 Data persistence is typically only required for high-value state that users have expended effort to create. In the following examples, persisting state either saves time or aids in commercial activities:
 
@@ -88,7 +88,7 @@ For transient data representing navigation state, model the data as a part of th
 The contents of the browser's address bar are retained:
 
 * If the user manually reloads the page.
-* If the web server becomes unavailable—the user is forced to reload the page in order to connect to a different server.
+* If the web server becomes unavailable, and the user is forced to reload the page in order to connect to a different server.
 
 For information on defining URL patterns with the `@page` directive, see <xref:blazor/routing>.
 

aspnetcore/blazor/state-management.md

@@ -704,6 +704,8 @@ In [Razor components](xref:blazor/components), `@using` also controls which comp
 
 ## Directive attributes
 
+Razor directive attributes are represented by implicit expressions with reserved keywords following the `@` symbol. A directive attribute typically changes the way an element is parsed or enables different functionality.
+
 ### \@attributes
 
 *This scenario only applies to Razor components (.razor).*