Updates

Author: guardrex

aspnetcore/blazor/components/integration-hosted-webassembly.md

@@ -1064,7 +1064,6 @@ The persisted prerendered state is transferred to the client, where it's used to
 
 ## Additional Blazor WebAssembly resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
 * [Prerendering support with assembly lazy loading](xref:blazor/webassembly-lazy-load-assemblies#lazy-load-assemblies-in-a-hosted-blazor-webassembly-solution)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)

aspnetcore/blazor/state-management/index.md

@@ -157,7 +157,7 @@ Root-level cascading values with a <xref:Microsoft.AspNetCore.Components.Cascadi
 
 :::moniker-end
 
-## Troubleshoot
+## Support state modifications from outside Blazor's synchronization context
 
 When using a custom state management service where you want to support state modifications from outside Blazor's synchronization context (for example from a timer or a background service), all consuming components must wrap the <xref:Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged%2A> call in <xref:Microsoft.AspNetCore.Components.ComponentBase.InvokeAsync%2A?displayProperty=nameWithType>. This ensures the change notification is handled on the renderer's synchronization context.