docs: Fix some typos

Found with the codespell utility.

Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>

diff --git a/docs/formatcaps.rst b/docs/formatcaps.rst
index da6b215780bce001d920c432889e78cf73360815..7e525487e72574a878f00f1144617b2406363dd0 100644 (file)
--- a/docs/formatcaps.rst
+++ b/docs/formatcaps.rst
@@ -39,7 +39,7 @@ The ``<host/>`` element consists of the following child elements:
    The host CPU architecture and features.
 
    Note that, while this element contains a ``topology`` sub-element,
-   the information contained therein is farily high-level and likely
+   the information contained therein is fairly high-level and likely
    not very useful when it comes to optimizing guest vCPU placement.
    Look into the ``topology`` *element*, described below, for more
    detailed information.

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index c1876ad467e0e50d05d10a622e451593204d2286..4bc6a318f59006411670f9e93771440bb0b24bce 100644 (file)
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -3468,7 +3468,7 @@ paravirtualized driver is specified via the ``disk`` element.
       automatically distributed among the configured iothreads.
 
       Optionally the ``iothread`` element can have multiple ``queue``
-      subelements with mandatory ``id`` atribute specifying that the iothread
+      subelements with mandatory ``id`` attribute specifying that the iothread
       should be used to handle given virt queue. If queue mapping is present
       the ``queues`` attribute of  ``driver`` must be configured and all
       configured virt queues must be included in the mapping. The
@@ -8423,7 +8423,7 @@ Example: usage of external TPM emulator :since:`Since 9.0.0`
 
    This element does not work with the ``passthrough`` backend.
 
-   When specified, it is the user's responsability to prevent files from being
+   When specified, it is the user's responsibility to prevent files from being
    used by multiple VMs or emulators (swtpm will also use advisory locking). If
    not specified, the storage configuration is left to libvirt discretion.
 

diff --git a/docs/glib-adoption.rst b/docs/glib-adoption.rst
index 046cd821f7e72931132bdcd1350c3b9aa32b7f60..6448f25b4f2b6cdf0d02e16029f55c7c08965d2b 100644 (file)
--- a/docs/glib-adoption.rst
+++ b/docs/glib-adoption.rst
@@ -19,7 +19,7 @@ Array operations
 
    https://developer.gnome.org/glib/stable/glib-Arrays.html
 
-   Instead of using plain C arrays, it is preferrable to use one of
+   Instead of using plain C arrays, it is preferable to use one of
    the GLib types, ``GArray``, ``GPtrArray`` or ``GByteArray``.
    These all use a struct to track the array memory and size
    together and efficiently resize.