From 1e7836535903de2fc7f63073146cf288dc46b0d2 Mon Sep 17 00:00:00 2001
From: spiritlhl <103393591+spiritLHLS@users.noreply.github.com>
Date: Thu, 24 Apr 2025 08:51:03 +0000
Subject: [PATCH] =?UTF-8?q?fix:=20=E4=BF=AE=E5=A4=8D=E6=8E=92=E7=89=88?=
 =?UTF-8?q?=E9=94=99=E8=AF=AF?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/en/incomplete/webvirtcloud.md | 10 +++++-----
 docs/incomplete/webvirtcloud.md    | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/en/incomplete/webvirtcloud.md b/docs/en/incomplete/webvirtcloud.md
index ffd9cc18bd..64941211bf 100644
--- a/docs/en/incomplete/webvirtcloud.md
+++ b/docs/en/incomplete/webvirtcloud.md
@@ -85,8 +85,6 @@ curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt
    After the execution is completed, there will be a prompt that needs to be filled in the Controller panel side of the content.
    Panel side to fill in the Hostname is the IPV4 address of the current computing node, as well as to fill in the Token to identify the node.
 
-## Troubleshooting
-
 ### NetworkManager Version Issue
 
 You might see this error during installation:
@@ -111,7 +109,7 @@ After installation, a **Token** will be generated for adding the compute node to
 
 Path: `Admin Panel > Computers > Add`
 
-### Add IP Mapping for the Created Virtual Machine
+### Add Public IPV4 Ports Mapping for the Created Virtual Machine
 
 Assume your virtual machine appears in the user control panel as:
 
@@ -152,6 +150,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
 
 Now the internal virtual machine is exposed to the internet and can be accessed remotely.
 
+## Troubleshooting
+
 ### Troubleshooting Adding Compute Node
 
 On the Controller node, execute:
@@ -206,7 +206,7 @@ docker logs webvirtcloud-backend -f
 
 Then trigger the error from the frontend; the log will now display the corresponding error in real time.
 
-### Restarting Docker Containers After Controller Reboot
+### Docker containers do not restart themselves after a Controller reboot
 
 If Docker containers don't auto-restart after a system reboot, run:
 
@@ -214,7 +214,7 @@ If Docker containers don't auto-restart after a system reboot, run:
 docker start $(docker ps -a -q)
 ```
 
-### Disadvantages
+## Disadvantages
 
 The VM image is written to death, there is no way to use your own custom image, and there is no way to export it, and the original image does not have password login and ROOT login available.
 
diff --git a/docs/incomplete/webvirtcloud.md b/docs/incomplete/webvirtcloud.md
index b6dd3ccd5d..55f2506296 100644
--- a/docs/incomplete/webvirtcloud.md
+++ b/docs/incomplete/webvirtcloud.md
@@ -89,8 +89,6 @@ bash install_hypervisor.sh x.x.x.x
 
 面板端要填入Hostname的是当前计算节点的IPV4地址，还有要填入Token识别节点。
 
-## 问题排查
-
 ### NetworkManager 版本问题
 
 安装过程中可能会出现以下错误：
@@ -115,7 +113,7 @@ Error: Failed to add 'br-ext' connection: connection.autoconnect-ports: unknown
 
 路径: `Admin Panel > Computers > Add`
 
-### 给开设的虚拟机添加IP映射
+### 给开设的虚拟机添加公网IP端口映射
 
 假设此时你的虚拟机在用户端控制面板显示为
 
@@ -156,6 +154,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
 
 这样内网的虚拟机就被映射出来，可以直接远程登录使用了。
 
+## 问题排查
+
 ### 添加计算节点错误排查
 
 在Controller控制端执行：
@@ -210,7 +210,7 @@ docker logs webvirtcloud-backend -f
 
 然后前端去触发错误的位置，这块日志实时加载就会看到对应的报错了
 
-### Controller 重启后 Docker 容器重启
+### Controller 重启后 Docker 容器不自重启
 
 如果 Docker 容器在系统重启后没有自动重启，执行以下命令：
 
@@ -218,7 +218,7 @@ docker logs webvirtcloud-backend -f
 docker start $(docker ps -a -q)
 ```
 
-### 缺点
+## 缺点
 
 系统镜像是写死的，没法使用自己制作的自定义镜像，也没办法导出使用，同时原始的镜像没有设置远程可用密码登录和ROOT登录可用