From 31aa4057bd5d6483566b4452a9cd3e44961c8d82 Mon Sep 17 00:00:00 2001
From: sealionnn <72611254+sealionnn@users.noreply.github.com>
Date: Wed, 24 Jun 2026 10:29:01 -0400
Subject: [PATCH] Fixed small typo in building_2d_games ch 19

---
 .../building_2d_games/19_user_interface_fundamentals/index.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/tutorials/building_2d_games/19_user_interface_fundamentals/index.md b/articles/tutorials/building_2d_games/19_user_interface_fundamentals/index.md
index 5bcda8d2..e73da67c 100644
--- a/articles/tutorials/building_2d_games/19_user_interface_fundamentals/index.md
+++ b/articles/tutorials/building_2d_games/19_user_interface_fundamentals/index.md
@@ -40,7 +40,7 @@ When designing and implementing game UI systems, developers must decide how UI e
 
 ## Parent-Child Relationships
 
-Parent-child relationships are a part of many UI system. This relationship is implemented with UI elements containing other UI elements, creating a tree-like structure. This hierarchial approach mirrors how interface elements naturally group together in designs.
+Parent-child relationships are a part of many UI systems. This relationship is implemented with UI elements containing other UI elements, creating a tree-like structure. This hierarchial approach mirrors how interface elements naturally group together in designs.
 
 For example, a settings panel might contain multiple buttons, labels, and sliders.  By making these elements children of the panel, they can be managed as a cohesive unit.  This organizational structure provides several significant advantages: