External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-06 09:55:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix typos

Browse Source 
Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
This commit is contained in:
Tim Wiederhake 2022-07-18 11:10:55 +02:00
parent 62ca300530
commit 57d263d6a3
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/drvqemu.rst
View File

@ -449,7 +449,7 @@ for libvirt to check compatibility prior to migration.
If using ``host-model`` the target host hardware and software deployment
must expose a superset of the features of the source host CPU. If using
``host-passthrough`` the target host CPU and software deployment must
always expose a superset of the fetures, however, it is further strongly
always expose a superset of the features, however, it is further strongly
recommended that the source and destination hosts be identical in every
way.

2
docs/testing.rst
View File

@ -30,7 +30,7 @@ valuable marker when accepting upstream contributions. Therefore, it is
recommended to run libvirt builds against your changes in various containers to
either locally or by using GitLab's shared CI runners to make sure everything
runs cleanly before submitting your patches. The images themselves come from
libvirt's GitLab container registry, but this can be overriden if needed, see
libvirt's GitLab container registry, but this can be overridden if needed, see
below.
Registry

2
docs/testtck.rst
View File

@ -33,7 +33,7 @@ happens.
Using TCK
---------
TCK can be used independently of the enviroment, i.e. both on your local host
TCK can be used independently of the environment, i.e. both on your local host
or in a VM. We strongly recommend using a VM for the tests as TCK might affect
your current host setup, see `Running TCK`_.