From a741d02c62a12ba3063d49f665a49b1a4f2a85d4 Mon Sep 17 00:00:00 2001
From: AaronAjose <aaronajoseajo@gmail.com>
Date: Wed, 24 Sep 2025 14:51:23 +0800
Subject: [PATCH 1/2] chore: fix typos

---
 packages/svelte/src/internal/client/dom/elements/attributes.js | 2 +-
 packages/svelte/src/internal/client/render.js                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/packages/svelte/src/internal/client/dom/elements/attributes.js b/packages/svelte/src/internal/client/dom/elements/attributes.js
index fb6a92cc82bd..e9c72865cf81 100644
--- a/packages/svelte/src/internal/client/dom/elements/attributes.js
+++ b/packages/svelte/src/internal/client/dom/elements/attributes.js
@@ -334,7 +334,7 @@ function set_attributes(
 			// the value is set to the text content of the option element, and setting the value
 			// to null or undefined means the value is set to the string "null" or "undefined".
 			// To align with how we handle this case in non-spread-scenarios, this logic is needed.
-			// There's a super-edge-case bug here that is left in in favor of smaller code size:
+			// There's a super-edge-case bug here that is left in favor of smaller code size:
 			// Because of the "set missing props to null" logic above, we can't differentiate
 			// between a missing value and an explicitly set value of null or undefined. That means
 			// that once set, the value attribute of an <option> element can't be removed. This is
diff --git a/packages/svelte/src/internal/client/render.js b/packages/svelte/src/internal/client/render.js
index f5e32a219699..b1165a6e7aee 100644
--- a/packages/svelte/src/internal/client/render.js
+++ b/packages/svelte/src/internal/client/render.js
@@ -143,7 +143,7 @@ export function hydrate(component, options) {
 			e.hydration_failed();
 		}
 
-		// If an error occured above, the operations might not yet have been initialised.
+		// If an error occurred above, the operations might not yet have been initialised.
 		init_operations();
 		clear_text_content(target);
 

From 78525eb1f17a57985c1da9da2b7e92c24daa113e Mon Sep 17 00:00:00 2001
From: Rich Harris <hello@rich-harris.dev>
Date: Wed, 24 Sep 2025 11:20:04 -0400
Subject: [PATCH 2/2] revert bad change

---
 packages/svelte/src/internal/client/dom/elements/attributes.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/svelte/src/internal/client/dom/elements/attributes.js b/packages/svelte/src/internal/client/dom/elements/attributes.js
index e9c72865cf81..fb6a92cc82bd 100644
--- a/packages/svelte/src/internal/client/dom/elements/attributes.js
+++ b/packages/svelte/src/internal/client/dom/elements/attributes.js
@@ -334,7 +334,7 @@ function set_attributes(
 			// the value is set to the text content of the option element, and setting the value
 			// to null or undefined means the value is set to the string "null" or "undefined".
 			// To align with how we handle this case in non-spread-scenarios, this logic is needed.
-			// There's a super-edge-case bug here that is left in favor of smaller code size:
+			// There's a super-edge-case bug here that is left in in favor of smaller code size:
 			// Because of the "set missing props to null" logic above, we can't differentiate
 			// between a missing value and an explicitly set value of null or undefined. That means
 			// that once set, the value attribute of an <option> element can't be removed. This is