Update apps/svelte.dev/content/blog/2025-03-01-whats-new-in-svelte-march-2025.md

Co-authored-by: Simon H <[email protected]>

Author: DreaminDani

apps/svelte.dev/content/blog/2025-03-01-whats-new-in-svelte-march-2025.md

@@ -14,7 +14,6 @@ But before we dive into that, let's get to some updates!
 - Native support for Websockets in SvelteKit is now available for testing! You can install the version of SvelteKit from the PR using pkg.pr.new and the PR number ([How To Install](https://github.com/sveltejs/kit/issues/1491#issuecomment-2645962690), [PR/Docs](https://github.com/sveltejs/kit/pull/12973))
 - `$props.id()` provides SSR-safe ID generation - unique for each instance of a component (**[email protected]**, [Docs](https://svelte.dev/docs/svelte/props#props.id()), [#15185](https://github.com/sveltejs/svelte/pull/15185))
 - SvelteKit now supports an option for server-side route resolution. This means that instead of loading the whole routing manifest in the client, and doing the route resolution there, the server runtime is invoked for each route request (**[email protected]**, [#13379](https://github.com/sveltejs/kit/pull/13379))
-- The Vercel adapter will now generate edge function dedicated to server side route resolution when using that option in SvelteKit (**@sveltejs/adapter-vercel 5.6.0 - 5.6.2**, [#13379](https://github.com/sveltejs/kit/pull/13379), [#13409](https://github.com/sveltejs/kit/pull/13409), [#13461](https://github.com/sveltejs/kit/pull/13461))
 - The values for `cache-control` and `content-type` headers are now validated in dev mode to help catch invalid values early (**2.17.0**, [#13114](https://github.com/sveltejs/kit/pull/13114))
 
 For a full list of bug fixes in Svelte, SvelteKit and its adapters, check out their CHANGELOGs [here](https://github.com/sveltejs/svelte/blob/main/packages/svelte/CHANGELOG.md) and [here](https://github.com/sveltejs/kit/tree/main/packages).