From f5ed903585f43e54e596290ba190ef8cdf8d28f8 Mon Sep 17 00:00:00 2001
From: Tomi Turtiainen <10324676+tomi@users.noreply.github.com>
Date: Fri, 14 Nov 2025 20:54:42 +0200
Subject: [PATCH] Fix description of sub-workflow breaking change in v2 (#3873)

Co-authored-by: Kartik Balasubramanian <22399046+HumanistSerif@users.noreply.github.com>
---
 docs/2-0-breaking-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/2-0-breaking-changes.md b/docs/2-0-breaking-changes.md
index 6c6b6d58f..aac68e3c0 100644
--- a/docs/2-0-breaking-changes.md
+++ b/docs/2-0-breaking-changes.md
@@ -14,7 +14,7 @@ The release of n8n 2.0 continues n8n's commitment to providing a secure, reliabl
 
 ### Return expected sub-workflow data when it contains a wait node
 
-Previously, when a workflow (parent) called a subworkflow (child) that contained a Wait node, the parent workflow incorrectly received the input items to the Wait node from the child workflow.
+Previously, when a workflow (parent) called a subworkflow (child) that contained a node that waits (for example a Wait node or a human-in-the-loop node), the parent workflow incorrectly received the input items to the waiting node from the child workflow.
 
 In v2, the parent workflow now receives the output data from the end of the child workflow instead.