Update _posts/2026-01-22-ten-years-of-webassembly-a-retrospective.md

Co-authored-by: Nick Fitzgerald <fitzgen@gmail.com>

Author: 2 people

_posts/2026-01-22-ten-years-of-webassembly-a-retrospective.md

@@ -24,7 +24,7 @@ PNaCl placed the program's call stack in its own memory space—a reasonable
 
 Asm.js took a different approach, which Dan Gohman—then at Mozilla—describes as a "trusted call stack," where compiled code and JavaScript could share the same stack. 
 
-"That means Asm.js was able to kind of coexist with JavaScript," he says. "You can call into JavaScript, and JavaScript can call into you." This design decision—later inherited by WebAssembly—would prove foundational, enabling everything from seamless browser integration to the Component Model's vision of calling across isolation boundaries.
+"That means Asm.js was able to kind of coexist with JavaScript," he says. "You can call into JavaScript, and JavaScript can call into you." This design decision—later inherited by WebAssembly—would prove foundational, enabling everything from seamless browser integration to calling functions across isolation boundaries in the Component Model.
 
 ## "We're going to tell each other's managers that the other one's on board."