From 1d0bd2f2123dde3d28e28fdb5aa1cd354a88d328 Mon Sep 17 00:00:00 2001
From: RedworkDE <10944644+RedworkDE@users.noreply.github.com>
Date: Sat, 3 Jun 2023 21:01:14 +0200
Subject: [PATCH] Clarify the docs on Node.queue_free

---
 doc/classes/Node.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/classes/Node.xml b/doc/classes/Node.xml
index 4ea96f97e5a..c6a3217e0ec 100644
--- a/doc/classes/Node.xml
+++ b/doc/classes/Node.xml
@@ -654,7 +654,8 @@
 		<method name="queue_free">
 			<return type="void" />
 			<description>
-				Queues a node for deletion at the end of the current frame. When deleted, all of its child nodes will be deleted as well. This method ensures it's safe to delete the node, contrary to [method Object.free]. Use [method Object.is_queued_for_deletion] to check whether a node will be deleted at the end of the frame.
+				Queues a node for deletion at the end of the current frame. When deleted, all of its child nodes will be deleted as well, and all references to the node and its children will become invalid, see [method Object.free].
+				It is safe to call [method queue_free] multiple times per frame on a node, and to [method Object.free] a node that is currently queued for deletion. Use [method Object.is_queued_for_deletion] to check whether a node will be deleted at the end of the frame.
 			</description>
 		</method>
 		<method name="remove_child">