GITBOOK-1624: No subject

Author: pjoshi751

blogs/why-odoo.md

@@ -2,7 +2,7 @@
 
 A frequent question in the OpenG2P community is _why the project has chosen the Odoo framework as its underlying technology_ for building some of the core modules. This blog post clarifies the rationale behind that decision.
 
-The story goes back to OpenG2P’s roots: the platform was originally developed as an extension of UNDP’s system, which made extensive use of Odoo for program management functions. Multiple project milestones involved thoughtful evaluations about potentially moving away from Odoo. Each time, the conclusion remained consistent—Odoo continues to deliver critical flexibility and rapid feature deployment, especially for core OpenG2P modules like [Registry](../social-registry/) and [PBMS](../pbms/).
+The story goes back to OpenG2P’s roots: the platform was originally developed as an extension of UNDP’s system, which made extensive use of Odoo for program management functions. During the course of OpenG2P's evolution, multiple project milestones involved thoughtful evaluations about potentially moving away from Odoo. Each time, the conclusion remained consistent—Odoo continues to deliver critical flexibility and rapid feature deployment, especially for core OpenG2P modules like [Registry](../social-registry/) and [PBMS](../pbms/).
 
 **Adaptability and speed** remain vital for OpenG2P, as new country requirements and business processes frequently emerge. The ability to update the core platform rapidly is a significant advantage and Odoo’s integrated user interface makes a big difference—even when compared to purely API-driven systems.