godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-04 14:11:02 +03:00
Code Issues Packages Projects Releases Wiki Activity

Use more standard terminology. Fix grammar.

Browse Source 
Change to use node relationship terminology ("sibling") that is both more standard[0] & more inclusive.

Fix pluralisation (i.e. "Xs nodes" -> "X nodes").

[0] e.g. https://en.wikipedia.org/wiki/Tree_structure#Terminology_and_properties
This commit is contained in:
follower
2020-02-18 03:01:57 +13:00
committed by GitHub
parent e60bb57b4b
commit f17a55db2e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tutorials/plugins/editor/making_main_screen_plugins.rst
View File

@@ -79,7 +79,7 @@ UI element instantiation, and it will also manage the communication between them
As a matter of fact, we wish to design each UI element in their own scene.
Different scenes are not aware of each other unless they are both children of a
parent scene, yet they will then require ``get_node("../brother")`` accessors.
parent scene, yet they will then require ``get_node("../sibling")`` accessors.
Such practice is more likely to produce errors at runtime, especially if these
scenes do not share the same parent node. This is why, they should only be
allowed to access their children.
@@ -92,7 +92,7 @@ be instanced by ``main_screen_plugin.gd`` script, this one script will also
connect each of them to the required signals.
.. note:: If the ``main_screen_plugin.gd`` instantiates the UI scenes, won't
they be brothers nodes then?
they be sibling nodes then?
Not necessarily: this script may add all UI scenes as children of the same node
of the editor's scene tree - but maybe it won't. And the ``main_screen_plugin.gd``