diff --git a/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md b/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md
index e1a5debf8c..11832419a1 100644
--- a/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md
+++ b/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md
@@ -56,7 +56,7 @@ Let's compare some aspects of each solution:
 | Called directly within a job, not from a step | Run as a step within a job |
 | Can contain multiple jobs | Does not contain jobs |
 | Each step is logged in real-time | Logged as one step even if it contains multiple steps |
-| Can connect a maximum of four levels of workflows | Can be nested to have up to 10 composite actions in one workflow |
+| Can connect a maximum of ten levels of workflows | Can be nested to have up to 10 composite actions in one workflow |
 | Can use secrets | Cannot use secrets |
 
 ## Workflow templates
diff --git a/content/actions/how-tos/reuse-automations/reuse-workflows.md b/content/actions/how-tos/reuse-automations/reuse-workflows.md
index 699a9d92f7..ce61c0e22d 100644
--- a/content/actions/how-tos/reuse-automations/reuse-workflows.md
+++ b/content/actions/how-tos/reuse-automations/reuse-workflows.md
@@ -181,7 +181,7 @@ jobs:
 
 ## Nesting reusable workflows
 
-You can connect a maximum of four levels of workflows - that is, the top-level caller workflow and up to three levels of reusable workflows. For example: _caller-workflow.yml_ → _called-workflow-1.yml_ → _called-workflow-2.yml_ → _called-workflow-3.yml_. Loops in the workflow tree are not permitted.
+You can connect a maximum of ten levels of workflows - that is, the top-level caller workflow and up to nine levels of reusable workflows. For example: _caller-workflow.yml_ → _called-workflow-1.yml_ → _called-workflow-2.yml_ → _called-workflow-3.yml_ → ... → _called-workflow-9.yml_. Loops in the workflow tree are not permitted.
 
 > [!NOTE] Nested reusable workflows require all workflows in the chain to be accessible to the caller, and permissions can only be maintained or reduced—not elevated—throughout the chain. For more information, see [AUTOTITLE](/actions/reference/reusable-workflows-reference#access-and-permissions-for-nested-workflows).
 
diff --git a/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md b/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md
index 446cfcd7c8..42ac526b48 100644
--- a/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md
+++ b/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md
@@ -46,8 +46,8 @@ For {% ifversion ghes or ghec %}internal or {% endif %}private repositories, the
 
 ### Limitations of reusable workflows
 
-* You can connect up to four levels of workflows. For more information, see [Nesting reusable workflows](/actions/how-tos/sharing-automations/reuse-workflows#nesting-reusable-workflows).
-* You can call a maximum of 20 unique reusable workflows from a single workflow file. This limit includes any trees of nested reusable workflows that may be called starting from your top-level caller workflow file.
+* You can connect up to ten levels of workflows. For more information, see [Nesting reusable workflows](/actions/how-tos/sharing-automations/reuse-workflows#nesting-reusable-workflows).
+* You can call a maximum of 50 unique reusable workflows from a single workflow file. This limit includes any trees of nested reusable workflows that may be called starting from your top-level caller workflow file.
 
   For example, _top-level-caller-workflow.yml_ → _called-workflow-1.yml_ → _called-workflow-2.yml_ counts as 2 reusable workflows.