[docs] rephrase SvelteKit intro

dummdidumm · dummdidumm · commit a34312963a95 · 2022-12-14T16:09:43.000+01:00
diff --git a/content/tutorial/02-sveltekit/01-concepts/01-introducing-sveltekit/README.md b/content/tutorial/02-sveltekit/01-concepts/01-introducing-sveltekit/README.md
@@ -2,9 +2,7 @@
 title: What is SvelteKit?
 ---
 
-So far, we've been working on individual components, or groups of components, in isolation. But to build a complete app, you need more than just components.
-
-That's where SvelteKit comes in. Whereas Svelte is a _component framework_, SvelteKit is an _app framework_ (or 'metaframework', depending on who you ask) that solves the tricky problems of building something production-ready:
+SvelteKit is a framework for building extremely high-performance web apps. Whereas Svelte is a _component framework_, SvelteKit is an _app framework_ (or 'metaframework', depending on who you ask) that solves the tricky problems of building something production-ready:
 
 - Routing
 - Server-side rendering
@@ -20,4 +18,4 @@ That's where SvelteKit comes in. Whereas Svelte is a _component framework_, Svel
 
 SvelteKit apps are server-rendered by default (like traditional 'multi-page apps' or MPAs) for excellent first load performance and SEO characteristics, but can then transition to client-side navigation (like modern 'single-page apps' or SPAs) to avoid jankily reloading everything (including things like third-party analytics code) when the user navigates. They can run anywhere JavaScript runs, though — as we'll see — your users may not need to run any JavaScript at all.
 
-If that sounds complicated, worry not: you've been using SvelteKit this whole time!
+If that sounds complicated, worry not: SvelteKit is the framework that grows with you! Start simple and add new features as they come. This tutorial will go over the core concepts, while the [Advanced SvelteKit](/handle) tutorial teaches you how to tackle more complex use cases.
