docs: Fix typos

Signed-off-by: Tim Wiederhake <twiederh@redhat.com>

diff --git a/docs/drvqemu.rst b/docs/drvqemu.rst
index c9f24322687fa2fe88d3c2a3155c814dc1ed9271..c33706ccea5a8e55b6afd5cce0251b76fc50c683 100644 (file)
--- a/docs/drvqemu.rst
+++ b/docs/drvqemu.rst
@@ -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.
 

diff --git a/docs/testing.rst b/docs/testing.rst
index 21abf42080d385c4bfe363b55f61e6acd08f7092..a597c3ed07697a695ece7b7865f92e7903eeaf16 100644 (file)
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -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

diff --git a/docs/testtck.rst b/docs/testtck.rst
index 6264b40de7f10addfb63dc595eb358a36c0d9e66..100a278acdd091fb8359028cdb804862ba41fe25 100644 (file)
--- a/docs/testtck.rst
+++ b/docs/testtck.rst
@@ -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`_.