style(formatting): technical review

docs/components/early-access/alpha/sap/camunda-sap-integration.md

@@ -17,30 +17,30 @@ These features run in the customer's [SAP BTP instance](https://www.sap.com/prod
 
 ![SAP integration overview](./img/sap-integration-overview.png)
 
-## Technical requirements - SAP
+## Technical requirements
 
-Generally speaking, Camunda's SAP integration has ony few technical requirements. 
+All SAP integration artifacts have the following technical requirements:
 
-Yet all SAP integration artifacts have these technical requirements in common:
-
-- they run on SAP BTP, Cloud Foundry environment, and thus [need the respective service](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all)
-- [(free) Destination Service](https://discovery-center.cloud.sap/serviceCatalog/destination?region=all&service_plan=lite&commercialModel=btpea) for system- and service connectivity
-- if the S/4 or ECC system is located on-premises:
+- They run on SAP BTP, Cloud Foundry environment, and thus [need the respective service](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all).
+- [(free) Destination Service](https://discovery-center.cloud.sap/serviceCatalog/destination?region=all&service_plan=lite&commercialModel=btpea) for system and service connectivity.
+- If the S/4 or ECC system is located on-premises:
   - [(free) Connectivity Service](https://discovery-center.cloud.sap/serviceCatalog/connectivity-service?region=all)
-  - [SAP Cloud Connector](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/cloud-connector) configured and connected to both S/4 / ECC and the BTP subaccount where the Camunda SAP Integration artifacts will run
-- technical user with respective access right to the S/4 and/or ECC system
+  - [SAP Cloud Connector](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/cloud-connector) configured and connected to both S/4 ECC and the BTP subaccount where the Camunda SAP integration artifacts will run.
+- Technical user with respective access right to the S/4 and/or ECC system.
 
-For the **SAP OData connector**, no additional services are needed.
+### SAP OData Connector
 
-For the **SAP RFC connector**, there's additionally the [(free) SAP Authorization and Trust Management Service](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all) mandatory.
+No additional requirements.
 
-For the **SAP BTP Integration** moreover required:
+### SAP RFC Connector
 
-- [(free) SAP Authorization and Trust Management Service](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all) 
-- [PostgreSQL on SAP BTP, hyperscaler option](https://discovery-center.cloud.sap/serviceCatalog/postgresql-hyperscaler-option?region=all)
+- [(free) SAP Authorization and Trust Management Service](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all)
 
-For scaling out and up, it is usually sufficient to either add multiple instances of an integration module (e.g. the SAP OData connector) or equipping an integration module with more runtime memory (e.g. the SAP BTP integration). 
+### SAP BTP integration
+
+- [(free) SAP Authorization and Trust Management Service](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all)
+- [PostgreSQL on SAP BTP, hyperscaler option](https://discovery-center.cloud.sap/serviceCatalog/postgresql-hyperscaler-option?region=all)
 
-For more sophisticated tuning, all mechanism of BTP can be applied (such as the [(free) Application Autoscaler](https://discovery-center.cloud.sap/serviceCatalog/application-autoscaler?service_plan=standard&region=all&commercialModel=btpea)), as all SAP integration artifacts fully adhere to the BTP cloud based development standards and can moreover be fully configured just as any custom developed apps on BTP.
+For scaling out and up, either add multiple instances of an integration module (for example, the SAP OData Connector) or equip an integration module with more runtime memory (for example, the SAP BTP integration).
 
-We strive not only to keep the integration as simple and lean as possible, but also not to foster any lock-in. "We cook, you plate".
+For more sophisticated tuning, all mechanisms of BTP can be applied (such as the [(free) Application Autoscaler](https://discovery-center.cloud.sap/serviceCatalog/application-autoscaler?service_plan=standard&region=all&commercialModel=btpea)), as all SAP integration artifacts fully adhere to the BTP cloud-based development standards and can be fully configured just as any custom developed apps on BTP.