Address comment

docs/advanced/settings.md

@@ -546,7 +546,7 @@ https://your.upgrade.checker-url/v99/checkupgrade
 
   :::
 
-- `restoreVM`: This setting controls whether to automatically restore running VMs after a single-node upgrade. By default, it is set to `false`, meaning all VMs are stopped after the upgrade. If set to true, Harvester will restart VMs that were running prior to the upgrade. Note that VMs that were paused before the upgrade will remain stopped once the upgrade is complete.
+- `restoreVM`: Option that enables Harvester to automatically restore running VMs after a single-node cluster is upgraded. The default value is `false`, which causes all VMs to be stopped after the upgrade is completed. When set to `true`, Harvester restarts VMs that were running before the upgrade was started. VMs that were paused before the upgrade are not restarted.
 
 **Example**:
 

docs/advanced/singlenodeclusters.md

@@ -55,6 +55,6 @@ If you want Longhorn to create multiple replicas on a node with multiple disks,
 
 ## Upgrades and Maintenance
 
-Single-node clusters do not support [Live Migration](../vm/live-migration.md), so VMs become unavailable during cluster upgrades. Harvester forcibly shuts down all VMs before starting the upgrade process. To restore running VMs after upgrade, please set `restoreVM` to true in the [`upgrade-config` setting](./settings.md#upgrade-config).
+Single-node clusters do not support [Live Migration](../vm/live-migration.md), so VMs become unavailable during cluster upgrades. Harvester forcibly shuts down all VMs before starting the upgrade process. You can configure Harvester to automatically restore running VMs using the `restoreVM` option of the [`upgrade-config`](./settings.md#upgrade-config) setting.
 
 Enabling [Maintenance Mode](../host/host.md#node-maintenance) is also not possible because that operation relies on Live Migration functionality, and Harvester cannot place the only control plane in Maintenance Mode.