While the links work they'd trip up the link validator script which will be added later. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> --- docs/api.rst | 2 +- docs/formatdomaincaps.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api.rst b/docs/api.rst index 08e5a0eed9..cdba642967 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -27,7 +27,7 @@ wise thing to do in most cases. See the `connection URI <uri.html>`__ page for a full descriptions of the values allowed. OnDevice the application obtains a -`virConnectPtr </html/libvirt-libvirt-host.html#virConnectPtr>`__ +`virConnectPtr <html/libvirt-libvirt-host.html#virConnectPtr>`__ connection to the hypervisor it can then use it to manage the hypervisor's available domains and related virtualization resources, such as storage and networking. All those are exposed as first class diff --git a/docs/formatdomaincaps.rst b/docs/formatdomaincaps.rst index 1ff45da6f0..933469b2a2 100644 --- a/docs/formatdomaincaps.rst +++ b/docs/formatdomaincaps.rst @@ -18,7 +18,7 @@ more recent to support VFIO, while legacy KVM is achievable just fine with older qemus. The main difference between -`virConnectGetCapabilities </html/libvirt-libvirt-host.html#virConnectGetCapabilities>`__ +`virConnectGetCapabilities <html/libvirt-libvirt-host.html#virConnectGetCapabilities>`__ and the emulator capabilities API is, the former one aims more on the host capabilities (e.g. NUMA topology, security models in effect, etc.) while the latter one specializes on the hypervisor capabilities. -- 2.35.3
