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>
This commit is contained in:
Ján Tomko 2020-01-27 16:38:19 +01:00
parent b0b94a8d32
commit fe8921c27b
2 changed files with 3 additions and 3 deletions

View File

@ -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

View File

@ -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