docs: fix typos

docs/content/3.api/1.composables/use-fetch.md

@@ -54,7 +54,7 @@ All fetch options can be given a `computed` or `ref` value. These will be watche
 ::
 
 * **Options (from `useAsyncData`)**:
-  * `key`: a unique key to ensure that data fetching can be properly de-duplicated across requests, if not provided, it will be generated based on the static code location where `useAyncData` is used.
+  * `key`: a unique key to ensure that data fetching can be properly de-duplicated across requests, if not provided, it will be generated based on the static code location where `useAsyncData` is used.
   * `server`: Whether to fetch the data on the server (defaults to `true`).
   * `default`: A factory function to set the default value of the data, before the async function resolves - particularly useful with the `lazy: true` option.
   * `pick`: Only pick specified keys in this array from the `handler` function result.

docs/content/3.api/1.composables/use-router.md

@@ -45,7 +45,7 @@ router.replace({ hash: "#bio" });
 
 ## Navigation Guards
 
-`useRouter` composable provides `afterEach`, `beforeEach` and `beforeResolve` helper methods that acts as nagivation guards.
+`useRouter` composable provides `afterEach`, `beforeEach` and `beforeResolve` helper methods that acts as navigation guards.
 
 However, Nuxt has a concept of **route middleware** that simplifies the implementation of navigation guards and provides a better developer experience.
 

docs/content/3.api/1.composables/use-runtime-config.md

@@ -43,7 +43,7 @@ Variables that need to be accessible on the server are added directly inside `ru
 ::ReadMore{link="/guide/going-further/runtime-config"}
 ::
 
-## Acess Runtime Config
+## Access Runtime Config
 
 To access runtime config, we can use `useRuntimeConfig()` composable: