docs: fix since version in driver documentation

Also one stray angle bracket.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Fixes: 068efae5b1a9efeea4a9c3bc0ae80747da5024fb
Fixes: 3e9076e777aff2f4b08330ed17e559fcfb6b3529
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>

diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index f6abb457062e2dc4a86bcb6545ed5796c70a88cb..87542afd274ab9f55e1aa3a00d13cd1e0b3530e4 100644 (file)
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -66,7 +66,7 @@ qemu+ssh://root@example.com/system   (remote access, SSH tunnelled)
     <h3><a id="uriembedded">Embedded driver</a></h3>
 
     <p>
-      Since 6.0.0 the QEMU driver has experimental support for operating
+      Since 6.1.0 the QEMU driver has experimental support for operating
       in an embedded mode. In this scenario, rather than connecting to
       the libvirtd daemon, the QEMU driver runs in the client application
       process directly. To use this the client application must have
@@ -149,7 +149,7 @@ qemu+ssh://root@example.com/system   (remote access, SSH tunnelled)
       when opening a future connection.
     </p>
 
-    <h4><a id="embedAPI">API usage with event loop></a></h4>
+    <h4><a id="embedAPI">API usage with event loop</a></h4>
 
     <p>
       To use the QEMU driver in embedded mode the application must

diff --git a/docs/drvsecret.html.in b/docs/drvsecret.html.in
index 9a05fe1f097b420e0b8e356bfc4a7a90970959d5..1bd7d75215ec6956e465bac3bbd0b9a5c7771714 100644 (file)
--- a/docs/drvsecret.html.in
+++ b/docs/drvsecret.html.in
@@ -35,7 +35,7 @@ secret+ssh://root@example.com/system   (remote access, SSH tunnelled)
     <h3><a id="uriembedded">Embedded driver</a></h3>
 
     <p>
-      Since 6.0.0 the secret driver has experimental support for operating
+      Since 6.1.0 the secret driver has experimental support for operating
       in an embedded mode. In this scenario, rather than connecting to
       the libvirtd daemon, the secret driver runs in the client application
       process directly. To open the driver in embedded mode the app use the