Signed-off-by: Tim Wiederhake <twiederh(a)redhat.com&gt; --- docs/drvqemu.rst | 2 +- docs/testing.rst | 2 +- docs/testtck.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/drvqemu.rst b/docs/drvqemu.rst index c9f2432268..c33706ccea 100644 --- 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 21abf42080..a597c3ed07 100644 --- 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 6264b40de7..100a278acd 100644 --- 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`_. -- 2.36.1