migration: fix typos in qapi-schema from latest migration additions

Recent migration QAPI enhancements had a few spelling mistakes
and also incorrect version number in a few places.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1464776234-9910-2-git-send-email-berrange@redhat.com
Message-Id: <1464776234-9910-2-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
This commit is contained in:
Daniel P. Berrange 2016-06-01 11:17:13 +01:00 committed by Amit Shah
parent 096631bd95
commit bdbba12b6f
1 changed files with 5 additions and 5 deletions

View File

@ -490,7 +490,7 @@
#
# @error-desc: #optional the human readable error description string, when
# @status is 'failed'. Clients should not attempt to parse the
# error strings. (Since 2.6)
# error strings. (Since 2.7)
#
# Since: 0.14.0
##
@ -635,7 +635,7 @@
# migration URI does not already include a hostname. For
# example if using fd: or exec: based migration, the
# hostname must be provided so that the server's x509
# certificate identity canbe validated. (Since 2.7)
# certificate identity can be validated. (Since 2.7)
#
# Since: 2.4
##
@ -676,7 +676,7 @@
# migration URI does not already include a hostname. For
# example if using fd: or exec: based migration, the
# hostname must be provided so that the server's x509
# certificate identity canbe validated. (Since 2.7)
# certificate identity can be validated. (Since 2.7)
#
# Since: 2.4
##
@ -712,14 +712,14 @@
# be for a 'client' endpoint, while for the incoming side the
# credentials must be for a 'server' endpoint. Setting this
# will enable TLS for all migrations. The default is unset,
# resulting in unsecured migration at the QEMU level. (Since 2.6)
# resulting in unsecured migration at the QEMU level. (Since 2.7)
#
# @tls-hostname: hostname of the target host for the migration. This is
# required when using x509 based TLS credentials and the
# migration URI does not already include a hostname. For
# example if using fd: or exec: based migration, the
# hostname must be provided so that the server's x509
# certificate identity canbe validated. (Since 2.6)
# certificate identity can be validated. (Since 2.7)
#
# Since: 2.4
##