Merge pull request #2023 from spryker/thomas-schwaier-spryker-patch-2

Update app-composition-platform-installation.md

docs/acp/user/app-composition-platform-installation.md

@@ -40,7 +40,7 @@ To make your project ACP-ready, different update steps are necessary depending o
 - SCCOS product release [202211.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html): All the changes required for ACP readiness are already included, but you should still verify them at the project level.
 - Older versions: To get the project ACP-ready, you should complete all steps described in this document.
 
-{% info_block infoBox "Product version ealier than 202211.0" %}
+{% info_block infoBox "Product version earlier than 202211.0" %}
 
 If you were onboarded with a version older than product release [202211.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html), please [contact us](https://support.spryker.com/). 
 
@@ -73,6 +73,12 @@ For [each app](https://docs.spryker.com/docs/acp/user/intro-to-acp/acp-overview.
 
 ### 2. Configure SCCOS
 
+{% info_block infoBox "This step can be omitted for Product version later than 202211.0" %}
+
+If your version is based on product release [202211.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html) or newer, you can skip this section! 
+
+{% endinfo_block %}
+
 Once you have ensured that your project modules are up-to-date, proceed to configure your SCCOS project to activate the ACP catalog in the Back Office using the following steps:
 
 1. Define the configuration and add plugins to the following files: