motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-07-27 04:13:53 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: correct typos

Browse source 
Correct typos automatically found with the `typos` tool
<https://crates.io/crates/typos>

Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
(mjt: trivial fixup)
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
This commit is contained in:
Manos Pitsidianakis 2024-02-20 10:52:08 +02:00 • committed by Michael Tokarev
parent aab4631a4a
commit c555b504d0
6 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/devel/ci-jobs.rst.inc
View file

@ -147,7 +147,7 @@ Set this variable to 1 to create the pipelines, but leave all
the jobs to be manually started from the UI the jobs to be manually started from the UI
Set this variable to 2 to create the pipelines and run all Set this variable to 2 to create the pipelines and run all
the jobs immediately, as was historicaly behaviour the jobs immediately, as was the historical behaviour
QEMU_CI_AVOCADO_TESTING QEMU_CI_AVOCADO_TESTING
~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~

2
docs/devel/docs.rst
View file

@ -21,7 +21,7 @@ are processed in two ways:
The syntax of these ``.hx`` files is simple. It is broadly an The syntax of these ``.hx`` files is simple. It is broadly an
alternation of C code put into the C output and rST format text alternation of C code put into the C output and rST format text
put into the documention. A few special directives are recognised; put into the documentation. A few special directives are recognised;
these are all-caps and must be at the beginning of the line. these are all-caps and must be at the beginning of the line.
``HXCOMM`` is the comment marker. The line, including any arbitrary ``HXCOMM`` is the comment marker. The line, including any arbitrary

2
docs/devel/testing.rst
View file

@ -728,7 +728,7 @@ For example to setup the HPPA ports builds of Debian::
EXECUTABLE=(pwd)/qemu-hppa V=1 EXECUTABLE=(pwd)/qemu-hppa V=1
The ``DEB_`` variables are substitutions used by The ``DEB_`` variables are substitutions used by
``debian-boostrap.pre`` which is called to do the initial debootstrap ``debian-bootstrap.pre`` which is called to do the initial debootstrap
of the rootfs before it is copied into the container. The second stage of the rootfs before it is copied into the container. The second stage
is run as part of the build. The final image will be tagged as is run as part of the build. The final image will be tagged as
``qemu/debian-sid-hppa``. ``qemu/debian-sid-hppa``.

2
docs/interop/prl-xml.txt
View file

@ -122,7 +122,7 @@ Each Image element has following child elements:
* Type - image type of the element. It can be: * Type - image type of the element. It can be:
"Plain" for raw files. "Plain" for raw files.
"Compressed" for expanding disks. "Compressed" for expanding disks.
* File - path to image file. Path can be relative to DiskDecriptor.xml or * File - path to image file. Path can be relative to DiskDescriptor.xml or
absolute. absolute.
== Snapshots element == == Snapshots element ==

2
docs/interop/vhost-user.rst
View file

@ -989,7 +989,7 @@ When reconnecting:
#. If ``d.flags`` is not equal to the calculated flags value (means #. If ``d.flags`` is not equal to the calculated flags value (means
back-end has submitted the buffer to guest driver before crash, so back-end has submitted the buffer to guest driver before crash, so
it has to commit the in-progres update), set ``old_free_head``, it has to commit the in-progress update), set ``old_free_head``,
``old_used_idx``, ``old_used_wrap_counter`` to ``free_head``, ``old_used_idx``, ``old_used_wrap_counter`` to ``free_head``,
``used_idx``, ``used_wrap_counter`` ``used_idx``, ``used_wrap_counter``

2
docs/system/devices/canokey.rst
View file

@ -14,7 +14,7 @@ CanoKey [1]_ is an open-source secure key with supports of
All these platform-independent features are in canokey-core [3]_. All these platform-independent features are in canokey-core [3]_.
For different platforms, CanoKey has different implementations, For different platforms, CanoKey has different implementations,
including both hardware implementions and virtual cards: including both hardware implementations and virtual cards:
* CanoKey STM32 [4]_ * CanoKey STM32 [4]_
* CanoKey Pigeon [5]_ * CanoKey Pigeon [5]_