Describe the utilities as the scripts run them

- The OVA/OVF import creates the VM with LSI and e1000
- The utilities picker lists 25 tools; jq and ncdu come from the analysis group
- A finished UUP Dump ISO is chosen with Install with personal ISO

web/messages/en/docs/utils/export-vm.json

@@ -121,7 +121,7 @@
     "unsupportedHwTitle": "Export completes but VMware refuses to import: \"Unsupported hardware family\"",
     "unsupportedHwBody": "Some ESXi versions reject OVF descriptors that declare a hardware family they don't recognise. Open the .ovf in a text editor (or extract the .ova first), find <code>&lt;vssd:VirtualSystemType&gt;</code> and edit it to a value ESXi accepts (e.g. <code>vmx-13</code> for ESXi 6.5+). For a quick workaround, try VirtualBox — it's more permissive.",
     "nicTitle": "Imported VM uses a different NIC or SCSI controller",
-    "nicBody": "The OVF preserves the NIC count, not the original model. Review the imported VM’s network settings in the destination hypervisor. The export declares an lsilogic SCSI controller for VMware compatibility. When importing back into Proxmox, you can select <code>VirtIO SCSI</code> if the guest has suitable drivers.",
+    "nicBody": "The OVF preserves the NIC count, not the original model. Review the imported VM’s network settings in the destination hypervisor. The export declares an lsilogic SCSI controller for VMware compatibility. When importing back into Proxmox with ProxMenux, the VM is created with an LSI controller and e1000 NICs; switch to <code>VirtIO SCSI</code> and VirtIO afterwards if the guest has suitable drivers.",
     "runningTitle": "VM was running and I declined to stop it — export aborted",
     "runningBody": "The script can't produce a consistent image while disks are being written. Either accept the shutdown prompt next time, or stop the VM manually first (<code>qm shutdown $VMID</code>) and re-run.",
     "slowTitle": "Disk conversion is slow",