Revised based on the CG feedback received

Author: lum1n0us

_posts/2025-01-16-wamr-2024-summary.md

@@ -44,6 +44,8 @@ Another significant feature introduced in 2024 is the shared heap. This feature
 
 The shared heap approach uses a pre-allocated region of linear memory as a "swap" area. Both the embedded system and Wasm can store and access shared objects here without the need for copying. However, this feature comes with its own set of challenges. Unlike memory.grow(), the new memory region isn't controlled by Wasm and may not even be aware of it. This requires runtime APIs to map the embedded-provided memory area into linear memory, making it a runtime-level solution rather than a Wasm opcode.
 
+It's important to note that the shared heap is an experimental feature, and the intent is to work towards a standardized approach within the WebAssembly Community Group (CG). This will help set expectations for early adopters and ensure alignment with the broader Wasm ecosystem. As the feature evolves, feedback from the community will be crucial in shaping its development and eventual standardization.
+
 ### Newly Implemented Features
 
 Several features have been finalized in 2024, further enhancing WAMR's capabilities: