From 05efb4c9cf7d793e7635e6e6e761eaa2676f7df2 Mon Sep 17 00:00:00 2001
From: TheCool <53025128+TheOnlyCool1@users.noreply.github.com>
Date: Fri, 21 Jun 2024 00:10:38 -0700
Subject: [PATCH] Update scene_organization.rst

---
 tutorials/best_practices/scene_organization.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tutorials/best_practices/scene_organization.rst b/tutorials/best_practices/scene_organization.rst
index 274962794..d05771fb4 100644
--- a/tutorials/best_practices/scene_organization.rst
+++ b/tutorials/best_practices/scene_organization.rst
@@ -238,7 +238,7 @@ is the next best thing. Inevitably, changes may need to be made to a class and
 if these changes cause it to interact with other scenes in unforeseen ways,
 then things will start to break down. The whole point of all this indirection
 is to avoid ending up in a situation where changing one class results in
-adversely effecting other classes dependent on it.
+adversely affecting other classes dependent on it.
 
 Scripts and scenes, as extensions of engine classes, should abide
 by *all* OOP principles. Examples include...