Fix some typos

Signed-off-by: Tim Wiederhake <twiederh@redhat.com>

diff --git a/NEWS.rst b/NEWS.rst
index 089ad733f2db685cb5fe31eedc754e5f18e8e3c1..490886beb4fc91ed627599575172cf4e2c525521 100644 (file)
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -258,7 +258,7 @@ v8.10.0 (2022-12-01)
 
   * Support for SGX EPC (enclave page cache)
 
-    Users can add a ``<memory model='sgx-epc'>`` device to lauch a VM with
+    Users can add a ``<memory model='sgx-epc'>`` device to launch a VM with
     ``Intel Software Guard Extensions``.
 
   * Support migration of vTPM state of QEMU vms on shared storage
@@ -295,7 +295,7 @@ v8.10.0 (2022-12-01)
 
   * RPM packaging changes
 
-    - add optional dependancy of ``libvirt-daemon`` on ``libvirt-client``
+    - add optional dependency of ``libvirt-daemon`` on ``libvirt-client``
 
       The ``libvirt-guests.`` tool requires the ``virsh`` client to work
       properly, but we don't want to require the installation of the daemon
@@ -321,7 +321,7 @@ v8.10.0 (2022-12-01)
   * Allow incoming connections to guests on routed networks w/firewalld
 
     A change in handling of implicit rules in ``firewalld 1.0.0`` broke
-    incomming connections to VMs when using ``routed`` network. This is fixed
+    incoming connections to VMs when using ``routed`` network. This is fixed
     by adding a new ``libvirt-routed`` zone configured to once again allow
     incoming sessions to guests on routed networks.
 

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index da059f9aac1be5a6ab96311d96395a8826975322..80612382caef09e73efbb7fb1bd7cf58fd7eaedf 100644 (file)
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -7576,7 +7576,7 @@ feature is planned for a future version of libvirt.
 
 Having multiple watchdogs is usually not something very common, but be aware
 that this might happen, for example, when an implicit watchdog device is added
-as part of another device.  For example whe iTCO watchdog being part of the ich9
+as part of another device.  For example the iTCO watchdog being part of the ich9
 southbridge, which is used with the q35 machine type. :since:`Since 9.1.0`
 
 ::

diff --git a/docs/kbase/launch_security_sev.rst b/docs/kbase/launch_security_sev.rst
index f3c8695f73584cd3cb254024c3339abf75fbc425..6a3740d297fd2dddde16c596e9b0a51c39fab2bb 100644 (file)
--- a/docs/kbase/launch_security_sev.rst
+++ b/docs/kbase/launch_security_sev.rst
@@ -460,7 +460,7 @@ With it launched, it is possible to query the launch measurement::
   sev-build-id   : 15
   sev-policy     : 3
 
-The techiques required to validate the measurement reported are beyond the
+The techniques required to validate the measurement reported are beyond the
 scope of this document. Fortunately, libvirt provides a tool that can be used
 to perform this validation::
 

diff --git a/examples/systemtap/amd-sev-es-vmsa.stp b/examples/systemtap/amd-sev-es-vmsa.stp
index 2ac0b6eb53d380f3ed3b38993ceab935077d13b5..604c494a3a408df3d60ce6c1485e97c68ba06bc2 100644 (file)
--- a/examples/systemtap/amd-sev-es-vmsa.stp
+++ b/examples/systemtap/amd-sev-es-vmsa.stp
@@ -21,7 +21,7 @@
 #
 # NOTE: This directly references specific structures and places in the
 #       kernel source code. It is expected that this example will need to be
-#       editted to match the kernel you intend to run it against.
+#       edited to match the kernel you intend to run it against.
 #
 # The captured VMSA will be printed to the console in hex format,
 # and can be converted to the required binary format by feeding
@@ -42,8 +42,8 @@ function dump_vmsa(addr:long) {
 }
 
 # This line number will need to be updated for the specific kernel
-# version that is being probed. The line that needs to be targetted
-# is the one beween the call to clflush_cache_range(...) and the
+# version that is being probed. The line that needs to be targeted
+# is the one between the call to clflush_cache_range(...) and the
 # call to sev_issue_cmd(kvm, SEV_CMD_LAUNCH_UPDATE...).
 #
 # Line 635 is correct for Linux v6.3

diff --git a/src/qemu/qemu_fd.c b/src/qemu/qemu_fd.c
index d613f220321af0a54b5ec6abe6fb7b78dda6209a..feab907afd794b988f1df7f3d72d3627cc122266 100644 (file)
--- a/src/qemu/qemu_fd.c
+++ b/src/qemu/qemu_fd.c
@@ -98,7 +98,7 @@ qemuFDPassNew(const char *prefix,
 
 /**
  * qemuFDPassNewPassed:
- * @fdSetID: ID of an FDset which was allready passed to qemu
+ * @fdSetID: ID of an FDset which was already passed to qemu
  *
  * Create qemuFDPass pointing to an already passed FD. Useful to use with
  * qemuFDPassTransferMonitorRollback, when restoring after restart.

diff --git a/src/storage_file/storage_source.c b/src/storage_file/storage_source.c
index baa182261f68b22b538bcc682b71a9708db65260..0846c400c8048d9b24adf952fa3819efb5cb1c25 100644 (file)
--- a/src/storage_file/storage_source.c
+++ b/src/storage_file/storage_source.c
@@ -330,7 +330,7 @@ virStorageSourceChainLookup(virStorageSource *chain,
  *
  * Looks up a storage source definition corresponding to @base in @chain.
  *
- * Returns virStorageSource withing chain or NULL if not found.
+ * Returns virStorageSource within chain or NULL if not found.
  */
 virStorageSource *
 virStorageSourceChainLookupBySource(virStorageSource *chain,

diff --git a/tests/testutilsqemu.c b/tests/testutilsqemu.c
index af3835a411a518dbe50277d1a77eff7cfd1c0ea9..a5780dc746c2323ca22a330a860d2631856707fe 100644 (file)
--- a/tests/testutilsqemu.c
+++ b/tests/testutilsqemu.c
@@ -476,7 +476,7 @@ qemuTestCapsCacheInsertImpl(virFileCache *cache,
     size_t i;
 
     if (virQEMUCapsGetArch(caps) != VIR_ARCH_NONE) {
-        /* all tests using real caps or arcitecture are expected to call:
+        /* all tests using real caps or architecture are expected to call:
          *
          *  virFileCacheClear(driver.qemuCapsCache);
          *