From 06ddd366d165c7a9a50fc7021da7cf9a5369644d Mon Sep 17 00:00:00 2001
From: Ben McCann <322311+benmccann@users.noreply.github.com>
Date: Tue, 19 Dec 2023 21:27:56 -0800
Subject: [PATCH] Update
 sites/svelte-5-preview/src/routes/docs/content/01-api/02-runes.md

---
 .../svelte-5-preview/src/routes/docs/content/01-api/02-runes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sites/svelte-5-preview/src/routes/docs/content/01-api/02-runes.md b/sites/svelte-5-preview/src/routes/docs/content/01-api/02-runes.md
index 0849e90bd3..c12685b15e 100644
--- a/sites/svelte-5-preview/src/routes/docs/content/01-api/02-runes.md
+++ b/sites/svelte-5-preview/src/routes/docs/content/01-api/02-runes.md
@@ -144,7 +144,7 @@ The portions of `$: {}` that are triggering side-effects can be replaced with `$
 - They run after the DOM has been updated, whereas `$:` statements run immediately _before_
 - You can return a cleanup function that will be called whenever the effect refires
 
-Additionally, you may prefer to use effects in some places where you previously used `onMount` and `afterUpdate` (the latter of which will be deprecated in Svelte 5). There are some differences between these APIs as `$effect` should not be used to compute reactive values and will be triggered each time a referenced reactive variable changes changes (unless using `$untrack`).
+Additionally, you may prefer to use effects in some places where you previously used `onMount` and `afterUpdate` (the latter of which will be deprecated in Svelte 5). There are some differences between these APIs as `$effect` should not be used to compute reactive values and will be triggered each time a referenced reactive variable changes (unless using `untrack`).
 
 ## `$effect.pre`