docs: small fixes

Author: pi0

README.md

@@ -1,15 +1,16 @@
-# Nuxt Bridge
+# 🌉 Nuxt Bridge
 
 > Experience Nuxt 3 features on existing Nuxt 2 projects.
 
-If you're starting a fresh Nuxt 3 project, please skip this section and go to [Nuxt 3 Installation](https://v3.nuxtjs.org/getting-started/quick-start).
-
-**Note:** Nuxt Bridge provides identical features to Nuxt 3 ([Nuxt 3 docs](https://v3.nuxtjs.org/guide/features/views)) but there are some limitations, notably that `useAsyncData` and `useFetch` composables are not available. Please read the rest of this page for details.
-
 Bridge is a forward-compatibility layer that allows you to experience many of the new Nuxt 3 features by simply installing and enabling a Nuxt module.
 
 Using Nuxt Bridge, you can make sure your project is (almost) ready for Nuxt 3 and have the best developer experience without needing a major rewrite or risk breaking changes.
 
+⚠️ **Note:** Nuxt Bridge provides identical features to Nuxt 3 ([Nuxt 3 docs](https://v3.nuxtjs.org/guide/features/views)) but there are some limitations, notably that `useAsyncData` and `useFetch` composables are not available. Please read the rest of this page for details.
+
+🌱 **Note:** If you're starting a fresh Nuxt project, please skip this module and directly go to the [Nuxt 3 Installation](https://v3.nuxtjs.org/getting-started/quick-start).
+
+
 ## Installation
 
 ### Upgrade to the latest Nuxt 2
@@ -23,11 +24,11 @@ Make sure your dev server (`nuxt dev`) isn't running, remove any package lock fi
 
 Then, reinstall your dependencies:
 
-```bash [Yarn]
+```bash
+# Using yarn
 yarn install
-```
 
-```bash [NPM]
+# Using npm
 npm install
 ```
 
@@ -37,11 +38,12 @@ Once the installation is complete, make sure both development and production bui
 
 Install `@nuxt/bridge-edge` as a development dependency:
 
-```bash [Yarn]
+```bash
+
+# Using yarn
 yarn add --dev @nuxt/bridge@npm:@nuxt/bridge-edge
-```
 
-```bash [NPM]
+# Using npm
 npm install -D @nuxt/bridge@npm:@nuxt/bridge-edge
 ```
 
@@ -51,7 +53,7 @@ You will also need to update your scripts within your `package.json` to reflect
 
 ### Nuxi
 
-Nuxt 3 introduced the new Nuxt CLI command [`nuxi`](/api/commands/add). Update your scripts as follows to leverage the better support from Nuxt Bridge:
+Nuxt 3 introduced the new Nuxt CLI command [`nuxi`](https://v3.nuxtjs.org/api/commands/add). Update your scripts as follows to leverage the better support from Nuxt Bridge:
 
 ```diff
 {
@@ -126,11 +128,11 @@ In case you need to extend options provided by `./.nuxt/tsconfig.json` further,
 
 ## Migrate Composition API
 
-If you were using `@vue/composition-api` or `@nuxtjs/composition-api`, please read the [composition api migration guide](/bridge/bridge-composition-api).
+If you were using `@vue/composition-api` or `@nuxtjs/composition-api`, please read the [composition api migration guide](https://v3.nuxtjs.org/bridge/bridge-composition-api).
 
 ### Migrate from CommonJS to ESM
 
-Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](/guide/going-further/esm) for more info and upgrading.
+Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native ES Modules](https://v3.nuxtjs.org/guide/going-further/esm) for more info and upgrading.
 
 ## Remove incompatible and obsolete modules
 
@@ -139,8 +141,8 @@ Nuxt 3 natively supports TypeScript and ECMAScript Modules. Please check [Native
 - Remove `@nuxt/typescript-build`: Bridge enables same functionality
 - Remove `@nuxt/typescript-runtime` and `nuxt-ts`: Nuxt 2 has built-in runtime support
 - Remove `@nuxt/nitro`: Bridge injects same functionality
-- Remove `@vue/composition-api` from your dependencies ([migration guide](/bridge/bridge-composition-api)).
-- Remove `@nuxtjs/composition-api` from your dependencies (and from your modules in `nuxt.config`) ([migration guide](/bridge/bridge-composition-api)).
+- Remove `@vue/composition-api` from your dependencies ([migration guide](https://v3.nuxtjs.org/bridge/bridge-composition-api)).
+- Remove `@nuxtjs/composition-api` from your dependencies (and from your modules in `nuxt.config`) ([migration guide](https://v3.nuxtjs.org/bridge/bridge-composition-api)).
 
 ## Exclude built Nitro folder from git
 
@@ -164,7 +166,7 @@ export default defineNuxtConfig({
 
 You can now migrate to the Nuxt 3 plugins API, which is slightly different in format from Nuxt 2.
 
-Plugins now take only one argument (`nuxtApp`). You can find out more in [the docs](/guide/directory-structure/plugins).
+Plugins now take only one argument (`nuxtApp`). You can find out more in [the docs](https://v3.nuxtjs.org/guide/directory-structure/plugins).
 
 ```js
 export default defineNuxtPlugin(nuxtApp => {
@@ -204,7 +206,7 @@ export default defineNuxtConfig({
 This `useHead` composable uses `@vueuse/head` under the hood (rather than `vue-meta`) to manipulate your `<head>`.
 Accordingly, we recommend not to use both the native Nuxt 2 `head()` properties as well as `useHead`, as they may conflict.
 
-For more information on how to use this composable, see [the docs](/guide/features/head-management).
+For more information on how to use this composable, see [the docs](https://v3.nuxtjs.org/guide/features/head-management).
 
 ## Feature Flags