fix：修复说明歧义

docs/en/guide/oneclickvirt/oneclickvirt_install.md

@@ -8,9 +8,11 @@ Distinguish between the panel side and the controlled side. The controlled side
 
 ## Controlled Side
 
-Perform environment installation according to the main installation instructions elsewhere in this documentation. This won't be elaborated on here. The tutorial has corresponding installation commands for the four mainstream virtualization technologies. Please refer to them yourself.
+For other virtual environments corresponding to this guide, their main installation scripts can be used to set up the environment. We won't elaborate further here. This tutorial provides installation commands for the main setup of the four major virtualization technologies. Please refer to them directly.
 
-The controlled side only needs to have the virtualization environment installed, and does not need to install an agent for control. Just ensure that SSH login is available (the SSH login address can be either public or private network, as long as connectivity is not an issue).
+If possible, always use the scripts to install the corresponding environment. Otherwise, you may encounter strange issues like inconsistent presets. If you lack technical expertise, do not manually install the environment. Use scripts for everything.
+
+The controlled end only requires the virtualization environment to be installed. There is no need to install an additional agent for control. Simply ensure SSH login is possible (the SSH login address can be public or internal network, as long as connectivity is unimpeded).
 
 ## Panel Side
 

docs/en/guide/oneclickvirt/oneclickvirt_usage.md

@@ -228,10 +228,12 @@ If you need to enable API operation mode, after successfully saving the node set
 
 ### Hardware Configuration (Optional)
 
-![](./images/hardware.png)
+![](./images/hardwareconfig.png)
 
 Only lxd and incus support setting default instance parameter configurations. Generally use the defaults unless you need to manually limit certain special hardware resources; otherwise, generally no modification is needed.
 
+If you need to set the maximum percentage of CPU usage or similar parameters, the settings here can meet your requirements.
+
 ### Health Check (Required)
 
 ![](./images/autoapi4.png)

docs/guide/oneclickvirt/oneclickvirt_install.md

@@ -8,7 +8,9 @@ outline: deep
 
 ## 受控端
 
-对应本说明别的主体安装进行环境安装，这里不过多赘述，四大主流的虚拟化技术的主体安装本教程都有对应的安装命令进行安装，自行查阅。
+对应本说明别的虚拟环境的主体安装脚本可以进行环境安装，这里不过多赘述，四大主流的虚拟化技术的主体安装本教程都有对应的安装命令进行安装，自行查阅。
+
+如有条件务必使用脚本进行对应的环境安装，否则可能出现预设不一致等奇奇怪怪的问题，没有技术力不要手动安装环境，一切通过脚本。
 
 受控端只需要安装好虚拟化环境即可，不必额外安装agent进行控制，只要确保SSH能登录即可(SSH登录地址可公网可内网，连通性无问题即可)。
 
@@ -244,7 +246,7 @@ https://github.com/oneclickvirt/oneclickvirt/pkgs/container/oneclickvirt
 
 中查询
 
-#### 方式一：预构建镜像
+#### 预构建镜像
 
 **镜像标签说明**
 
@@ -347,7 +349,7 @@ docker pull spiritlhl/oneclickvirt:latest
 
 然后再按全新环境下开设的步骤来，这样会提示重新初始化，所有原始数据已删除。
 
-#### 方式二：DockerCompose自编译
+#### DockerCompose自编译
 
 使用 Docker Compose 可以一键部署完整的开发环境，采用**分容器部署**架构，包括独立的前端容器、后端容器和数据库容器：
 
@@ -405,7 +407,7 @@ docker-compose down
 rm -rf ./data
 ```
 
-#### 方式三：Dockerfile自编译
+#### Dockerfile自编译
 
 这种方式适合自行修改源码与自定义构建：
 

docs/guide/oneclickvirt/oneclickvirt_usage.md

@@ -228,10 +228,12 @@ SSH超时配置是设计测试连通性和优化容错率的，也可以用来
 
 ### 硬件配置(可选)
 
-![](./images/hardware.png)
+![](./images/hardwareconfig.png)
 
 仅lxd和incus下支持设置默认的实例参数配置，一般使用默认的就行了，除非你需要手动限制某些特殊的硬件资源，否则一般不需要修改。
 
+如果你需要设置CPU占用的最大百分比等内容，这里的设置可以满足你的需求。
+
 ### 健康检测(必选)
 
 ![](./images/autoapi4.png)