From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] fixed grammar in qm manpage
Date: Fri, 2 Dec 2022 12:52:21 +0100 [thread overview]
Message-ID: <20221202115221.3645762-1-n.ullreich@proxmox.com> (raw)
Fixed two small grammar errors in the qm manpage. Rephrased a
sentence before the fixed sentence so that it would be more legible.
Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
qm.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index f923ccf..6f8f8ec 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -252,7 +252,7 @@ IO Thread
The option *IO Thread* can only be used when using a disk with the
*VirtIO* controller, or with the *SCSI* controller, when the emulated controller
type is *VirtIO SCSI single*.
-With this enabled, Qemu creates one I/O thread per storage controller,
+With this enabled, Qemu creates one I/O thread per storage controller
rather than a single thread for all I/O. This can increase performance when
multiple disks are used and each disk has its own storage controller.
@@ -764,7 +764,7 @@ open-source, x86 BIOS implementation. SeaBIOS is a good choice for most
standard setups.
Some operating systems (such as Windows 11) may require use of an UEFI
-compatible implementation instead. In such cases, you must rather use *OVMF*,
+compatible implementation. In such cases, you must use *OVMF* instead,
which is an open-source UEFI implementation. footnote:[See the OVMF Project https://github.com/tianocore/tianocore.github.io/wiki/OVMF]
There are other scenarios in which the SeaBIOS may not be the ideal firmware to
--
2.30.2
next reply other threads:[~2022-12-02 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 11:52 Noel Ullreich [this message]
2023-01-16 15:53 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221202115221.3645762-1-n.ullreich@proxmox.com \
--to=n.ullreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox