Apply suggestions from code review

Co-authored-by: Michał 'Disper' Drzewiecki <michal.drzewiecki@sap.com>

docs/contributor/testing-strategy.md

@@ -14,15 +14,15 @@ We investigate the product by separating it into layers:
 
 2. Business Features
 
-    Combines the business logic into feature which is consumed by our customers.
+    Combines the code into feature which is consumed by our customers.
 
 3. Product Integration
 
     Verifies how our product is integarted into the technical landscape, how it interacts with 3rd party systems and how it is accessible by customers or remote systems.
 
 For each layer, there is a dedicated testing approach used:
 
-1. **Unit Testing for Business Logic:** Writing and executing tests for individual functions, methods, and components to verify their behavior and correctness in isolation.
+1. **Unit Testing for Code:** Writing and executing tests for individual functions, methods, and components to verify their behavior and correctness in isolation.
 2. **Integration Testing for Business Features:** Validating the integration and interaction between different components, modules, and services in the project.
 3. **End-to-End Testing:** Testing the application as a whole in a production-like environment, mimicking real-world scenarios to ensure the entire system functions correctly, is performing well and secure.