Sync svelte docs (#755)

sync svelte docs

Co-authored-by: Rich-Harris <[email protected]>

Author: github-actions[bot]

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

@@ -230,7 +230,7 @@ All visible elements have the following readonly bindings, measured with a `Resi
 bind:this={dom_node}
 ```
 
-To get a reference to a DOM node, use `bind:this`. The value will be `undefined` until the component is mounted — in other words, you should read it inside an effect or an event handler, but not during component initialisation:
+To get a reference to a DOM node, use `bind:this`. The value will be `undefined` until the component is mounted — in other words, you should read it inside an effect or an event handler, but not during component initialisation:
 
 ```svelte
 <script>

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

@@ -68,7 +68,7 @@ transition = (node: HTMLElement, params: any, options: { direction: 'in' | 'out'
 
 Transitions can use custom functions. If the returned object has a `css` function, Svelte will generate keyframes for a [web animation](https://developer.mozilla.org/en-US/docs/Web/API/Web_Animations_API).
 
-The `t` argument passed to `css` is a value between `0` and `1` after the `easing` function has been applied. _In_ transitions run from `0` to `1`, _out_ transitions run from `1` to `0` — in other words, `1` is the element's natural state, as though no transition had been applied. The `u` argument is equal to `1 - t`.
+The `t` argument passed to `css` is a value between `0` and `1` after the `easing` function has been applied. _In_ transitions run from `0` to `1`, _out_ transitions run from `1` to `0` — in other words, `1` is the element's natural state, as though no transition had been applied. The `u` argument is equal to `1 - t`.
 
 The function is called repeatedly _before_ the transition begins, with different `t` and `u` arguments.
 
@@ -169,4 +169,3 @@ An element with transitions will dispatch the following events in addition to an
 	</p>
 {/if}
 ```
-

apps/svelte.dev/content/docs/svelte/99-legacy/02-legacy-reactive-assignments.md

@@ -15,7 +15,7 @@ In legacy mode, any top-level statement (i.e. not inside a block or a function)
 	// when `a`, `b` or `sum` change
 	$: console.log(`${a} + ${b} = ${sum}`);
 
-	// this is a 'reactive assignment' — `sum` will be
+	// this is a 'reactive assignment' — `sum` will be
 	// recalculated when `a` or `b` change. It is
 	// not necessary to declare `sum` separately
 	$: sum = a + b;

apps/svelte.dev/content/docs/svelte/99-legacy/40-legacy-component-api.md

@@ -11,7 +11,7 @@ In Svelte 3 and 4, the API for interacting with a component is different than in
 const component = new Component(options);
 ```
 
-A client-side component — that is, a component compiled with `generate: 'dom'` (or the `generate` option left unspecified) is a JavaScript class.
+A client-side component — that is, a component compiled with `generate: 'dom'` (or the `generate` option left unspecified) is a JavaScript class.
 
 ```ts
 // @noErrors