Updates

Author: guardrex

aspnetcore/blazor/fundamentals/signalr.md

@@ -534,8 +534,8 @@ The `components-reconnect-state-changed` event indicates a reconnection status c
 * `show`: The reconnection modal is shown.
 * `hide`: The reconnection model is closed.
 * `retrying`: Reconnect attempts are in progress.
-* `failed`: A reconnection attempt has failed.
-* `rejected`: A reconnection attempt was received but rejected.
+* `failed`: A reconnection attempt failed.
+* `rejected`: A reconnection attempt was received by the server but rejected.
 
 The following table describes the CSS classes applied to the `components-reconnect-modal` element. The **Event** column represents the value of the matching `components-reconnect-state-changed` JavaScript event.
 
@@ -549,25 +549,25 @@ The following table describes the CSS classes applied to the `components-reconne
 
 Additional CSS classes to further control the style of rendered elements is described in the following table. The **Event** column represents the value of the matching `components-reconnect-state-changed` JavaScript event.
 
-| CSS class | Event | Indicates… |
+| CSS class | Event | Displayed on… |
 | --- | --- | --- |
-| `components-reconnect-first-attempt-visible` | `retrying` | Displayed on the first retry attempt. |
-| `components-reconnect-repeated-attempt-visible` | `retrying` | Displayed on the subsequent retry attempts. |
-| `components-reconnect-failed-visible` | `failed`/`rejected` | Displayed when reconnection attempts have failed or a reconnection attempt has been rejected. |
+| `components-reconnect-first-attempt-visible` | `retrying` | The first retry attempt. |
+| `components-reconnect-repeated-attempt-visible` | `retrying` | Subsequent retry attempts. |
+| `components-reconnect-failed-visible` | `failed`/`rejected` | Reconnection attempts that have failed or been rejected. |
 
-To display the maximum number of reconnect retries, define an element with an `id` of `components-reconnect-max-retries`:
+An element with an `id` of `components-reconnect-max-retries` displays the maximum number of reconnect retries:
 
 ```html
 <span id="components-reconnect-max-retries"></span>
 ```
 
-To display the current reconnect attempt, define an element with an `id` of `components-reconnect-current-attempt`:
+An element with an `id` of `components-reconnect-current-attempt` displays the current reconnect attempt:
 
 ```html
 <span id="components-reconnect-current-attempt"></span>
 ```
 
-To display the number of seconds to the next reconnection attempt, define an element with an `id` of `components-seconds-to-next-attempt`:
+An element with an `id` of `components-seconds-to-next-attempt` displays the number of seconds to the next reconnection attempt:
 
 ```html
 <span id="components-seconds-to-next-attempt"></span>

aspnetcore/release-notes/aspnetcore-10/includes/blazor.md

@@ -36,14 +36,14 @@ The [`[Route]` attribute](xref:Microsoft.AspNetCore.Components.RouteAttribute) n
 
 Previously, <xref:Microsoft.AspNetCore.Components.NavigationManager.NavigateTo%2A?displayProperty=nameWithType> scrolled to the top of the page for same-page navigations. This behavior has been changed in .NET 10 so that the browser no longer scrolls to the top of the page when navigating to the same page. This means the viewport is no longer reset when making updates to the address for the current page, such as changing the query string or fragment.
 
-### Reconnection UI component added to the Blazor Web App template
+### Reconnection UI component added to the Blazor Web App project template
 
-The Blazor Web App project template now includes a `ReconnectModal` component, including collocated stylesheet and JavaScript files, for improved developer control over the reconnection UI when the client loses the WebSocket connection to the server. The component isn't required to inline styles programatically, so it doesn't violate stricter Content Security Policy (CSP) settings for the `style-src` policy, thus avoiding CSP violations that faced the reconnection UI in prior releases.
+The Blazor Web App project template now includes a `ReconnectModal` component, including collocated stylesheet and JavaScript files, for improved developer control over the reconnection UI when the client loses the WebSocket connection to the server. The component isn't required to inline styles programatically, so it doesn't violate stricter Content Security Policy (CSP) settings for the `style-src` policy, thus avoiding CSP violations that occurred with the reconnection UI in prior releases.
 
 New reconnection UI features:
 
-* Apart from indicating the reconnection state by setting a specific CSS class on the element with the `components-reconnect-modal` ID, it also dispatches a custom event in `components-reconnect-state-changed` that can be listened for on the modal element.
-* The new reconnection state `retrying` is indicated by both a CSS class and the custom event, so that code can better differentiate the stages of the reconnection process.
+* Apart from indicating the reconnection state by setting a specific CSS class on the reconnection UI element, the new `components-reconnect-state-changed` event is dispatched for reconnection state changes.
+* Code can better differentiate the stages of the reconnection process with the new reconnection state "`retrying`," indicated by both the CSS class and the new event.
 
 For more information, see <xref:blazor/fundamentals/signalr?view=aspnetcore-10.0#reflect-the-server-side-connection-state-in-the-ui>.