fixes

documentation/docs/02-runes/02-$state.md

@@ -119,7 +119,7 @@ class Todo {
 }
 ```
 
-> Svelte provides reactive implementations of built-in classes like `Set` and `Map` that can be imported from [`svelte/reactivity`](svelte-reactivity).
+> [NOTE!] Svelte provides reactive implementations of built-in classes like `Set` and `Map` that can be imported from [`svelte/reactivity`](svelte-reactivity).
 
 ## `$state.raw`
 

documentation/docs/03-template-syntax/19-await-expressions.md

@@ -39,7 +39,7 @@ Currently, you can only use `await` inside a [`<svelte:boundary>`](svelte-bounda
 
 This restriction will be lifted once Svelte supports asynchronous server-side rendering (see [caveats](#Caveats)).
 
-> In the [playground](/playground), your app is rendered inside a boundary with an empty pending snippet, so that you can use `await` without having to create one.
+> [!NOTE] In the [playground](/playground), your app is rendered inside a boundary with an empty pending snippet, so that you can use `await` without having to create one.
 
 ## Synchronized updates
 

documentation/docs/05-special-elements/01-svelte-boundary.md

@@ -38,7 +38,7 @@ As of Svelte 5.36, boundaries with a `pending` snippet can contain [`await`](awa
 
 The `pending` snippet will _not_ be shown for subsequent async updates — for these, you can use [`$effect.pending()`]($effect#$effect.pending).
 
-> In the [playground](/playground), your app is rendered inside a boundary with an empty pending snippet, so that you can use `await` without having to create one.
+> [!NOTE] In the [playground](/playground), your app is rendered inside a boundary with an empty pending snippet, so that you can use `await` without having to create one.
 
 
 ### `failed`