docs: fix link error in document website

docs/en/guide/define-mock.md

@@ -34,4 +34,4 @@ export default defineMock([
 
 `type: MockOptionsItem | MockOptionsItem[]`
 
-See [mock-config](/en/guide/mock-config)
+See [mock-config](./mock-config)

docs/en/guide/install.md

@@ -1,6 +1,6 @@
 # Install
 
-This section will guide you through the process of installing this plugin in your project. If you have already completed the installation, please skip to [Usage](/en/guide/usage)。
+This section will guide you through the process of installing this plugin in your project. If you have already completed the installation, please skip to [Usage](./usage)。
 
 <div class="tip custom-block" style="padding-top: 8px">
 

docs/en/guide/mock-plugin.md

@@ -19,4 +19,4 @@ export default defineConfig({
 
 `type: MockServerPluginOptions`
 
-See [pluginConfig](/en/guide/plugin-config)
+See [pluginConfig](./plugin-config)

docs/en/guide/teamwork.md

@@ -7,7 +7,7 @@ On the other hand, within the plugin, a solution is provided to address team col
 
 ## Solution
 
-In [File Directory Management](/guide/file-management), we have provided the recommended approach for standardizing and refining the management of `mock files`. However, even when refining to a single file for **single interface + parameter validation**, it is still inevitable to encounter conflicts when multiple people modify the same interface.
+In [File Directory Management](./file-management), we have provided the recommended approach for standardizing and refining the management of `mock files`. However, even when refining to a single file for **single interface + parameter validation**, it is still inevitable to encounter conflicts when multiple people modify the same interface.
 
 In this scenario, a recommended solution is to localize the mock file and exclude it from being committed to git:
 

docs/en/guide/usage.md

@@ -2,7 +2,7 @@
 
 This section will guide you through the process of using this plugin in your project.
 
-If you haven't installed this plugin in your project yet, please refer to [Install](/en/guide/install).
+If you haven't installed this plugin in your project yet, please refer to [Install](./install).
 
 ## Step1: Import plugin
 

docs/zh/guide/define-mock.md

@@ -34,4 +34,4 @@ export default defineMock([
 
 `type: MockOptionsItem | MockOptionsItem[]`
 
-查看 [mock-config](/guide/mock-config)
+查看 [mock-config](./mock-config)

docs/zh/guide/install.md

@@ -1,6 +1,6 @@
 # 安装
 
-本节将帮助你如何在项目中安装 此插件。如果你已经完成了安装，请直接跳转到 [使用](/guide/usage)。
+本节将帮助你如何在项目中安装 此插件。如果你已经完成了安装，请直接跳转到 [使用](./usage)。
 
 <div class="tip custom-block" style="padding-top: 8px">
 

docs/zh/guide/mock-plugin.md

@@ -19,4 +19,4 @@ export default defineConfig({
 
 `type: MockServerPluginOptions`
 
-查看 [pluginConfig](/guide/plugin-config)
+查看 [pluginConfig](./plugin-config)

docs/zh/guide/teamwork.md

@@ -7,7 +7,7 @@
 
 ## 协作方案
 
-在 [文件目录管理](/guide/file-management) 中，我们给出了如何规范化，细化管理 `mock file` 的推荐方式，
+在 [文件目录管理](./file-management) 中，我们给出了如何规范化，细化管理 `mock file` 的推荐方式，
 但即使细化到了 **单一接口 + 参数验证** 为单个文件时，还是无法避免 多人同时改动改接口导致冲突。
 
 在这种场景下，一种推荐的解决方案是，将 mock 文件本地化，忽略该 mock 文件 提交到 git：

docs/zh/guide/usage.md

@@ -1,6 +1,6 @@
 # 使用
 
-本节将帮助你在项目中使用此插件，如果你还未在项目中安装此插件，请先查看 [安装](/guide/install)。
+本节将帮助你在项目中使用此插件，如果你还未在项目中安装此插件，请先查看 [安装](./install)。
 
 ## Step1: 引入插件
 
@@ -83,7 +83,7 @@ export default defineConfig({
 └── package.json
 ```
 
-插件提供了 [`defineMock()`](/guide/define-mock) 函数帮助编写 mock 配置。
+插件提供了 [`defineMock()`](./define-mock) 函数帮助编写 mock 配置。
 
 ```ts [api.mock.ts]
 import { defineMock } from 'vite-plugin-mock-dev-server'