Re: [PATCH pve-docs 2/2] qm: pci passthrough: fix grammar and spelling

["Michael Köppl" <m.koeppl@proxmox.com>]

2 nits inline, other than that I like the changes!

Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>

On Tue Aug 25, 2026 at 1:46 PM CEST, Jakob Klocker wrote:

[snip]
 
> @@ -300,13 +300,14 @@ VM Configuration
>  When passing through a GPU, the best compatibility is reached when using
>  'q35' as machine type, 'OVMF' ('UEFI' for VMs) instead of SeaBIOS and PCIe
>  instead of PCI. Note that if you want to use 'OVMF' for GPU passthrough, the
> -GPU needs to have an UEFI capable ROM, otherwise use SeaBIOS instead. To check if
> +GPU needs to have a UEFI-capable ROM, otherwise use SeaBIOS instead. To check if
>  the ROM is UEFI capable, see the
>  https://pve.proxmox.com/wiki/PCI_Passthrough#How_to_know_if_a_graphics_card_is_UEFI_.28OVMF.29_compatible[PCI Passthrough Examples]
>  wiki.
>  
> -Furthermore, using OVMF, disabling vga arbitration may be possible, reducing the
> -amount of legacy code needed to be run during boot. To disable vga arbitration:
> +Furthermore, when using OVMF, you may be able to disable VGA arbitration,

nit: might just be me, but to me "you may be able to..." reads like the
the person now has the ability to do so. Maybe something like "VGA
arbitration can potentially be disabled" would be more fitting.

> +which reduces the amount of legacy code that needs to run at boot.
> +To disable VGA arbitration:
>  
>  ----
>   echo "options vfio-pci ids=<vendor-id>,<device-id> disable_vga=1" > /etc/modprobe.d/vfio.conf
> @@ -335,17 +336,17 @@ or by adding a line to the VM configuration file:

[snip]

> +a single device to provide multiple 'VFs' (**V**irtual **F**unctions) to the
> +system. Each of those 'VFs' can be used in a different VM, with full hardware
> +features and also better performance and lower latency than software-virtualized
> +devices.
>  
> -Currently, the most common use case for this are NICs (**N**etwork
> +Currently, the most common use case for this is NICs (**N**etwork

nit: both versions read a bit awkward to me, even though the second is
grammatically correct. Maybe something like "Currently, the most common
use case for this is with NICs" could work.

>  **I**nterface **C**ard) with SR-IOV support, which can provide multiple VFs per
> -physical port. This allows using features such as checksum offloading, etc. to
> -be used inside a VM, reducing the (host) CPU overhead.
> +physical port. This allows features such as checksum offloading to be used 
> +inside a VM, reducing the (host) CPU overhead.
>  
>  Host Configuration

[snip]