Luckily, the new URL still points to the same location, the only change is in the document name where an escaped space (%20) was replaced by an underscore. Signed-off-by: Erik Skultety <eskultet(a)redhat.com&gt; --- docs/formatdomain.html.in | 4 ++-- docs/formatdomaincaps.html.in | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 7f07bb7f55..2ae5006849 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -8785,8 +8785,8 @@ qemu-kvm -net nic,model=? /dev/null different entity using a different key the encrypted guests data will be incorrectly decrypted, leading to unintelligible data. - For more information see various input parameters and its format see the SEV API spec - <a href="https://support.amd.com/TechDocs/55766_SEV-KM%20API_Specificat... https://support.amd.com/TechDocs/55766_SEV-KM%20API_Specification.pdf </a> + For more information see various input parameters and its format see the + <a href="https://support.amd.com/TechDocs/55766_SEV-KM_API_Specificatio... API spec</a> <span class="since">Since 4.4.0</span> </p> <pre> diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in index cafd9abbdf..ba48daab2d 100644 --- a/docs/formatdomaincaps.html.in +++ b/docs/formatdomaincaps.html.in @@ -481,7 +481,7 @@ <p> For more details on SEV feature see: - <a href="https://support.amd.com/TechDocs/55766_SEV-KM%20API_Specificat... + <a href="https://support.amd.com/TechDocs/55766_SEV-KM_API_Specificatio... SEV API spec</a> and <a href="http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12... SEV White Paper</a> </p> -- 2.20.1