Sync svelte docs (#1347)

sync svelte docs

Co-authored-by: svelte-docs-bot[bot] <196124396+svelte-docs-bot[bot]@users.noreply.github.com>

Author: github-actions[bot]

apps/svelte.dev/content/docs/svelte/03-template-syntax/01-basic-markup.md

@@ -83,12 +83,14 @@ As with elements, `name={name}` can be replaced with the `{name}` shorthand.
 <Widget foo={bar} answer={42} text="hello" />
 ```
 
+## Spread attributes
+
 _Spread attributes_ allow many attributes or properties to be passed to an element or component at once.
 
-An element or component can have multiple spread attributes, interspersed with regular ones.
+An element or component can have multiple spread attributes, interspersed with regular ones. Order matters — if `things.a` exists it will take precedence over `a="b"`, while `c="d"` would take precedence over `things.c`:
 
 ```svelte
-<Widget {...things} />
+<Widget a="b" {...things} c="d" />
 ```
 
 ## Events

apps/svelte.dev/content/docs/svelte/03-template-syntax/03-each.md

@@ -44,7 +44,9 @@ An each block can also specify an _index_, equivalent to the second argument in
 {#each expression as name, index (key)}...{/each}
 ```
 
-If a _key_ expression is provided — which must uniquely identify each list item — Svelte will use it to diff the list when data changes, rather than adding or removing items at the end. The key can be any object, but strings and numbers are recommended since they allow identity to persist when the objects themselves change.
+If a _key_ expression is provided — which must uniquely identify each list item — Svelte will use it to intelligently update the list when data changes by inserting, moving and deleting items, rather than adding or removing items at the end and updating the state in the middle.
+
+The key can be any object, but strings and numbers are recommended since they allow identity to persist when the objects themselves change.
 
 ```svelte
 {#each items as item (item.id)}

apps/svelte.dev/content/docs/svelte/06-runtime/02-context.md

@@ -126,7 +126,7 @@ In many cases this is perfectly fine, but there is a risk: if you mutate the sta
 ```svelte
 <!--- file: App.svelte ---->
 <script>
-	import { myGlobalState } from 'svelte';
+	import { myGlobalState } from './state.svelte.js';
 
 	let { data } = $props();
 

apps/svelte.dev/content/docs/svelte/98-reference/21-svelte-compiler.md

@@ -594,10 +594,11 @@ namespace AST {
 		| AST.SvelteBoundary;
 
 	export type Tag =
-		| AST.ExpressionTag
-		| AST.HtmlTag
+		| AST.AttachTag
 		| AST.ConstTag
 		| AST.DebugTag
+		| AST.ExpressionTag
+		| AST.HtmlTag
 		| AST.RenderTag;
 
 	export type TemplateNode =