Update website/content/en/status/report-2023-04-2023-06/kboot.adoc

Co-authored-by: Graham Perrin <[email protected]>

website/content/en/status/report-2023-04-2023-06/kboot.adoc

@@ -17,7 +17,7 @@ The normal FreeBSD /boot/loader is built as a Linux binary that reads in the Fre
 It places them into memory as if it were running in a pre-boot environment and then loads that image into the Linux kernel with man:kexec_load[2] and does a special reboot to that kernel image.
 For UEFI enabled systems, it passes the UEFI memory table, and pointer to UEFI runtime services to the new kernel.
 
-It supports loading files from the host's filesystem, from any loader(8) supported filesystem on the host's block devices (including ZPOOLS that span multiple devices), from ram disk images and from files downloaded over the network.
+It supports loading files from the host's filesystem, from any man:loader[8]-supported filesystem on the host's block devices (including pools that span multiple devices), from ram disk images and from files downloaded over the network.
 Any mix of these is available, so configuraiton overrides can be loaded from the host's filesystem, but the kernel can be loaded from dedicated storage (say NVME) or a ram disk image.
 It supports a host console running over stdin/stdout.
 It supports explicit locations like `/dev/nvme0ns1:/boot/loader/gerbil.conf` to be explicit about where to load filesystems from.