docs: rephrasing repo example declaration

Author: FaGru3n

docs/release/trg-2/trg-2-4.md

@@ -10,24 +10,24 @@ title: TRG 2.04 - Leading product repository
 
 ## Why
 
-We have multiply stakeholders for a repository: System team, release management, test management, external people who are trying it out, want to contribute or need to set it up.
+We have multiply stakeholders for a repository: system team, release management, test management, external people who are trying it out, want to contribute or need to set it up.
 They need to be able to understand complicated product structures in an intuitive way to have an easier task of diving into a product.
 
 ## Description
 
 Each product **must** have a leading product repository that can point the users to all the parts/components/charts/releases of that product.
 This can be achieved by having a single repository for a product or creating references to the other repositories.
 
-A good example when a product has a separate repository for frontend and backend. Then the product team **must** have a leading repository where they reference the components/repositories of the product:
+Good product examples have separate repositories for each component (e.g. frontend and backend). Then the product team **must** have a leading repository where they reference the components/repositories of the product:
 
 - productname: leading product repository
-  - README.md: contains the urls for the backend and frontend applications
+  - README.md: contains the urls for e.g. the backend and frontend applications
   - README.md: each repo follows our [TRG 1.01](../trg-1/trg-1-1.md) about the README.md
-  - README.md: an [example](#readme-example-section-for-a-leading-product-repository) for a leading product repository
+  - README.md: an [example section](#readme-example-section-for-a-leading-product-repository) for a leading product repository
   - contains the release of the product
   - contains the [product helm chart](../trg-5/trg-5-08)
-- productname-A-frontend: the repository for the frontend application
-- productname-A-backend: the repository for the backend application
+- productname-a-component: e.g. the repository for the frontend application
+- productname-b-component: e.g. the repository for the backend application
 
 ## Leading product repository rules