docs: fix storybook link (#39)

Storybook has an official SvelteKit page now, so linking to it.

Really enjoyed your Svelte Summit talk -- Kitbook really nails a bunch of stuff that we've wanted to do for Storybook. Amazing work!

packages/kitbook/src/docs/why.md

@@ -4,10 +4,10 @@ While a lot of great tools exist, they are buggy and/or do not work well for bui
 
 - **[Svench](https://svench-docs.vercel.app/)** deserves much of the credit for Kitbook's initial inspiration and is an amazing tool. Unfortunately, it often broke on Windows, sometimes requiring the dev server to be started twice before success, and has other quirks that have left me without the ability to use my workbench. I attribute these problems simply due to the fact that 1.0 was built long before SvelteKit and while 2.0 will work great if @rixo gets time for that, so far he hasn't updated Svench to work with the current SvelteKit.
 
-- **[Storybook](https://codingcat.dev/tutorial/integrating-storybook-with-sveltekit)** was very buggy with SvelteKit for a long time so it pushed me away. Things are better now but Storybook still is not the tool I'm looking for. In short, too many features I don't need, not enough of the ones I do need, and too much boilerplate. [Histoire](https://histoire.dev/) is less bloated but in a similar boat. Both of them are very prototype focused and aren't so great for an easy to read documentation tool I'm looking for. (Histoire's documentation is cordoned off to a little box in the upper right that seems like an afterthought). A prototyping tool should also be a useful place for both developers and non-developers to read documentation, explore components and not get lost in the controls. If developers don't write documentation as they build components, chances are they never will, or they will be sorely out of date.
+- **[Storybook](https://storybook.js.org/docs/get-started/sveltekit)** was very buggy with SvelteKit for a long time so it pushed me away. Things are better now but Storybook still is not the tool I'm looking for. In short, too many features I don't need, not enough of the ones I do need, and too much boilerplate. [Histoire](https://histoire.dev/) is less bloated but in a similar boat. Both of them are very prototype focused and aren't so great for an easy to read documentation tool I'm looking for. (Histoire's documentation is cordoned off to a little box in the upper right that seems like an afterthought). A prototyping tool should also be a useful place for both developers and non-developers to read documentation, explore components and not get lost in the controls. If developers don't write documentation as they build components, chances are they never will, or they will be sorely out of date.
 
 - **Bookit** took a step the right direction its tight SvelteKit integration but Scott stopped working on it.
 
 - **Vitebook** was visually appealing but was missing many important prototyping features and was discontinued.
 
-All of the above tools, especially Svench, have served as a source of inspiration and ideas for Kitbook.
+All of the above tools, especially Svench, have served as a source of inspiration and ideas for Kitbook.