External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 05:35:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Remove extra leading slash in 'api' and 'formatdomaincaps' pages

Browse Source 
While the links work they'd trip up the link validator script which will
be added later.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Peter Krempa 2022-05-31 15:39:07 +02:00
parent 610407dad3
commit d19c8e7a57
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api.rst
View File

@ -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. page for a full descriptions of the values allowed.
OnDevice the application obtains a 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 connection to the hypervisor it can then use it to manage the
hypervisor's available domains and related virtualization resources, hypervisor's available domains and related virtualization resources,
such as storage and networking. All those are exposed as first class such as storage and networking. All those are exposed as first class

2
docs/formatdomaincaps.rst
View File

@ -18,7 +18,7 @@ more recent to support VFIO, while legacy KVM is achievable just fine with older
qemus. qemus.
The main difference between 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 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 capabilities (e.g. NUMA topology, security models in effect, etc.) while the
latter one specializes on the hypervisor capabilities. latter one specializes on the hypervisor capabilities.