fix(docs): fix some links in the documentation

docs/content/en/lang-switcher.md

@@ -46,7 +46,7 @@ computed: {
 
 <alert type="info">
 
-When using `detectBrowserLanguage` and wanting to persist locale on a route change, you must call one of the functions that update the stored locale cookie. Call either [`setLocaleCookie(locale)`](/api/#setlocalecookie) to persist just the cookie locale or [`setLocale(locale)`](/api/#setlocale) to both persist the cookie locale and switch the route to the specified locale. Otherwise, locale might switch back to the saved one during navigation.
+When using `detectBrowserLanguage` and wanting to persist locale on a route change, you must call one of the functions that update the stored locale cookie. Call either [`setLocaleCookie(locale)`](/api#setlocalecookie) to persist just the cookie locale or [`setLocale(locale)`](/api#setlocale) to both persist the cookie locale and switch the route to the specified locale. Otherwise, locale might switch back to the saved one during navigation.
 
 </alert>
 

docs/content/en/migrating.md

@@ -14,7 +14,7 @@ Follow this guide to upgrade from one major version to the other.
 
 In some cases, having SEO enabled globally caused performance issues and/or conflicted with other plugins. To mitigate these issues, SEO features are now disabled by default.
 
-If you were affected by one of the issues above, we recommend that you read the [Improve performances](/seo/#improving-performance) section to enable SEO only where you need it.
+If you were affected by one of the issues above, we recommend that you read the [Improve performances](/seo#improving-performance) section to enable SEO only where you need it.
 
 If you'd like to restore the old behaviour, you can reenable SEO features globally by setting the `seo` option to `true`:
 

docs/content/en/options-reference.md

@@ -28,7 +28,7 @@ export default {
 }
 ```
 
-The former approach has the benefit of having having type-checking enabled if you have followed the [Typescript setup](/setup/#typescript).
+The former approach has the benefit of having having type-checking enabled if you have followed the [Typescript setup](/setup#typescript).
 
 ## Properties
 
@@ -152,7 +152,7 @@ Set to a path to which you want to redirect users accessing the root URL (`/`).
 - type: `boolean`
 - default: `false`
 
-If `true`, a SEO metadata will be generated for the routes. Note that performance can suffer with this option enabled and there might be compatibility issues with some plugins. The recommended way is to set up SEO as described in [Improving performance](/seo/#improving-performance).
+If `true`, a SEO metadata will be generated for the routes. Note that performance can suffer with this option enabled and there might be compatibility issues with some plugins. The recommended way is to set up SEO as described in [Improving performance](/seo#improving-performance).
 
 ## `differentDomains`
 
@@ -166,7 +166,7 @@ Set this to `true` when using different domains for each locale. If enabled, no
 - type: `boolean`
 - default: `true`
 
-Whether [custom paths](/routing/#custom-paths) are extracted from page files using babel parser.
+Whether [custom paths](/routing#custom-paths) are extracted from page files using babel parser.
 
 ## `pages`
 
@@ -186,7 +186,7 @@ Properties:
 - `moduleName` (default: `'i18n'`) - The module's namespace.
 - `syncLocale` (default: `false`) - If enabled, current app's locale is synced with **nuxt-i18n** store module.
 - `syncMessages` (default: `false`) - If enabled, current translation messages are synced with **nuxt-i18n** store module. **This will make the page response bigger so don't use unless necessary.**
-- `syncRouteParams` (default: `true`) - Enables a `setRouteParams` mutation for using custom route names with dynamic routes. See more information in [Dynamic route parameters](/lang-switcher/#dynamic-route-parameters)
+- `syncRouteParams` (default: `true`) - Enables a `setRouteParams` mutation for using custom route names with dynamic routes. See more information in [Dynamic route parameters](/lang-switcher#dynamic-route-parameters)
 
 ## `vueI18n`
 

docs/content/es/lang-switcher.md

@@ -45,7 +45,7 @@ computed: {
 
 <alert type="info">
 
-When using `detectBrowserLanguage` and wanting to persist locale on a route change, you must call one of the functions that update the stored locale cookie. Call either [`setLocaleCookie(locale)`](/api/#setlocalecookie) to persist just the cookie locale or [`setLocale(locale)`](/api/#setlocale) to both persist the cookie locale and switch the route to the specified locale. Otherwise, locale might switch back to the saved one during navigation.
+When using `detectBrowserLanguage` and wanting to persist locale on a route change, you must call one of the functions that update the stored locale cookie. Call either [`setLocaleCookie(locale)`](/api#setlocalecookie) to persist just the cookie locale or [`setLocale(locale)`](/api#setlocale) to both persist the cookie locale and switch the route to the specified locale. Otherwise, locale might switch back to the saved one during navigation.
 
 </alert>
 

docs/content/es/migrating.md

@@ -14,7 +14,7 @@ Siga esta guía para actualizar de una versión principal a otra.
 
 En algunos casos, tener SEO habilitado globalmente causó problemas de rendimiento y / o entró en conflicto con otros complementos. Para mitigar estos problemas, las características de SEO ahora están deshabilitadas de forma predeterminada.
 
-Si se vio afectado por uno de los problemas anteriores, le recomendamos que lea la sección [Mejorar el rendimiento](/seo/#improving-performance) para habilitar el SEO solo donde lo necesites.
+Si se vio afectado por uno de los problemas anteriores, le recomendamos que lea la sección [Mejorar el rendimiento](/seo#improving-performance) para habilitar el SEO solo donde lo necesites.
 
 Si desea restaurar el comportamiento anterior, puede habilitar las funciones de SEO a nivel mundial estableciendo la opción `seo` en `true`:
 

docs/content/es/options-reference.md

@@ -28,7 +28,7 @@ export default {
 }
 ```
 
-The former approach has the benefit of having having type-checking enabled if you have followed the [Typescript setup](/setup/#typescript).
+The former approach has the benefit of having having type-checking enabled if you have followed the [Typescript setup](/setup#typescript).
 
 ## Properties
 
@@ -152,7 +152,7 @@ Set to a path to which you want to redirect users accessing the root URL (`/`).
 - type: `boolean`
 - default: `false`
 
-If `true`, a SEO metadata will be generated for the routes. Note that performance can suffer with this option enabled and there might be compatibility issues with some plugins. The recommended way is to set up SEO as described in [Improving performance](/seo/#improving-performance).
+If `true`, a SEO metadata will be generated for the routes. Note that performance can suffer with this option enabled and there might be compatibility issues with some plugins. The recommended way is to set up SEO as described in [Improving performance](/seo#improving-performance).
 
 ## `differentDomains`
 
@@ -166,7 +166,7 @@ Set this to `true` when using different domains for each locale. If enabled, no
 - type: `boolean`
 - default: `true`
 
-Whether [custom paths](/routing/#custom-paths) are extracted from page files using babel parser.
+Whether [custom paths](/routing#custom-paths) are extracted from page files using babel parser.
 
 ## `pages`
 
@@ -186,7 +186,7 @@ Properties:
 - `moduleName` (default: `'i18n'`) - The module's namespace.
 - `syncLocale` (default: `false`) - If enabled, current app's locale is synced with **nuxt-i18n** store module.
 - `syncMessages` (default: `false`) - If enabled, current translation messages are synced with **nuxt-i18n** store module. **This will make the page response bigger so don't use unless necessary.**
-- `syncRouteParams` (default: `true`) - Enables a `setRouteParams` mutation for using custom route names with dynamic routes. See more information in [Dynamic route parameters](/lang-switcher/#dynamic-route-parameters)
+- `syncRouteParams` (default: `true`) - Enables a `setRouteParams` mutation for using custom route names with dynamic routes. See more information in [Dynamic route parameters](/lang-switcher#dynamic-route-parameters)
 
 ## `vueI18n`