From db3d171e2ba49ec9260bd11344ddd087bf25a701 Mon Sep 17 00:00:00 2001
From: Mark Davis <311063+markdav-is@users.noreply.github.com>
Date: Thu, 4 Sep 2025 16:07:49 -0700
Subject: [PATCH] Update instructions/oqtane.instructions.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 instructions/oqtane.instructions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/instructions/oqtane.instructions.md b/instructions/oqtane.instructions.md
index ae81c3e..f4722fd 100644
--- a/instructions/oqtane.instructions.md
+++ b/instructions/oqtane.instructions.md
@@ -62,7 +62,7 @@ applyTo: '**/*.razor, **/*.razor.cs, **/*.razor.css'
 ## State Management Libraries
 
 - Use Blazor's built-in Cascading Parameters and EventCallbacks for basic state sharing across components.
-- use built-in Oqtane state management in the base classes like PageSate and SiteState when appripriate.
+- use built-in Oqtane state management in the base classes like PageState and SiteState when appropriate.
 - Avoid adding extra depenencies like Fluxor or BlazorState when the application grows in complexity.
 - For client-side state persistence in Blazor WebAssembly, consider using Blazored.LocalStorage or Blazored.SessionStorage to maintain state between page reloads.
 - For server-side Blazor, use Scoped Services and the StateContainer pattern to manage state within user sessions while minimizing re-renders.