diff --git a/docs/content/1.getting-started/2.installation/1.nuxt.md b/docs/content/1.getting-started/2.installation/1.nuxt.md index 8079eb80..6851e267 100644 --- a/docs/content/1.getting-started/2.installation/1.nuxt.md +++ b/docs/content/1.getting-started/2.installation/1.nuxt.md @@ -95,7 +95,7 @@ export default defineNuxtConfig({ ### `fonts` -Use the `fonts` option to enable or disable the `@nuxt/fonts` module. +Use the `fonts` option to enable or disable the [`@nuxt/fonts`](https://github.com/nuxt/fonts) module. - Default: `true`{lang="ts-type"} @@ -110,7 +110,7 @@ export default defineNuxtConfig({ ### `colorMode` -Use the `colorMode` option to enable or disable the `@nuxt/color-mode` module. +Use the `colorMode` option to enable or disable the [`@nuxt/color-mode`](https://github.com/nuxt-modules/color-mode) module. - Default: `true`{lang="ts-type"} diff --git a/docs/content/1.getting-started/3.theme.md b/docs/content/1.getting-started/3.theme.md index f9a2619c..59441b88 100644 --- a/docs/content/1.getting-started/3.theme.md +++ b/docs/content/1.getting-started/3.theme.md @@ -46,7 +46,7 @@ You can learn more about this on [https://tailwindcss.com/blog/tailwindcss-v4-al You can use the `@source` directive to add explicit content glob patterns if you want to look for Tailwind classes in other files that are not automatically detected. -This can be useful when writing Tailwind classes in markdown files with `@nuxt/content`: +This can be useful when writing Tailwind classes in markdown files with [`@nuxt/content`](https://github.com/nuxt/content): ```vue [app.vue]