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>
This commit is contained in:
Han Han 2023-10-09 09:18:26 +08:00 committed by Ján Tomko
parent 081a24d113
commit c1d8eb579f
3 changed files with 3 additions and 3 deletions

View File

@ -2179,7 +2179,7 @@ are:
Enable QEMU vmcoreinfo device to let the guest kernel save debug details. Enable QEMU vmcoreinfo device to let the guest kernel save debug details.
:since:`Since 4.4.0` (QEMU only) :since:`Since 4.4.0` (QEMU only)
``htm`` ``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 Possible values for the ``state`` attribute are ``on`` and ``off``. If the
attribute is not defined, the hypervisor default will be used. :since:`Since attribute is not defined, the hypervisor default will be used. :since:`Since
4.6.0` (QEMU/KVM only) 4.6.0` (QEMU/KVM only)

View File

@ -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 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 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 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. values.
Guest configuration Guest configuration

View File

@ -5267,7 +5267,7 @@ dom-fd-associate
Associate one or more fds described via *--pass-fds* argument to *domain* as 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 *--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 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 use to avoid keeping them open unnecessarily. Best-effort security label restore