Virtual Hardware Platform: fix editing-errors.

Signed-off-by: Thomas Sanders <[email protected]>

Author: thomassa

xen-api/futures/virt-hw-platform-vn/virt-hw-platform-vn.md

@@ -19,7 +19,7 @@ We want a clean way to ensure that xapi only tries to run a guest VM on a host t
 * When a host boots it populates its own entry from a hardcoded value, currently `[0; 1]` i.e. a list containing the two integer elements `0` and `1`. (Alternatively this could come from a config file.)
   * If this new version-handling functionality is introduced in a hotfix, at some point the pool master will have the new functionality while at least one slave does not. An old slave-host that does not yet have software to handle this feature will not set its DB entry, which will therefore remain as `[0]` (maintained in the DB by the master).
 * The existing test for whether a VM can run on (or migrate to) a host must include a check that the VM's virtual hardware platform version is in the host's list of supported versions.
-* When a VM is made to start using a feature is available only in a certain virtual hardware platform version, xapi must set it the VM's virt_hw_vn to the minimum of that version-number and its current value.
+* When a VM is made to start using a feature that is available only in a certain virtual hardware platform version, xapi must set the VM's hardware_platform_version to the maximum of that version-number and its current value (i.e. raise if needed).
 
 For the version we could consider some type other than integer, but a strict ordering is needed.