docs: Fix various typos.

documentation/docs/02-runes/05-$props.md

@@ -64,7 +64,7 @@ let { a, b, c, ...others } = $props();
 
 ## Updating props
 
-References to a prop inside a component update when the prop itself updates — when `count` changes in `App.svelte`, it will also change inside `Child.svelte`. But the child component is able to temporarily override the prop value, which can be useful for unsaved emphemeral state ([demo](/playground/untitled#H4sIAAAAAAAAE6WQ0WrDMAxFf0WIQR0Wmu3VTQJln7HsIfVcZubIxlbGRvC_DzuBraN92qPula50tODZWB1RPi_IX16jLALWSOOUq6P3-_ihLWftNEZ9TVeOWBNHlNhGFYznfqCBzeRdYHh6M_YVzsFNsNs3pdpGd4eBcqPVDMrNxNDBXeSRtXioDgO1zU8ataeZ2RE4Utao924RFXQ9iHXwvoPHKpW1xY4g_Bg0cSVhKS0p560Za95612ZC02ONrD8ZJYdZp_rGQ37ff_mSP86Np2TWZaNNmdcH56P4P67K66_SXoK9pG-5dF5Z9QEAAA==)):
+References to a prop inside a component update when the prop itself updates — when `count` changes in `App.svelte`, it will also change inside `Child.svelte`. But the child component is able to temporarily override the prop value, which can be useful for unsaved ephemeral state ([demo](/playground/untitled#H4sIAAAAAAAAE6WQ0WrDMAxFf0WIQR0Wmu3VTQJln7HsIfVcZubIxlbGRvC_DzuBraN92qPula50tODZWB1RPi_IX16jLALWSOOUq6P3-_ihLWftNEZ9TVeOWBNHlNhGFYznfqCBzeRdYHh6M_YVzsFNsNs3pdpGd4eBcqPVDMrNxNDBXeSRtXioDgO1zU8ataeZ2RE4Utao924RFXQ9iHXwvoPHKpW1xY4g_Bg0cSVhKS0p560Za95612ZC02ONrD8ZJYdZp_rGQ37ff_mSP86Np2TWZaNNmdcH56P4P67K66_SXoK9pG-5dF5Z9QEAAA==)):
 
 <!-- prettier-ignore -->
 ```svelte

documentation/docs/03-template-syntax/07-@render.md

@@ -14,7 +14,7 @@ To render a [snippet](snippet), use a `{@render ...}` tag.
 {@render sum(5, 6)}
 ```
 
-The expression can be an identifer like `sum`, or an arbitrary JavaScript expression:
+The expression can be an identifier like `sum`, or an arbitrary JavaScript expression:
 
 ```svelte
 {@render (cool ? coolSnippet : lameSnippet)()}

documentation/docs/06-runtime/02-context.md

@@ -63,7 +63,7 @@ The context is then available to children of the component (including slotted co
 
 > [!NOTE] `setContext`/`getContext` must be called during component initialisation.
 
-Context is not inherently reactive. If you need reactive values in context then you can pass a `$state` object into context, whos properties _will_ be reactive.
+Context is not inherently reactive. If you need reactive values in context then you can pass a `$state` object into context, whose properties _will_ be reactive.
 
 ```svelte
 <!--- file: Parent.svelte --->
@@ -112,7 +112,7 @@ You can also retrieve the whole context map that belongs to the closest parent c
 
 ## Encapsulating context interactions
 
-The above methods are very unopionated about how to use them. When your app grows in scale, it's worthwhile to encapsulate setting and getting the context into functions and properly type them.
+The above methods are very unopinionated about how to use them. When your app grows in scale, it's worthwhile to encapsulate setting and getting the context into functions and properly type them.
 
 ```ts
 // @errors: 2304

documentation/docs/07-misc/03-typescript.md

@@ -109,7 +109,7 @@ Type `$props` just like a regular object with certain properties.
 
 ## Generic `$props`
 
-Components can declare a generic relationship between their properties. One example is a generic list component that receives a list of items and a callback property that reveives an item from the list. To declare that the `items` property and the `select` callback operate on the same types, add the `generics` attribute to the `script` tag:
+Components can declare a generic relationship between their properties. One example is a generic list component that receives a list of items and a callback property that receives an item from the list. To declare that the `items` property and the `select` callback operate on the same types, add the `generics` attribute to the `script` tag:
 
 ```svelte
 <script lang="ts" generics="Item extends { text: string }">