On a Wednesday in 2020, Erik Skultety wrote:
I overlooked this typo during review of 2c3ffa37.
Please do not follow commit hashes directly by a period. * rephrase the sentence * just drop the period * include a separator like <> or put in into the Fixes: tag Jano
Reported-by: Yalan Zhang <yalzhang@redhat.com> Signed-off-by: Erik Skultety <eskultet@redhat.com> ---
Pushed as trivial.
docs/kbase/launch_security_sev.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/kbase/launch_security_sev.rst b/docs/kbase/launch_security_sev.rst index 19b978481a..cfdc2a6120 100644 --- a/docs/kbase/launch_security_sev.rst +++ b/docs/kbase/launch_security_sev.rst @@ -30,7 +30,7 @@ Enabling SEV on the host ========================
Before VMs can make use of the SEV feature you need to make sure your -AMD CPU does support SEV. You can run ``libvirt-host-validate`` +AMD CPU does support SEV. You can run ``virt-host-validate`` (libvirt >= 6.5.0) to check if your host supports secure guests or you can follow the manual checks below.
-- 2.26.2