diff --git a/setup/unstable_versions.rst b/setup/unstable_versions.rst
index 5e6e138ff8d..6b30a0f785b 100644
--- a/setup/unstable_versions.rst
+++ b/setup/unstable_versions.rst
@@ -8,7 +8,7 @@ Creating a New Project Based on an Unstable Symfony Version
 -----------------------------------------------------------
 
 
-Suppose that the Symfony 4.0 version hasn't been released yet and you want to create
+Suppose that the Symfony 5.4 version hasn't been released yet and you want to create
 a new project to test its features. First, `install the Composer package manager`_.
 Then, open a command console, enter your project's directory and
 run the following command:
@@ -24,7 +24,7 @@ in the ``my_project/`` directory.
 Upgrading your Project to an Unstable Symfony Version
 -----------------------------------------------------
 
-Suppose again that Symfony 4.0 hasn't been released yet and you want to upgrade
+Suppose again that Symfony 5.4 hasn't been released yet and you want to upgrade
 an existing application to test that your project works with it.
 
 First, open the ``composer.json`` file located in the root directory of your
@@ -35,8 +35,8 @@ new version and change your ``minimum-stability`` to ``beta``:
 
       {
           "require": {
-    +         "symfony/framework-bundle": "^4.0",
-    +         "symfony/finder": "^4.0",
+    +         "symfony/framework-bundle": "^5.4",
+    +         "symfony/finder": "^5.4",
               "...": "..."
           },
     +     "minimum-stability": "beta"
@@ -44,7 +44,7 @@ new version and change your ``minimum-stability`` to ``beta``:
 
 You can also use set ``minimum-stability`` to ``dev``, or omit this line
 entirely, and opt into your stability on each package by using constraints
-like ``4.0.*@beta``.
+like ``5.4.*@beta``.
 
 Finally, from a terminal, update your project's dependencies: