Wasm Docs: explicitly refer to legacy exception handling proposal to …

…avoid misinterpretation


Co-authored-by: Aleksey Zamulla <[email protected]>

docs/topics/wasm/wasm-overview.md

@@ -39,7 +39,7 @@ Kotlin/Wasm as its compilation target. Applications built with Kotlin/Wasm and C
 ![Kotlin/Wasm demo](wasm-demo.png){width=700}
 
 > To run applications built with Kotlin/Wasm in a browser, you need a browser version that supports the new garbage collection
-> and exception handling proposals. To check the browser support status, see the [WebAssembly
+> and legacy exception handling proposals. To check the browser support status, see the [WebAssembly
 > roadmap](https://webassembly.org/roadmap/).
 >
 {style="tip"}

docs/topics/wasm/wasm-troubleshooting.md

@@ -81,7 +81,7 @@ Including Chromium-based browsers such as Edge, Brave, Opera, or Samsung Interne
 ## Wasm proposals support
 
 Kotlin/Wasm improvements are based on [WebAssembly proposals](https://webassembly.org/roadmap/). Here you can find details about the support for WebAssembly's 
-garbage collection and exception handling proposals. 
+garbage collection and (legacy) exception handling proposals. 
 
 ### Garbage collection proposal
 
@@ -91,6 +91,8 @@ For this reason, we strongly recommend that you update your Wasm projects to the
 
 ### Exception handling proposal
 
+The Kotlin toolchain uses the [legacy exception handling proposal](https://github.com/WebAssembly/exception-handling/blob/master/proposals/exception-handling/legacy/Exceptions.md) by default which allows running produced Wasm binaries in wider range of environments.
+
 Since Kotlin 2.0.0, we have introduced support for the new version of Wasm [exception handling proposal](https://github.com/WebAssembly/exception-handling/blob/main/proposals/exception-handling/Exceptions.md) within Kotlin/Wasm.
 
 This update ensures the new exception handling proposal aligns with Kotlin requirements, enabling the use of Kotlin/Wasm on virtual machines that only support the latest version of the proposal.