docs: Fix typos

Signed-off-by: Han Han <hhan@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Ján Tomko <jtomko@redhat.com>

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index af62fcd82005cd4bbde1c65100efff0ed638c9b2..03735e4593aa5672be0a744e2243da5710dcc59c 100644 (file)
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -2179,7 +2179,7 @@ are:
    Enable QEMU vmcoreinfo device to let the guest kernel save debug details.
    :since:`Since 4.4.0` (QEMU only)
 ``htm``
-   Configure HTM (Hardware Transational Memory) availability for pSeries guests.
+   Configure HTM (Hardware Transactional Memory) availability for pSeries guests.
    Possible values for the ``state`` attribute are ``on`` and ``off``. If the
    attribute is not defined, the hypervisor default will be used. :since:`Since
    4.6.0` (QEMU/KVM only)

diff --git a/docs/kbase/kvm-realtime.rst b/docs/kbase/kvm-realtime.rst
index 87ab314bcb84d2e4a3da12530f50e66fe8bbf317..c829eac120c00cb5826ec6e347d8c6e3c2bc939a 100644 (file)
--- a/docs/kbase/kvm-realtime.rst
+++ b/docs/kbase/kvm-realtime.rst
@@ -103,7 +103,7 @@ Be aware that CPU ID numbers are not always allocated sequentially as shown
 here. It is not unusual to see IDs interleaved between sockets on the two NUMA
 nodes, such that ``0-3,8-11`` are on the first node and ``4-7,12-15`` are on
 the second node.  Carefully check the ``virsh capabilities`` output to determine
-the CPU ID numbers when configiring both ``isolcpus`` and the guest ``cpuset``
+the CPU ID numbers when configuring both ``isolcpus`` and the guest ``cpuset``
 values.
 
 Guest configuration

diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst
index 4ae3bb4d939ad5250720f6eb33ccaf6c7f03ae9a..c42597491222b5690f87e7c3fbc4661239be2775 100644 (file)
--- a/docs/manpages/virsh.rst
+++ b/docs/manpages/virsh.rst
@@ -5267,7 +5267,7 @@ dom-fd-associate
 
 Associate one or more fds described via *--pass-fds* argument to *domain* as
 *--name*. The lifetime of the passed fd group is the same as the connection, thus
-exitting virsh un-registers them afterwards.
+exiting virsh un-registers them afterwards.
 
 By default security labels are applied if needed but they are not restored after
 use to avoid keeping them open unnecessarily. Best-effort security label restore