Also one stray angle bracket.

Signed-off-by: Ján Tomko <jto...@redhat.com>
Fixes: 068efae5b1a9efeea4a9c3bc0ae80747da5024fb
Fixes: 3e9076e777aff2f4b08330ed17e559fcfb6b3529
---
 docs/drvqemu.html.in   | 4 ++--
 docs/drvsecret.html.in | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index f6abb45706..87542afd27 100644
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -66,7 +66,7 @@ qemu+ssh://r...@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://r...@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 9a05fe1f09..1bd7d75215 100644
--- a/docs/drvsecret.html.in
+++ b/docs/drvsecret.html.in
@@ -35,7 +35,7 @@ secret+ssh://r...@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
-- 
2.21.0

Reply via email to