docs: fix typos (#23921)

docs/1.getting-started/12.upgrade.md

@@ -1,6 +1,6 @@
 ---
 title: Upgrade Guide
-description: 'Learn how to upgrade to the lastest Nuxt version.'
+description: 'Learn how to upgrade to the latest Nuxt version.'
 navigation.icon: i-ph-arrow-circle-up-duotone
 ---
 

docs/2.guide/1.concepts/4.server-engine.md

@@ -58,5 +58,5 @@ Nuxt 3 generates this dist when running `nuxt build` into a [`.output`](/docs/gu
 The output contains runtime code to run your Nuxt server in any environment (including experimental browser service workers!) and serve your static files, making it a true hybrid framework for the JAMstack. In addition, Nuxt implements a native storage layer, supporting multi-source drivers and local assets.
 
 ::read-more{color="gray" icon="i-simple-icons-github" to="https://github.com/unjs/nitro" target="_blank"}
-Read more anout Nitro engine on GitHub.
+Read more about Nitro engine on GitHub.
 ::

docs/2.guide/2.directory-structure/1.pages.md

@@ -6,7 +6,7 @@ navigation.icon: i-ph-folder-duotone
 ---
 
 ::callout
-To reduce your application's bundle size, this directory is **optional**, meaning that [`vue-router`](https://router.vuejs.org) won't be included if you only use [`app.vue`](/docs/guide/directory-structure/app). To force the pages sytem, set `pages: true` in `nuxt.config` or have a [`app/router.options.ts`](/docs/guide/directory-structure/pages#router-options).
+To reduce your application's bundle size, this directory is **optional**, meaning that [`vue-router`](https://router.vuejs.org) won't be included if you only use [`app.vue`](/docs/guide/directory-structure/app). To force the pages system, set `pages: true` in `nuxt.config` or have a [`app/router.options.ts`](/docs/guide/directory-structure/pages#router-options).
 ::
 
 ## Usage

docs/3.api/5.kit/3.compatibility.md

@@ -51,7 +51,7 @@ Constraints to check for. It accepts the following properties:
 
   **Type**: `string`
 
-  Nuxt version in semver format. Versions may be defined in Node.js way, for exmaple: `>=2.15.0 <3.0.0`.
+  Nuxt version in semver format. Versions may be defined in Node.js way, for example: `>=2.15.0 <3.0.0`.
 
 - `bridge` (optional)
 
@@ -99,7 +99,7 @@ Constraints to check for. It accepts the following properties:
 
   **Type**: `string`
 
-  Nuxt version in semver format. Versions may be defined in Node.js way, for exmaple: `>=2.15.0 <3.0.0`.
+  Nuxt version in semver format. Versions may be defined in Node.js way, for example: `>=2.15.0 <3.0.0`.
 
 - `bridge` (optional)
 
@@ -147,7 +147,7 @@ Constraints to check for. It accepts the following properties:
 
   **Type**: `string`
 
-  Nuxt version in semver format. Versions may be defined in Node.js way, for exmaple: `>=2.15.0 <3.0.0`.
+  Nuxt version in semver format. Versions may be defined in Node.js way, for example: `>=2.15.0 <3.0.0`.
 
 - `bridge` (optional)
 

docs/5.community/6.roadmap.md

@@ -35,7 +35,7 @@ DevTools     | 2023          | -
 Scripts      | 2023          | [nuxt/nuxt#22016](https://github.com/nuxt/nuxt/discussions/22016)      | Easy 3rd party script management.
 Fonts        | 2023          | [nuxt/nuxt#22014](https://github.com/nuxt/nuxt/discussions/22014)      | Allow developers to easily configure fonts in their Nuxt apps.
 Assets       | 2023          | [nuxt/nuxt#22012](https://github.com/nuxt/nuxt/discussions/22012)      | Allow developers and modules to handle loading third-party assets.
-A11y         | 2023          | [nuxt/nuxt#23255](https://github.com/nuxt/nuxt/issues/23255)           | Accessibility hinting and utilties
+A11y         | 2023          | [nuxt/nuxt#23255](https://github.com/nuxt/nuxt/issues/23255)           | Accessibility hinting and utilities
 Translations | -             | [nuxt/translations#4](https://github.com/nuxt/translations/discussions/4) ([request access](https://github.com/nuxt/nuxt/discussions/16054)) | A collaborative project for a stable translation process for Nuxt 3 docs. Currently pending for ideas and documentation tooling support (content v2 with remote sources).
 
 ## Core Modules

docs/7.migration/6.pages-and-layouts.md

@@ -192,7 +192,7 @@ Most of the syntax and functionality are the same for the global [NuxtLink](/doc
 When migrating from Nuxt 2 to Nuxt 3, you will have to update how you programmatically navigate your users. In Nuxt 2, you had access to the underlying Vue Router with `this.$router`. In Nuxt 3, you can use the `navigateTo()` utility method which allows you to pass a route and parameters to Vue Router.
 
 ::callout{color="amber" icon="i-ph-warning-duotone"}
-Ensure to always `await` on [`navigateTo`](/docs/api/utils/navigate-to) or chain it's result by returning from functions.
+Ensure to always `await` on [`navigateTo`](/docs/api/utils/navigate-to) or chain its result by returning from functions.
 ::
 
 ::code-group

test/fixtures/basic-types/types.ts

@@ -346,7 +346,7 @@ describe('composables', () => {
     expectTypeOf(useAsyncData<string>(() => $fetch('/test'), { default: () => 'test' }).data).toEqualTypeOf<Ref<string>>()
     expectTypeOf(useLazyAsyncData<string>(() => $fetch('/test'), { default: () => 'test' }).data).toEqualTypeOf<Ref<string>>()
 
-    // transform must match the explicit generic because of typescript limiations microsoft/TypeScript#14400
+    // transform must match the explicit generic because of typescript limitations microsoft/TypeScript#14400
     expectTypeOf(useFetch<string>('/test', { transform: () => 'transformed' }).data).toEqualTypeOf<Ref<string | null>>()
     expectTypeOf(useLazyFetch<string>('/test', { transform: () => 'transformed' }).data).toEqualTypeOf<Ref<string | null>>()
     expectTypeOf(useAsyncData<string>(() => $fetch('/test'), { transform: () => 'transformed' }).data).toEqualTypeOf<Ref<string | null>>()

test/fixtures/basic/pages/useAsyncData/refresh.vue

@@ -29,7 +29,7 @@ initial = data.value!.count
 await refresh2()
 
 if (data.value!.count !== initial + 1) {
-  throw new Error('data2 refresh not syncronised?')
+  throw new Error('data2 refresh not synchronised?')
 }
 
 if (data.value!.count !== data2.value!.count) {