diff --git a/docs/scu/dev/how-the-spryker-code-upgrader-works.md b/docs/scu/dev/how-the-spryker-code-upgrader-works.md
index 1047716b2c2..b53a895c2b2 100644
--- a/docs/scu/dev/how-the-spryker-code-upgrader-works.md
+++ b/docs/scu/dev/how-the-spryker-code-upgrader-works.md
@@ -2,7 +2,7 @@
 title: How the Spryker Code Upgrader works
 description: Spryker Code Upgrader overview
 template: concept-topic-template
-last_updated: Jul 24, 2023
+last_updated: Aug 22, 2023
 redirect_from:
   - /docs/paas-plus/dev/how-the-spryker-code-upgrader-works.html
 ---
@@ -40,7 +40,14 @@ Please follow the link below to find all documentation needed to help you upgrad
 https://api.release.spryker.com/release-group/XXXX
 ```
 
-To continue running the Upgrader tool, install the major version manually, and re-run the Upgrader tool.
+To continue running the Upgrader tool, install the major version manually, and rerun the Upgrader tool.
+
+{% info_block infoBox "Composer dependency conflict" %}
+
+Spryker Code Upgrader uses the [composer](https://getcomposer.org/) for updating modules and libraries.
+If the composer detects a conflict, it stops the update process and generates an error message. To resolve the conflict, you must manually update the conflicting module and rerun the Upgrader pipeline.
+
+{% endinfo_block %}
 
 ### 3. Creates a Git branch