diff --git a/docu/2-basic/4-subscribe-consumer-subaccount/README.md b/docu/2-basic/4-subscribe-consumer-subaccount/README.md
index eb65517..2166ecf 100644
--- a/docu/2-basic/4-subscribe-consumer-subaccount/README.md
+++ b/docu/2-basic/4-subscribe-consumer-subaccount/README.md
@@ -20,13 +20,14 @@ In this part of the tutorial, you will learn how to subscribe your first Tenant
 
 [<img src="./images/SUB_SubsTenant.png" width="600"/>](./images/SUB_SubsTenant.png?raw=true)
 
-1.2. In the new Tenant Subaccount, **do not** enable any kind of runtime (like Kyma or Cloud Foundry).
+> **Important** -  In the new Tenant Subaccount, **do not have to** enable any kind of runtime (like Kyma or Cloud Foundry).
+> If you have tenant-specific workloads that are independent of the SaaS solution, you can enable the relevant runtime in the tenant subaccount. Otherwise, enabling a runtime in the tenant subaccount is not a prerequisite for consuming a SaaS solution on SAP BTP.
 
-1.3. Create a new subscription in the Tenant Subaccount. Therefore, please go to **Instances and Subscriptions** and click on **Create**. 
+1.2. Create a new subscription in the Tenant Subaccount. Therefore, please go to **Instances and Subscriptions** and click on **Create**. 
 
 [<img src="./images/SUB_CreateSub01.png" width="600"/>](./images/SUB_CreateSub01.png?raw=true)
 
-1.4. Select the **Sustainable SaaS** service from the dropdown list.
+1.3. Select the **Sustainable SaaS** service from the dropdown list.
 
 > **Hint** - In case of multiple deployments in the SAP BTP region (e.g., different Cloud Foundry Spaces or different Kyma Namespaces), make sure to use the correct service offering by checking the unique Service Id format in case of Kyma **\<ReleaseName>-\<Namespace>-\<ShootName>** and in case of Cloud Foundry **susaas-\<Space>-\<Organization>**.
 
@@ -38,9 +39,9 @@ In this part of the tutorial, you will learn how to subscribe your first Tenant
 
 [<img src="./images/SUB_CreateSub02Cf.png" width="400"/>](./images/SUB_CreateSub02Cf.png?raw=true)
 
-1.5. Select a plan of your choice (e.g., **default**). In the Kyma version of this sample application, click on **Next**. In the Cloud Foundry scenario, please ignore the next step.  
+1.4. Select a plan of your choice (e.g., **default**). In the Kyma version of this sample application, click on **Next**. In the Cloud Foundry scenario, please ignore the next step.  
 
-1.6. In the Kyma scenario, you can now define a **custom subdomain** for your Subscriber Tenant. Please make sure to understand this feature before making use of it. If you leave this field blank, the URL of your Subscriber Tenant will be created in the following format.
+1.5. In the Kyma scenario, you can now define a **custom subdomain** for your Subscriber Tenant. Please make sure to understand this feature before making use of it. If you leave this field blank, the URL of your Subscriber Tenant will be created in the following format.
 
 > **\<SubaccountSubdomain>-\<ReleaseName>-router-\<Namespace>.\<ShootName>.kyma.ondemand.com**<br>
 > e.g., subscriber-c3b2a1-susaas-router-default.a1b2c3.kyma.ondemand.com
@@ -52,9 +53,9 @@ While this may result in long and inconvenient URLs for your subscribers, the un
 
 In this sample, we did not implement a check for the uniqueness of the value provided. It is in your responsibility to ensure, not to double-assign the same custom subdomain to your subscribers! 
 
-1.7. Click on **Create** to setup the subscription for your Subscriber Tenant. 
+1.6. Click on **Create** to setup the subscription for your Subscriber Tenant. 
 
-1.8. Wait until your subscription is in status **Subscribed**, which can take a few minutes. In the background, the Backend Service running in your Cloud Foundry environment or Kyma Cluster will setup a new HDI Database Container for the Subscriber Tenant and create a new Cloud Foundry Route or Kyma API Rule to expose the Subscriber subdomain. This might even take a few seconds longer than implied by the **Subscribed** status.
+1.7. Wait until your subscription is in status **Subscribed**, which can take a few minutes. In the background, the Backend Service running in your Cloud Foundry environment or Kyma Cluster will setup a new HDI Database Container for the Subscriber Tenant and create a new Cloud Foundry Route or Kyma API Rule to expose the Subscriber subdomain. This might even take a few seconds longer than implied by the **Subscribed** status.
 
 [<img src="./images/SUB_CreateSub03.png" width="600"/>](./images/SUB_CreateSub03.png?raw=true)
 
@@ -186,4 +187,4 @@ Please use the following links to find further information on the topics above:
 * [SAP Help - Subscribe to Multitenant Applications Using the Cockpit](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/7a3e39622be14413b2a4df7c02ca1170.html?locale=en-US)
 * [SAP Help - Managing Services Using the SAP BTP Cockpit](https://help.sap.com/docs/SERVICEMANAGEMENT/09cc82baadc542a688176dce601398de/cdce096d411242bcbfb9644d0860fd0f.html?locale=en-US)
 * [SAP Help - Security Administration: Managing Authentication and Authorization](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/1ff47b2d980e43a6b2ce294352333708.html?locale=en-US)
-* [SAP Help - Assigning Role Collections to Users or User Groups](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/31532c77bd61421e9d40d100fd75ef52.html?locale=en-US)
\ No newline at end of file
+* [SAP Help - Assigning Role Collections to Users or User Groups](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/31532c77bd61421e9d40d100fd75ef52.html?locale=en-US)