Adjust deleting instructions

docs/user/03-10-preconfigured-secret.md

@@ -50,9 +50,10 @@ The following parameters manage cluster access:
 | Parameter                | Description                                                                                                                                                                              |
 |--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | **CLUSTER_ID**           | Generated when Kyma runtime is created.                                                                                                                                                  |
-| **MANAGEMENT_NAMESPACE** | Indicates the namespace for Secrets referenced in Service Instances and Secrets with the name containing a prefix of the Service Instance's namespace. By default, set to `kyma-system`. |
-| **RELEASE_NAMESPACE**    | Stores the chart's release namespace and indicates the namespace for `sap-btp-service-operator` and `sap-btp-operator-clusterid` secrets. By default, set to `kyma-system`.              |
+| **MANAGEMENT_NAMESPACE** | Indicates the namespace for Secrets referenced in service instances and Secrets with the name containing a prefix of the service instance's namespace. By default, set to `kyma-system`. |
+| **RELEASE_NAMESPACE**    | Stores the chart's release namespace and indicates the namespace for `sap-btp-service-operator` and `sap-btp-operator-clusterid` Secrets. By default, set to `kyma-system`.              |
 | **ALLOW_CLUSTER_ACCESS** | You can use every namespace for your operations. The parameter is always set to `true`. If you change it to `false`, the setting is automatically reverted.                              |
 
-See [Managing Access](https://github.com/SAP/sap-btp-service-operator#managing-access) for more information about parameters.
-To use your own cluster access settings, you must customize the `sap-btp-operator` Secret. For more information, see [Customize Default Credentials and Access](03-11-customize_secret.md).
+## Related Information
+
+[Customize Default Credentials and Access](03-11-customize_secret.md)

docs/user/03-11-customize_secret.md

@@ -24,7 +24,9 @@ To customize the `sap-btp-manager` Secret, modify the credentials in the followi
 * Label the Secret with `kyma-project.io/skip-reconciliation: 'true'`.
 * Provide the following credentials from your SAP Service Manager instance: **clientid**, **clientsecret**, **sm_url**, and **tokenurl**.
 * Optionally, provide your **cluster_id**. Otherwise, it is generated automatically.
-* Optionally, add the **credentials_namespace** parameter and provide the name of your custom namespace for Secrets with credentials to communicate with the SAP Service Manager.  
+* Optionally, add the **credentials_namespace** parameter and provide the name of your custom namespace for Secrets with credentials to communicate with the SAP Service Manager.
+   >[!NOTE]
+   > Setting the **credentials_namespace** parameter changes the values of **MANAGEMENT_NAMESPACE** and **RELEASE_NAMESPACE** keys in the `sap-btp-operator-config` ConfigMap. The custom namespace replaces the default `kyma-system` namespace for `sap-btp-service-operator` and `sap-btp-operator-clusterid` Secrets. BTP Manager deletes the Secrets from the default namespace and creates them in the custom namespace.
 
 Example:
 ```yaml
@@ -46,8 +48,6 @@ data:
   credentials_namespace: {CREDENTIALS_NAMESPACE}
 ```
 
-Setting the **credentials_namespace** parameter changes the values of **MANAGEMENT_NAMESPACE** and **RELEASE_NAMESPACE** keys in the `sap-btp-operator-config` ConfigMap. The custom namespace replaces the default `kyma-system` namespace for `sap-btp-service-operator` and `sap-btp-operator-clusterid` secrets. BTP Manager deletes the secrets from the default namespace and creates them in the custom namespace.
-
 ## Result
 
 Your customized `sap-btp-manager` Secret is now the default Secret of the SAP BTP Operator module. It generates the SAP BTP service operator's resources, as shown in the following diagram:
@@ -58,7 +58,3 @@ The reconciliation of the Secret stops and your changes are not reverted.
 
 > [!WARNING]
 > If you delete the customized `sap-btp-manager` Secret, the reconciliation starts again, and the preconfigured default `sap-btp-manager` Secret is recreated for your Kyma instance within 24 hours. See [Preconfigured Credentials and Access](./03-10-preconfigured-secret.md#credentials).
-
-> [!NOTE]
-> If you created all service instances in your Kyma cluster from the customized `sap-btp-manager` Secret, you can delete the cluster even if those instances still exist.
-> The non-deleted service instances do not block the deletion of the cluster.

docs/user/03-70-delete-bindings-and-instances.md

@@ -4,18 +4,11 @@ Delete service bindings and service instances using Kyma dashboard or kubectl.
 
 ## Context
 
-You can only delete service instances or service bindings created in Kyma using Kyma dashboard or kubectl. You can't perform these operations using the SAP BTP cockpit.
+You can only delete service instances or service bindings created in Kyma using Kyma dashboard or kubectl. You can't perform these operations using the SAP BTP cockpit. To successfully delete a service instance, first delete its service bindings.
 
 > [!WARNING]
 > Once you delete your service instances and service bindings, you cannot revert the operation.
 
-If you haven't deleted all the service instances and service bindings associated with the `sap-btp-service-operator` Secret in the `kyma-system` namespace, you can't delete your Kyma cluster from the SAP BTP cockpit. To delete the remaining service instances and service bindings, go to Kyma dashboard.
-
-If you have not deleted service instances and bindings connected to your expired free tier service, you can still find the service binding credentials in the SAP Service Manager instance details in the SAP BTP cockpit. Use them to delete the leftover service instances and bindings.
-
-> [!TIP]
-> To successfully delete a service instance, first delete its service bindings.
-
 Use either Kyma dashboard or kubectl to delete a service binding or a service instance.
 
 ## Procedure
@@ -40,4 +33,14 @@ To delete a service instance, run:
 ```bash
 kubectl delete serviceinstances.services.cloud.sap.com {SERVICE_INSTANCE_NAME}
 ```
-<!-- tabs:end -->
+<!-- tabs:end -->
+
+## Next Steps
+
+To delete your Kyma cluster, you may have to delete your service instances and bindings from it.
+
+You can't delete your Kyma cluster if your service instances use the credentials from the SAP Service Manager resources created automatically, as described in [Preconfigured Credentials and Access](03-10-preconfigured-secret.md#credentials). In this case, the existing service instances block the cluster's deletion. Delete your service instances and bindings in Kyma dashboard before you attempt to delete the cluster from the SAP BTP cockpit.
+
+You can delete your Kyma cluster even if your service instances still exist, provided they use credentials of SAP Service Manager service instances other than the one created automatically, as described in [Preconfigured Credentials and Access](03-10-preconfigured-secret.md#credentials). In this case, the non-deleted service instances do not block the cluster's deletion. 
+
+If you have not deleted service instances and bindings connected to your expired free tier service, you can still find the service binding credentials in the SAP Service Manager instance details in the SAP BTP cockpit. Use them to delete the leftover service instances and bindings.