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

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>

diff --git a/docs/api.rst b/docs/api.rst
index 08e5a0eed9ae1d611c5fe642f4f8901e95e25b5e..cdba642967683cd5c4d999a10a92b03d7be6f8ba 100644 (file)
--- 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 1ff45da6f0111475ef5444f44540205eced3945f..933469b2a2c147a7cbbf3b525a2a3593cc3f6e55 100644 (file)
--- 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.