Update content/en/docs/overview/context.md

Co-authored-by: vasu1124 <[email protected]>

content/en/docs/overview/context.md

@@ -57,7 +57,7 @@ Additionally, the **model needs to be extensible**. Being able to easily adapt t
 The model needs to support signing and verification processes out-of-the-box. This enables consumers of software components to verify that delivered components have not been tampered with. The signing and verification support has to acknowledge the fact that the technical artifact locations may change over time, which means that these concrete locations must not be part of the signing process.
 
 ### Network effects
-Re-use components described with OCM are ready for secure consumption and immediate integration by higher level components or products. Linking to trusted and already attested components can spawn across different teams within the same organization or even across organizational boundaries. This directly improves efficiency (cf. package models of maven or npm). 
+Re-use components described with OCM are ready for secure consumption and immediate integration by higher level components (or products). Linking to trusted and already attested components can spawn across different teams within the organization. This directly improves efficiency (cf. proficiency of package models of maven or npm). With other parties also describing component with OCM, a commercial contract can cover the necessary technical trust outside the organization and simplify its secure import and compliant re-use. OCM envisions a network effect across the industry.
 
 ## TL;DR - Summary
 All of the above boils down to the following requirements.<br>