diff --git a/aspnetcore/blazor/state-management.md b/aspnetcore/blazor/state-management.md
index 97b9e56f87..3ac6b77b1a 100644
--- a/aspnetcore/blazor/state-management.md
+++ b/aspnetcore/blazor/state-management.md
@@ -451,6 +451,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
 * To consume state across many components.
 * If there's just one top-level state object to persist.
 
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
 <h2 id="in-memory-state-container-service-wasm">In-memory state container service</h2>
 
 [!INCLUDE[](~/blazor/includes/state-container.md)]
@@ -896,6 +898,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
 * To consume state across many components.
 * If there's just one top-level state object to persist.
 
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
 <h2 id="in-memory-state-container-service-wasm">In-memory state container service</h2>
 
 [!INCLUDE[](~/blazor/includes/state-container.md)]
@@ -1356,6 +1360,8 @@ When implementing custom browser state storage, a useful approach is to adopt [c
 * To consume state across many components.
 * If there's just one top-level state object to persist.
 
+For additional discussion and example approaches, see [Blazor: In-memory state container as cascading parameter (dotnet/AspNetCore.Docs #27296)](https://github.com/dotnet/AspNetCore.Docs/issues/27296).
+
 <h2 id="in-memory-state-container-service-wasm">In-memory state container service</h2>
 
 [!INCLUDE[](~/blazor/includes/state-container.md)]