Describe the VM creation options as the scripts offer them

- ZimaOS offers Host or KVM64 and SCSI or SATA
- The disk image import works on an existing VM and several formats
- Synology loaders and the NAS list match the current menu

web/messages/en/docs/create-vm/index.json

@@ -35,7 +35,7 @@
         "iconBg": "bg-emerald-100 text-emerald-700",
         "description": "Eight NAS operating systems as dedicated VMs. Most use the auto-ISO flow; Synology DSM runs the specialised loader wizard.",
         "bullets": [
-          "Synology DSM (ARC / RR / TinyCore loaders)",
+          "Synology DSM (Arc / RR / Alpine RedPill M-shell loaders)",
           "TrueNAS SCALE and CORE (ZFS)",
           "OpenMediaVault (Debian-based)",
           "XigmaNAS (FreeBSD ZFS)",
@@ -106,7 +106,7 @@
       },
       {
         "path": "vm/select_nas_iso.sh",
-        "role": "ISO / appliance selector for NAS systems (Synology, TrueNAS, OMV, Rockstor, ZimaOS)."
+        "role": "ISO / appliance selector for NAS systems (Synology, TrueNAS, OMV, Rockstor, XigmaNAS, ZimaOS, FygoOS)."
       },
       {
         "path": "vm/select_windows_iso.sh",

web/messages/en/docs/create-vm/system-nas/synology.json

@@ -171,7 +171,7 @@
     "heading": "Step-by-step loader configuration",
     "intro": "The six common steps are: start the VM, choose a model, choose a DSM version, choose add-ons, build and boot. Menus and options vary by release. The M-shell screenshots below show an earlier TinyCore interface; the current script downloads Alpine RedPill M-shell, so follow its current prompts.",
     "warnCalloutTitle": "Loaders are not maintained by ProxMenux",
-    "warnCalloutBody": "Arc, RR and TinyCore are community projects with their own release cadence. If a step looks different from the screenshots below, the loader has probably updated — check the loader's own documentation (links at the bottom of this page)."
+    "warnCalloutBody": "Arc, RR and Alpine RedPill M-shell are community projects with their own release cadence. If a step looks different from the screenshots below, the loader has probably updated — check the loader's own documentation (links at the bottom of this page)."
   },
   "stepBadge": "Step",
   "step1": {

web/messages/en/docs/create-vm/system-nas/system-nas-others.json

@@ -69,7 +69,7 @@
       },
       {
         "param": "CPU type",
-        "optionsRich": "Host, KVM64 and other listed CPU models"
+        "optionsRich": "Host, KVM64 and other listed CPU models (ZimaOS: Host or KVM64)"
       },
       {
         "param": "Cores",
@@ -106,7 +106,7 @@
     "virtualItemsRich": [
       "Lists the Proxmox storage volumes available on the host.",
       "You pick the target storage and the size in GB.",
-      "The disk uses the selected bus: SCSI (default), SATA, VirtIO or IDE. SATA slots are <code>sata0</code>, <code>sata1</code>, …, with six slots numbered 0–5."
+      "The disk uses the selected bus: SCSI (default), SATA, VirtIO or IDE (ZimaOS: SCSI or SATA). SATA slots are <code>sata0</code>, <code>sata1</code>, …, with six slots numbered 0–5."
     ],
     "importHeading": "b. Add import disk",
     "importItemsRich": [

web/messages/en/docs/create-vm/system-windows.json

@@ -237,7 +237,7 @@
       {
         "href": "/docs/disk-manager/import-disk-image-vm",
         "label": "Import Disk Image to VM",
-        "tail": " — import an existing Windows .vmdk into a new VM; convert .vhdx images to a supported format first."
+        "tail": " — import an existing Windows disk image (.vmdk, .qcow2, .img or .raw) into an existing VM; convert .vhdx images to a supported format first."
       },
       {
         "href": "/docs/hardware/gpu-vm-passthrough",