docs/devel/clocks.rst | 2 +- docs/devel/control-flow-integrity.rst | 2 +- docs/devel/docs.rst | 2 +- docs/devel/ebpf_rss.rst | 2 +- docs/devel/multi-process.rst | 6 +++--- docs/devel/submitting-a-patch.rst | 2 +- docs/interop/vfio-user.rst | 2 +- docs/specs/ppc-spapr-hcalls.rst | 2 +- docs/specs/ppc-spapr-xive.rst | 2 +- docs/system/security.rst | 2 +- docs/user/main.rst | 2 +- 11 files changed, 13 insertions(+), 13 deletions(-)
Signed-off-by: Filip Hejsek <filip.hejsek@gmail.com>
---
docs/devel/clocks.rst | 2 +-
docs/devel/control-flow-integrity.rst | 2 +-
docs/devel/docs.rst | 2 +-
docs/devel/ebpf_rss.rst | 2 +-
docs/devel/multi-process.rst | 6 +++---
docs/devel/submitting-a-patch.rst | 2 +-
docs/interop/vfio-user.rst | 2 +-
docs/specs/ppc-spapr-hcalls.rst | 2 +-
docs/specs/ppc-spapr-xive.rst | 2 +-
docs/system/security.rst | 2 +-
docs/user/main.rst | 2 +-
11 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/devel/clocks.rst b/docs/devel/clocks.rst
index 16de32147b..997b09c6a4 100644
--- a/docs/devel/clocks.rst
+++ b/docs/devel/clocks.rst
@@ -280,7 +280,7 @@ so you can use this to model clock controller devices which
have guest-programmable frequency multipliers or dividers.
Similarly to ``clock_set()``, ``clock_set_mul_div()`` returns ``true`` if
-the clock state was modified; that is, if the multiplier or the diviser
+the clock state was modified; that is, if the multiplier or the divisor
or both were changed by the call.
Note that ``clock_set_mul_div()`` does not automatically call
diff --git a/docs/devel/control-flow-integrity.rst b/docs/devel/control-flow-integrity.rst
index 3d5702fa4c..466888bdf1 100644
--- a/docs/devel/control-flow-integrity.rst
+++ b/docs/devel/control-flow-integrity.rst
@@ -39,7 +39,7 @@ are planning to also enable fuzzing, then Clang 11+ is needed (more on this
later).
Given the use of LTO, a version of AR that supports LLVM IR is required.
-The easies way of doing this is by selecting the AR provided by LLVM::
+The easiest way of doing this is by selecting the AR provided by LLVM::
AR=llvm-ar-9 CC=clang-9 CXX=clang++-9 /path/to/configure --enable-cfi
diff --git a/docs/devel/docs.rst b/docs/devel/docs.rst
index a7768b5311..7fe7e44429 100644
--- a/docs/devel/docs.rst
+++ b/docs/devel/docs.rst
@@ -5,7 +5,7 @@ QEMU Documentation
QEMU's documentation is written in reStructuredText format and
built using the Sphinx documentation generator. We generate both
-the HTML manual and the manpages from the some documentation sources.
+the HTML manual and the manpages from the same documentation sources.
hxtool and .hx files
--------------------
diff --git a/docs/devel/ebpf_rss.rst b/docs/devel/ebpf_rss.rst
index ed5d33767b..85ef547623 100644
--- a/docs/devel/ebpf_rss.rst
+++ b/docs/devel/ebpf_rss.rst
@@ -31,7 +31,7 @@ Not for all packets, the hash can/should be calculated.
Note: currently, eBPF RSS does not support hash reporting.
-eBPF RSS turned on by different combinations of vhost-net, vitrio-net and tap configurations:
+eBPF RSS turned on by different combinations of vhost-net, virtio-net and tap configurations:
- eBPF is used:
diff --git a/docs/devel/multi-process.rst b/docs/devel/multi-process.rst
index 4ef539c0b0..cafe2aaba7 100644
--- a/docs/devel/multi-process.rst
+++ b/docs/devel/multi-process.rst
@@ -158,7 +158,7 @@ IOMMUs introduce another level of complexity, since the address given to
the guest virtio device to DMA to or from is not a guest physical
address. This case is handled by having vhost code within QEMU register
as a listener for IOMMU mapping changes. The vhost application maintains
-a cache of IOMMMU translations: sending translation requests back to
+a cache of IOMMU translations: sending translation requests back to
QEMU on cache misses, and in turn receiving flush requests from QEMU
when mappings are purged.
@@ -573,7 +573,7 @@ live migration
When a remote process receives a live migration indication from QEMU, it
will set up a channel using the received file descriptor with
``qio_channel_socket_new_fd()``. This channel will be used to create a
-*QEMUfile* that can be passed to ``qemu_save_device_state()`` to send
+*QEMUFile* that can be passed to ``qemu_save_device_state()`` to send
the process's device state back to QEMU. This method will be reversed on
restore - the channel will be passed to ``qemu_loadvm_state()`` to
restore the device state.
@@ -853,7 +853,7 @@ intx irq descriptor
The irq descriptors are created by the proxy object
``using event_notifier_init()`` to create the irq and re-sampling
-*eventds*, and ``kvm_vm_ioctl(KVM_IRQFD)`` to bind them to an interrupt.
+*eventfds*, and ``kvm_vm_ioctl(KVM_IRQFD)`` to bind them to an interrupt.
The interrupt route can be found with
``pci_device_route_intx_to_irq()``.
diff --git a/docs/devel/submitting-a-patch.rst b/docs/devel/submitting-a-patch.rst
index 5ccd09a397..cd08881dfb 100644
--- a/docs/devel/submitting-a-patch.rst
+++ b/docs/devel/submitting-a-patch.rst
@@ -241,7 +241,7 @@ Use B4
~~~~~~
The `b4`_ tool, used for Linux kernel development, can also be used for QEMU
-development. It is packaged in most distros and PyPi. The QEMU source tree
+development. It is packaged in most distros and PyPI. The QEMU source tree
includes a ``b4`` project configuration file at the root: ``.b4-config``.
Example workflow to prepare a patch series:
diff --git a/docs/interop/vfio-user.rst b/docs/interop/vfio-user.rst
index 1c92f442d2..3428241dae 100644
--- a/docs/interop/vfio-user.rst
+++ b/docs/interop/vfio-user.rst
@@ -1505,7 +1505,7 @@ Neither the request or reply have a payload.
--------------------------------
This message can be used to coalesce multiple device write operations
-into a single messgage. It is only used as an optimization when the
+into a single message. It is only used as an optimization when the
outgoing message queue is relatively full.
Request
diff --git a/docs/specs/ppc-spapr-hcalls.rst b/docs/specs/ppc-spapr-hcalls.rst
index 6cdcef2026..550026ea55 100644
--- a/docs/specs/ppc-spapr-hcalls.rst
+++ b/docs/specs/ppc-spapr-hcalls.rst
@@ -20,7 +20,7 @@ to an implementation specific range in PAPR.
``H_RTAS (0xf000)``
===================
-RTAS stands for Run-Time Abstraction Sercies and is a set of runtime services
+RTAS stands for Run-Time Abstraction Services and is a set of runtime services
generally provided by the firmware inside the guest to the operating system. It
predates the existence of hypervisors (it was originally an extension to Open
Firmware) and is still used by PAPR and LoPAR to provide various services that
diff --git a/docs/specs/ppc-spapr-xive.rst b/docs/specs/ppc-spapr-xive.rst
index f47f739e01..8b83942a29 100644
--- a/docs/specs/ppc-spapr-xive.rst
+++ b/docs/specs/ppc-spapr-xive.rst
@@ -171,7 +171,7 @@ native exploitation mode* is selected should contain:
- ``reg``
contains the base address and size of the thread interrupt
- managnement areas (TIMA), for the User level and for the Guest OS
+ management areas (TIMA), for the User level and for the Guest OS
level. Only the Guest OS level is taken into account today.
- ``ibm,xive-eq-sizes``
diff --git a/docs/system/security.rst b/docs/system/security.rst
index 75e39caede..1bd8423866 100644
--- a/docs/system/security.rst
+++ b/docs/system/security.rst
@@ -107,7 +107,7 @@ an issue as a normal bug.
possibility of large memory peaks and apply countermeasures to
provide continuity of host operations. It is typical for the Linux
OOM killer to reap the process triggering host memory overcommit
- in the case of exccessive usage, offering a degree of protection.
+ in the case of excessive usage, offering a degree of protection.
As such, bugs which can lead to excessive/unbounded memory allocations
will usually not be classified as security flaws, but should be
fixed as hardening bugs.
diff --git a/docs/user/main.rst b/docs/user/main.rst
index a8ddf91424..aef33bfd9a 100644
--- a/docs/user/main.rst
+++ b/docs/user/main.rst
@@ -23,7 +23,7 @@ System call translation
System calls are the principle interface between user-space and the
kernel. Generally the same system calls exist on all versions of the
kernel so QEMU includes a generic system call translator. The
-translator takes care of adjusting endianess, 32/64 bit parameter size
+translator takes care of adjusting endianness, 32/64 bit parameter size
and then calling the equivalent host system call.
QEMU can also adjust device specific ``ioctl()`` calls in a similar
---
base-commit: d7a65d1793d691d356a56833620f7d1e6f5d653b
change-id: 20261006-typos-in-docs-36cfdbbe52d3
Best regards,
--
Filip Hejsek <filip.hejsek@gmail.com>On Mon, Oct 12, 2026 at 12:34 PM Filip Hejsek <filip.hejsek@gmail.com> wrote: > > Signed-off-by: Filip Hejsek <filip.hejsek@gmail.com> LGTM Reviewed-by: John Snow <jsnow@redhat.com> Thanks! > --- > docs/devel/clocks.rst | 2 +- > docs/devel/control-flow-integrity.rst | 2 +- > docs/devel/docs.rst | 2 +- > docs/devel/ebpf_rss.rst | 2 +- > docs/devel/multi-process.rst | 6 +++--- > docs/devel/submitting-a-patch.rst | 2 +- > docs/interop/vfio-user.rst | 2 +- > docs/specs/ppc-spapr-hcalls.rst | 2 +- > docs/specs/ppc-spapr-xive.rst | 2 +- > docs/system/security.rst | 2 +- > docs/user/main.rst | 2 +- > 11 files changed, 13 insertions(+), 13 deletions(-) > > diff --git a/docs/devel/clocks.rst b/docs/devel/clocks.rst > index 16de32147b..997b09c6a4 100644 > --- a/docs/devel/clocks.rst > +++ b/docs/devel/clocks.rst > @@ -280,7 +280,7 @@ so you can use this to model clock controller devices which > have guest-programmable frequency multipliers or dividers. > > Similarly to ``clock_set()``, ``clock_set_mul_div()`` returns ``true`` if > -the clock state was modified; that is, if the multiplier or the diviser > +the clock state was modified; that is, if the multiplier or the divisor > or both were changed by the call. > > Note that ``clock_set_mul_div()`` does not automatically call > diff --git a/docs/devel/control-flow-integrity.rst b/docs/devel/control-flow-integrity.rst > index 3d5702fa4c..466888bdf1 100644 > --- a/docs/devel/control-flow-integrity.rst > +++ b/docs/devel/control-flow-integrity.rst > @@ -39,7 +39,7 @@ are planning to also enable fuzzing, then Clang 11+ is needed (more on this > later). > > Given the use of LTO, a version of AR that supports LLVM IR is required. > -The easies way of doing this is by selecting the AR provided by LLVM:: > +The easiest way of doing this is by selecting the AR provided by LLVM:: > > AR=llvm-ar-9 CC=clang-9 CXX=clang++-9 /path/to/configure --enable-cfi > > diff --git a/docs/devel/docs.rst b/docs/devel/docs.rst > index a7768b5311..7fe7e44429 100644 > --- a/docs/devel/docs.rst > +++ b/docs/devel/docs.rst > @@ -5,7 +5,7 @@ QEMU Documentation > > QEMU's documentation is written in reStructuredText format and > built using the Sphinx documentation generator. We generate both > -the HTML manual and the manpages from the some documentation sources. > +the HTML manual and the manpages from the same documentation sources. > > hxtool and .hx files > -------------------- > diff --git a/docs/devel/ebpf_rss.rst b/docs/devel/ebpf_rss.rst > index ed5d33767b..85ef547623 100644 > --- a/docs/devel/ebpf_rss.rst > +++ b/docs/devel/ebpf_rss.rst > @@ -31,7 +31,7 @@ Not for all packets, the hash can/should be calculated. > > Note: currently, eBPF RSS does not support hash reporting. > > -eBPF RSS turned on by different combinations of vhost-net, vitrio-net and tap configurations: > +eBPF RSS turned on by different combinations of vhost-net, virtio-net and tap configurations: > > - eBPF is used: > > diff --git a/docs/devel/multi-process.rst b/docs/devel/multi-process.rst > index 4ef539c0b0..cafe2aaba7 100644 > --- a/docs/devel/multi-process.rst > +++ b/docs/devel/multi-process.rst > @@ -158,7 +158,7 @@ IOMMUs introduce another level of complexity, since the address given to > the guest virtio device to DMA to or from is not a guest physical > address. This case is handled by having vhost code within QEMU register > as a listener for IOMMU mapping changes. The vhost application maintains > -a cache of IOMMMU translations: sending translation requests back to > +a cache of IOMMU translations: sending translation requests back to > QEMU on cache misses, and in turn receiving flush requests from QEMU > when mappings are purged. > > @@ -573,7 +573,7 @@ live migration > When a remote process receives a live migration indication from QEMU, it > will set up a channel using the received file descriptor with > ``qio_channel_socket_new_fd()``. This channel will be used to create a > -*QEMUfile* that can be passed to ``qemu_save_device_state()`` to send > +*QEMUFile* that can be passed to ``qemu_save_device_state()`` to send > the process's device state back to QEMU. This method will be reversed on > restore - the channel will be passed to ``qemu_loadvm_state()`` to > restore the device state. > @@ -853,7 +853,7 @@ intx irq descriptor > > The irq descriptors are created by the proxy object > ``using event_notifier_init()`` to create the irq and re-sampling > -*eventds*, and ``kvm_vm_ioctl(KVM_IRQFD)`` to bind them to an interrupt. > +*eventfds*, and ``kvm_vm_ioctl(KVM_IRQFD)`` to bind them to an interrupt. > The interrupt route can be found with > ``pci_device_route_intx_to_irq()``. > > diff --git a/docs/devel/submitting-a-patch.rst b/docs/devel/submitting-a-patch.rst > index 5ccd09a397..cd08881dfb 100644 > --- a/docs/devel/submitting-a-patch.rst > +++ b/docs/devel/submitting-a-patch.rst > @@ -241,7 +241,7 @@ Use B4 > ~~~~~~ > > The `b4`_ tool, used for Linux kernel development, can also be used for QEMU > -development. It is packaged in most distros and PyPi. The QEMU source tree > +development. It is packaged in most distros and PyPI. The QEMU source tree > includes a ``b4`` project configuration file at the root: ``.b4-config``. > > Example workflow to prepare a patch series: > diff --git a/docs/interop/vfio-user.rst b/docs/interop/vfio-user.rst > index 1c92f442d2..3428241dae 100644 > --- a/docs/interop/vfio-user.rst > +++ b/docs/interop/vfio-user.rst > @@ -1505,7 +1505,7 @@ Neither the request or reply have a payload. > -------------------------------- > > This message can be used to coalesce multiple device write operations > -into a single messgage. It is only used as an optimization when the > +into a single message. It is only used as an optimization when the > outgoing message queue is relatively full. > > Request > diff --git a/docs/specs/ppc-spapr-hcalls.rst b/docs/specs/ppc-spapr-hcalls.rst > index 6cdcef2026..550026ea55 100644 > --- a/docs/specs/ppc-spapr-hcalls.rst > +++ b/docs/specs/ppc-spapr-hcalls.rst > @@ -20,7 +20,7 @@ to an implementation specific range in PAPR. > ``H_RTAS (0xf000)`` > =================== > > -RTAS stands for Run-Time Abstraction Sercies and is a set of runtime services > +RTAS stands for Run-Time Abstraction Services and is a set of runtime services > generally provided by the firmware inside the guest to the operating system. It > predates the existence of hypervisors (it was originally an extension to Open > Firmware) and is still used by PAPR and LoPAR to provide various services that > diff --git a/docs/specs/ppc-spapr-xive.rst b/docs/specs/ppc-spapr-xive.rst > index f47f739e01..8b83942a29 100644 > --- a/docs/specs/ppc-spapr-xive.rst > +++ b/docs/specs/ppc-spapr-xive.rst > @@ -171,7 +171,7 @@ native exploitation mode* is selected should contain: > - ``reg`` > > contains the base address and size of the thread interrupt > - managnement areas (TIMA), for the User level and for the Guest OS > + management areas (TIMA), for the User level and for the Guest OS > level. Only the Guest OS level is taken into account today. > > - ``ibm,xive-eq-sizes`` > diff --git a/docs/system/security.rst b/docs/system/security.rst > index 75e39caede..1bd8423866 100644 > --- a/docs/system/security.rst > +++ b/docs/system/security.rst > @@ -107,7 +107,7 @@ an issue as a normal bug. > possibility of large memory peaks and apply countermeasures to > provide continuity of host operations. It is typical for the Linux > OOM killer to reap the process triggering host memory overcommit > - in the case of exccessive usage, offering a degree of protection. > + in the case of excessive usage, offering a degree of protection. > As such, bugs which can lead to excessive/unbounded memory allocations > will usually not be classified as security flaws, but should be > fixed as hardening bugs. > diff --git a/docs/user/main.rst b/docs/user/main.rst > index a8ddf91424..aef33bfd9a 100644 > --- a/docs/user/main.rst > +++ b/docs/user/main.rst > @@ -23,7 +23,7 @@ System call translation > System calls are the principle interface between user-space and the > kernel. Generally the same system calls exist on all versions of the > kernel so QEMU includes a generic system call translator. The > -translator takes care of adjusting endianess, 32/64 bit parameter size > +translator takes care of adjusting endianness, 32/64 bit parameter size > and then calling the equivalent host system call. > > QEMU can also adjust device specific ``ioctl()`` calls in a similar > > --- > base-commit: d7a65d1793d691d356a56833620f7d1e6f5d653b > change-id: 20261006-typos-in-docs-36cfdbbe52d3 > > Best regards, > -- > Filip Hejsek <filip.hejsek@gmail.com> >
© 2016 - 2026 Red Hat, Inc.