From 455da3ecec841f64a6713d990c18d09da85fdc41 Mon Sep 17 00:00:00 2001 From: DeeJayLSP <60024671+DeeJayLSP@users.noreply.github.com> Date: Sun, 6 Jun 2021 22:16:23 -0300 Subject: [PATCH] Update class reference link on Scene organization (#4962) doc_autoloads_versus_internal_nodes points to Autoloads versus regular nodes, so name it correctly. --- getting_started/workflow/best_practices/scene_organization.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting_started/workflow/best_practices/scene_organization.rst b/getting_started/workflow/best_practices/scene_organization.rst index 19aecc5c8..cc41625bb 100644 --- a/getting_started/workflow/best_practices/scene_organization.rst +++ b/getting_started/workflow/best_practices/scene_organization.rst @@ -306,7 +306,7 @@ If one has a system that... If one has systems that modify other systems' data, one should define those as their own scripts or scenes rather than autoloads. For more information on the reasons, please see the -:ref:`'Autoloads vs. Internal Nodes' ` +:ref:`Autoloads versus regular nodes ` documentation. Each subsystem within one's game should have its own section within the