--- wikisrc/ports/xen/howto.mdwn	2020/11/15 15:31:47	1.187
+++ wikisrc/ports/xen/howto.mdwn	2020/11/15 15:36:35	1.188
@@ -459,14 +459,14 @@ down cleanly on dom0 shutdown, add the f
 xendomains="domU-netbsd domU-linux"
 """]]
 
-# Creating a domU
+# domU setup for specific systems
 
 Creating domUs is almost entirely independent of operating system.  We
-have already presented the basics of config files.  Note that you must
-have already completed the dom0 setup so that "xl list" works.
+have already presented the basics of config files in the previous system.
 
-## Creating a NetBSD PV domU
+Of course, this section presumes that you have a working dom0.
 
+## Creating a NetBSD PV domU
 
 See the earlier config file, and adjust memory.  Decide on how much
 storage you will provide, and prepare it (file or LVM).
@@ -475,14 +475,14 @@ While the kernel will be obtained from t
 file should be present in the domU as /netbsd so that tools like
 savecore(8) can work.   (This is helpful but not necessary.)
 
-The kernel must be specifically for Xen and for use as a domU.  The
-i386 and amd64 provide the following kernels:
+The kernel must be specifically built for Xen, to use PV interfacesas
+a domU.  NetBSD release builds provide the following kernels:
 
         i386 XEN3PAE_DOMU
         amd64 XEN3_DOMU
 
 This will boot NetBSD, but this is not that useful if the disk is
-empty.  One approach is to unpack sets onto the disk outside of xen
+empty.  One approach is to unpack sets onto the disk outside of Xen
 (by mounting it, just as you would prepare a physical disk for a
 system you can't run the installer on).
 
@@ -502,11 +502,11 @@ line should be used in the config file.
 After booting the domain, the option to install via CDROM may be
 selected.  The CDROM device should be changed to `xbd1d`.
 
-Once done installing, "halt -p" the new domain (don't reboot or halt,
+Once done installing, "halt -p" the new domain (don't reboot or halt:
 it would reload the INSTALL_XEN3_DOMU kernel even if you changed the
 config file), switch the config file back to the XEN3_DOMU kernel,
 and start the new domain again. Now it should be able to use "root on
-xbd0a" and you should have a, functional NetBSD domU.
+xbd0a" and you should have a functional NetBSD domU.
 
 TODO: check if this is still accurate.
 When the new domain is booting you'll see some warnings about *wscons*