godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-05 22:09:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed minor grammatical error

Browse Source
This commit is contained in:
AV77
2023-05-11 14:27:29 +00:00
parent e7c5dd3d1b
commit 1426a11449
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tutorials/best_practices/scene_organization.rst
View File

@@ -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...