diff --git a/docs/en/Community-Articles/2026-08-10-oss-sustainability-in-.net-commercialization-of-key/Post.md b/docs/en/Community-Articles/2026-08-10-oss-sustainability-in-.net-commercialization-of-key/Post.md
index 2a67bf5e8e..bc35d478b2 100644
--- a/docs/en/Community-Articles/2026-08-10-oss-sustainability-in-.net-commercialization-of-key/Post.md
+++ b/docs/en/Community-Articles/2026-08-10-oss-sustainability-in-.net-commercialization-of-key/Post.md
@@ -67,8 +67,6 @@ In other words, the move to commercial licensing is often less about greed than
 
 
 
-![Generated illustration](inline-1.png)
-
 ## Why the community reaction is so mixed
 
 Even if the economics make sense, the backlash is real. And frankly, some of it is justified.
@@ -188,9 +186,7 @@ Now the questions are not just technical:
 
 That is architecture, budgeting, and compliance converging in one decision.
 
-
-
-![Generated illustration](inline-2.png)
+ 
 
 ## How teams should respond
 
@@ -311,4 +307,4 @@ The healthiest outcome is not pretending commercialization should never happen.
 - Teams should evaluate dependencies by license, governance, support policy, and replacement cost.
 - Commercial OSS can be the right choice for critical infrastructure, especially where support and security matter.
 - The real risk is not paying for software; it is being surprised by cost, lock-in, or migration pressure too late.
-- .NET teams should treat dependency strategy as an architectural and business decision, not just a NuGet decision.
\ No newline at end of file
+- .NET teams should treat dependency strategy as an architectural and business decision, not just a NuGet decision.