From 1426a11449e5295ad0e2a993135a49ea0359f12d Mon Sep 17 00:00:00 2001
From: AV77 <58653231+AV77@users.noreply.github.com>
Date: Thu, 11 May 2023 14:27:29 +0000
Subject: [PATCH] Fixed minor grammatical error

---
 tutorials/best_practices/scene_organization.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tutorials/best_practices/scene_organization.rst b/tutorials/best_practices/scene_organization.rst
index 103813d78..07318746e 100644
--- a/tutorials/best_practices/scene_organization.rst
+++ b/tutorials/best_practices/scene_organization.rst
@@ -233,14 +233,14 @@ in another context without any extra changes to its API.
   satisfied? Other programmers, and especially designers and writers, will need
   clear instructions in the messages telling them what to do to configure it.
 
-So, why do all this complex switcharoo work? Well, because scenes operate
+So, why does all this complex switcharoo work? Well, because scenes operate
 best when they operate alone. If unable to work alone, then working with
 others anonymously (with minimal hard dependencies, i.e. loose coupling)
 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.
+adversely effecting other classes dependent on it.
 
 Scripts and scenes, as extensions of engine classes, should abide
 by *all* OOP principles. Examples include...