From c4c66889cc88ef83dd756468f6776168e83fdc96 Mon Sep 17 00:00:00 2001
From: Simon Holthausen <simon.holthausen@vercel.com>
Date: Thu, 22 Jun 2023 19:08:36 +0200
Subject: [PATCH] try this

---
 .../blog/2023-02-21-streaming-snapshots-sveltekit.md       | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/documentation/blog/2023-02-21-streaming-snapshots-sveltekit.md b/documentation/blog/2023-02-21-streaming-snapshots-sveltekit.md
index 49aa05d4ac..899dc169c4 100644
--- a/documentation/blog/2023-02-21-streaming-snapshots-sveltekit.md
+++ b/documentation/blog/2023-02-21-streaming-snapshots-sveltekit.md
@@ -18,9 +18,7 @@ Now, in SvelteKit 1.8, we have a new solution: you can return a nested promise f
 For example, consider the following `load` function:
 
 ```ts
-/// file: +page.server.ts
-import type { PageServerLoad } from './$types';
-
+// @errors: 2304
 export const load: PageServerLoad = () => {
 	return {
 		post: fetchPost(),
@@ -34,7 +32,6 @@ export const load: PageServerLoad = () => {
 SvelteKit will automatically await the `fetchPost` call before it starts rendering the page, since it’s at the top level. However, it won’t wait for the nested `fetchComments` call to complete – the page will render and `data.streamed.comments` will be a promise that will resolve as the request completes. We can show a loading state in the corresponding `+page.svelte` using Svelte’s [await block](https://svelte.dev/docs#template-syntax-await):
 
 ```svelte
-<!-- file: +page.svelte --->
 <script lang="ts">
 	import type { PageData } from './$types';
 	export let data: PageData;
@@ -136,7 +133,6 @@ Now, you can export a `snapshot` object from a `+page.svelte` or `+layout.svelte
 For example, here is how you would capture and restore the value of a textarea:
 
 ```svelte
-<!-- file: +page.svelte -->
 <script lang="ts">
 	import type { Snapshot } from './$types';
 
@@ -166,6 +162,7 @@ SvelteKit uses platform-specific [adapters](https://kit.svelte.dev/docs/adapters
 Now, you can export a `config` object in your `+server.js`, `+page(.server).js` and `+layout(.server).js` files to control how those routes are deployed. Doing so in a `+layout.js` will apply the configuration to all child pages. The type of `config` is unique to each adapter, since it depends on the environment you’re deploying to.
 
 ```ts
+// @errors: 2307
 import type { Config } from 'some-adapter';
 
 export const config: Config = {