From db6dc3b36c4944e6604925fe01a2974130bbfb2c Mon Sep 17 00:00:00 2001
From: Cyberhead21 <126357372+Cyberhead21@users.noreply.github.com>
Date: Sun, 28 Dec 2025 23:56:37 +0100
Subject: [PATCH] Document functions used for changing scenes manually

---
 tutorials/scripting/change_scenes_manually.rst | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/tutorials/scripting/change_scenes_manually.rst b/tutorials/scripting/change_scenes_manually.rst
index 300636b5b04..7c2c2fb5fd3 100644
--- a/tutorials/scripting/change_scenes_manually.rst
+++ b/tutorials/scripting/change_scenes_manually.rst
@@ -73,7 +73,9 @@ access and integrity.
 
 2. **Hide the existing scene.** By changing the visibility or collision
    detection of the nodes, you can hide the entire node sub-tree from the
-   player's perspective.
+   player's perspective. Use
+   :ref:`CanvasItem.hide() <class_CanvasItem_method_hide>` to hide a scene and
+   :ref:`CanvasItem.show() <class_CanvasItem_method_show>` to show it again.
 
     - Memory still exists.
 
@@ -101,7 +103,8 @@ access and integrity.
 3. **Remove the existing scene from the tree.** Assign a variable
    to the existing scene's root node. Then use
    :ref:`Node.remove_child(Node) <class_Node_method_remove_child>` to detach the entire
-   scene from the tree.
+   scene from the tree. To attach it later, use
+   :ref:`Node.add_child(Node) <class_Node_method_add_child>`.
 
     - Memory still exists (similar pros/cons as hiding it from view).