fix up Makefile

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index cf39226e23d971339fe0c71c4c52c7be5e4f6f26..81fd39ec06e3d8c55a5f2716deb0b8ec10de9dbd 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -126,8 +126,8 @@ BIOS clock to have the UTC time.
 System Settings
 ~~~~~~~~~~~~~~~
 
-On VM creation you can change the type some basic system components of the new
-VM. You can specify which xref:qm_display[display type] you want to use.
+On VM creation you can change some basic system components of the new VM. You
+can specify which xref:qm_display[display type] you want to use.
 [thumbnail="screenshot/gui-create-vm-system.png"]
 Additionally, the xref:qm_hard_disk[SCSI controller] can be changed.
 If you plan to install the QEMU Guest Agent, or if your selected ISO image
@@ -699,8 +699,12 @@ BIOS and UEFI
 ~~~~~~~~~~~~~
 
 In order to properly emulate a computer, QEMU needs to use a firmware.
-By default QEMU uses *SeaBIOS* for this, which is an open-source, x86 BIOS
-implementation. SeaBIOS is a good choice for most standard setups.
+Which, on common PCs often known as BIOS or (U)EFI, is executed as one of the
+first steps when booting a VM. It is responsible for doing basic hardware
+initialization and for providing an interface to the firmware and hardware for
+the operating system. By default QEMU uses *SeaBIOS* for this, which is an
+open-source, x86 BIOS implementation. SeaBIOS is a good choice for most
+standard setups.
 
 There are, however, some scenarios in which a BIOS is not a good firmware
 to boot from, e.g. if you want to do VGA passthrough. footnote:[Alex Williamson has a very good blog entry about this.
@@ -1077,7 +1081,7 @@ include::qm-pci-passthrough.adoc[]
 endif::wiki[]
 
 Hookscripts
-~~~~~~~~~~~
+-----------
 
 You can add a hook script to VMs with the config property `hookscript`.