From 037a52a271d5cafe54685b05eca3a5425d5accc7 Mon Sep 17 00:00:00 2001
From: mariekirsch <63100752+mariekirsch@users.noreply.github.com>
Date: Tue, 18 Nov 2025 14:46:44 +0100
Subject: [PATCH] chore: save & deploy for Node version (#2808)

---
 docusaurus/docs/cloud/projects/settings.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docusaurus/docs/cloud/projects/settings.md b/docusaurus/docs/cloud/projects/settings.md
index ada98b0f55..e1fa83b0c4 100644
--- a/docusaurus/docs/cloud/projects/settings.md
+++ b/docusaurus/docs/cloud/projects/settings.md
@@ -325,8 +325,11 @@ The environment's Node version is based on the one chosen at the creation of the
 
 1. In the *Basic information* section of the <Icon name="faders" /> *Configuration* tab, click on the *Node version*'s edit <Icon name="pencil-simple" /> button.
 2. Using the *Node version* drop-down in the dialog, click on the version of your choice.
-3. Click on the **Save** button.
-4. Trigger a new deployment in the environment for which you changed the Node version. If the deployment fails, it is because the Node version doesn't match the version of your Strapi project. You will have to switch to the other Node version and re-deploy your project again.
+3. Click on **Save**, or **Save & deploy** if you want the changes to take effect immediately. 
+
+:::tip
+Ensure the Node version configured in your Strapi project matches the Node version shown in your project’s dashboard before deploying.
+:::
 
 #### Editing Git branch