diff --git a/content/tutorial/03-sveltekit/08-stores/03-updated-store/README.md b/content/tutorial/03-sveltekit/08-stores/03-updated-store/README.md
index e910c4dc7..967284576 100644
--- a/content/tutorial/03-sveltekit/08-stores/03-updated-store/README.md
+++ b/content/tutorial/03-sveltekit/08-stores/03-updated-store/README.md
@@ -4,38 +4,29 @@ title: updated
The `updated` store contains `true` or `false` depending on whether a new version of the app has been deployed since the page was first opened. For this to work, your `svelte.config.js` must specify `kit.version.pollInterval`.
-Version changes only happen in production, not during development. For that reason, `$updated` will always be `false` in this tutorial.
-
-You can manually check for new versions, regardless of `pollInterval`, by calling `updated.check()`.
-
```svelte
/// file: src/routes/+layout.svelte
+```
-
+Version changes only happen in production, not during development. For that reason, `$updated` will always be `false` in this tutorial.
-
+You can manually check for new versions, regardless of `pollInterval`, by calling `updated.check()`.
-+++{#if $updated}
-
- A new version of the app is available
+```svelte
+/// file: src/routes/+layout.svelte
-
-