Fix several typos in documentation (found by codespell)
Signed-off-by: Stefan Weil <sw@weilnetz.de> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org> [Mjt: add 2 fixes suggested by Peter: "as a" and "deactivate"] Reviewed-by: Michael Tokarev <mjt@tls.msk.ru> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Stefan Weil committed
Mar 19, 2026 at 19:34 UTC
b7ae542de40364cccb683a67e5f891d3ef69818f
11 files changed
+20
-20
contrib/plugins/traps.c
+1
-1
@@ -4,7 +4,7 @@
4
*
5
* Traps - count traps
6
*
7
- * Count the number of interrupts (asyncronous events), exceptions (synchronous
7
+ * Count the number of interrupts (asynchronous events), exceptions (synchronous
8
* events) and host calls (e.g. semihosting) per cpu and report those counts on
9
* exit.
10
*/
docs/about/emulation.rst
+1
-1
@@ -1043,7 +1043,7 @@ Count traps
1043
1044
``contrib/plugins/traps.c``
1045
1046
-This plugin counts the number of interrupts (asyncronous events), exceptions
1046
+This plugin counts the number of interrupts (asynchronous events), exceptions
1047
(synchronous events) and host calls (e.g. semihosting) per cpu.
1048
1049
Other emulation features
docs/devel/code-provenance.rst
+2
-2
@@ -213,7 +213,7 @@ The general principles when picking up abandoned work are:
213
* Indicate where the original patch was obtained from (mailing list, bug
214
tracker, author's git repo, etc) when sending it for review
215
* Acknowledge the extra work of the new contributor by including their
216
- ``Signed-off-by`` in the patch in addition to the orignal author's
216
+ ``Signed-off-by`` in the patch in addition to the original author's
217
* Indicate who is responsible for what parts of the patch. This is typically
218
done via a note in the commit message, just prior to the new contributor's
219
``Signed-off-by``::
@@ -259,7 +259,7 @@ process. A non-exhaustive list of examples is:
259
container images from a clean git checkout.
260
261
* eBPF: QEMU includes some generated eBPF machine code, since the required
262
- eBPF compilation tools are not broadly available on all targetted OS
262
+ eBPF compilation tools are not broadly available on all targeted OS
263
distributions. The corresponding eBPF C code for the binary is also
264
provided. This is a time-limited exception until the eBPF toolchain is
265
sufficiently broadly available in distros.
docs/system/tls.rst
+4
-4
@@ -76,10 +76,10 @@ loaded certificate will preferred. IOW file naming can influence
76
which certificates are used for a session.
77
78
The use of multiple sets of certificates is intended to allow an
79
-incremental transition to certificates using different crytographic
79
+incremental transition to certificates using different cryptographic
80
algorithms. This allows a newly deployed QEMU to introduce use of
81
stronger cryptographic algorithms that will be preferred when talking
82
-to other newly deployed QEMU instances, while retaining compatbility
82
+to other newly deployed QEMU instances, while retaining compatibility
83
with certificates issued to a historically deployed QEMU. This is
84
notably useful to support live migration from an old QEMU deployed
85
on older operating system releases, which may support fewer crypto
@@ -350,7 +350,7 @@ TLS certificates for Post-Quantum Cryptography
350
351
Given a new enough gnutls release, suitably integrated & configured with the
352
operating system crypto policies, QEMU is able to support post-quantum
353
-crytography on TLS enabled services, either exclusively or in a hybrid mode.
353
+cryptography on TLS enabled services, either exclusively or in a hybrid mode.
354
355
In exclusive mode, only a single set of certificates need to be configured
356
for QEMU, with PQC compliant algorithms. Such a QEMU configuration will only
@@ -404,7 +404,7 @@ Force disabling PQC via crypto priority
404
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
405
406
In the OS configuration for system crypto algorithm priorities has
407
-enabled PQC, this can (optionally) be overriden in QEMU configuration
407
+enabled PQC, this can (optionally) be overridden in QEMU configuration
408
disable use of PQC using the ``priority`` parameter to the ``tls-creds-x509``
409
object::
410
hw/arm/virt.c
+1
-1
@@ -2784,7 +2784,7 @@ static void virt_set_msi(Object *obj, const char *value, Error **errp)
2784
VirtMachineState *vms = VIRT_MACHINE(obj);
2785
2786
if (!strcmp(value, "auto")) {
2787
- vms->msi_controller = VIRT_MSI_CTRL_AUTO; /* Will be overriden later */
2787
+ vms->msi_controller = VIRT_MSI_CTRL_AUTO; /* Will be overridden later */
2788
} else if (!strcmp(value, "its")) {
2789
vms->msi_controller = VIRT_MSI_CTRL_ITS;
2790
} else if (!strcmp(value, "gicv2m")) {
include/hw/arm/virt.h
+1
-1
@@ -101,7 +101,7 @@ typedef enum VirtIOMMUType {
101
102
typedef enum VirtMSIControllerType {
103
VIRT_MSI_CTRL_NONE,
104
- /* This value is overriden at runtime.*/
104
+ /* This value is overridden at runtime.*/
105
VIRT_MSI_CTRL_AUTO,
106
/* Legacy option: its=off provides a GICv2m when using GICv2 */
107
VIRT_MSI_LEGACY_OPT_ITS_OFF,
include/plugins/qemu-plugin.h
+1
-1
@@ -1125,7 +1125,7 @@ bool qemu_plugin_read_register(struct qemu_plugin_register *handle,
1125
* Attempting to write a register with @buf smaller than the register size
1126
* will result in a crash or other undesired behavior.
1127
*
1128
- * Returns true on sucess, false on failure.
1128
+ * Returns true on success, false on failure.
1129
*/
1130
QEMU_PLUGIN_API
1131
bool qemu_plugin_write_register(struct qemu_plugin_register *handle,
qapi/block-core.json
+4
-4
@@ -3122,7 +3122,7 @@
3122
# the device to write to the target path only. Note that drive
3123
# mirroring includes `drive-mirror`, `blockdev-mirror` and
3124
# `block-commit` job (only in case of "active commit", when the node
3125
-# being commited is used by the guest). The ability to complete is
3125
+# being committed is used by the guest). The ability to complete is
3126
# signaled with a `BLOCK_JOB_READY` event.
3127
#
3128
# This command completes an active background block operation
@@ -5086,14 +5086,14 @@
5086
##
5087
# @blockdev-set-active:
5088
#
5089
-# Activate or inactivate a block device. Use this to manage the
5089
+# Activate or deactivate a block device. Use this to manage the
5090
# handover of block devices on migration with qemu-storage-daemon.
5091
#
5092
# Activating a node automatically activates all of its child nodes
5093
-# first. Inactivating a node automatically inactivates any of its
5093
+# first. Deactivating a node automatically deactivates any of its
5094
# child nodes that are not in use by a still active node.
5095
#
5096
-# @node-name: Name of the graph node to activate or inactivate. By
5096
+# @node-name: Name of the graph node to activate or deactivate. By
5097
# default, all nodes are affected by the operation.
5098
#
5099
# @active: true if the nodes should be active when the command returns
qapi/job.json
+1
-1
@@ -196,7 +196,7 @@
196
# the device to write to the target path only. Note that drive
197
# mirroring includes `drive-mirror`, `blockdev-mirror` and
198
# `block-commit` job (only in case of "active commit", when the node
199
-# being commited is used by the guest). The ability to complete is
199
+# being committed is used by the guest). The ability to complete is
200
# signaled with a `BLOCK_JOB_READY` event.
201
#
202
# This command completes an active background block operation
qapi/uefi.json
+1
-1
@@ -18,7 +18,7 @@
18
##
19
# @UefiVariable:
20
#
21
-# UEFI Variable. Check the UEFI specifification for more detailed
21
+# UEFI Variable. Check the UEFI specification for more detailed
22
# information on the fields.
23
#
24
# @guid: variable namespace GUID
qemu-options.hx
+3
-3
@@ -3223,7 +3223,7 @@ SRST
3223
Enable/disable list in DHCP/DHCPv6/NDP
3224
3225
``map-host-loopback``
3226
- Addresse to refer to host
3226
+ Address to refer to host
3227
3228
``map-guest-addr``
3229
Addr to translate to guest's address
@@ -3271,8 +3271,8 @@ SRST
3271
UDP ports to forward
3272
3273
``param=string``
3274
- ``string`` will be passed to passt has a command line parameter,
3275
- we can have multiple occurences of the ``param`` parameter to
3274
+ ``string`` will be passed to passt as a command line parameter,
3275
+ we can have multiple occurrences of the ``param`` parameter to
3276
pass multiple parameters to passt.
3277
3278
For instance, to pass ``--trace --log=trace.log``: