mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 02:01:24 +01:00
docs: fix spelling of 'receiver' and 'receiving' in libxc-migration-stream
Signed-off-by: Ravindra Kumar Bundela <ravindrarkb1205@gmail.com> Acked-by: Michal Orzel <michal.orzel@amd.com>
This commit is contained in:
1 parent
275ae20dd7
commit
5fa6f95842
1 file changed
+2
-2
@@ -753,7 +753,7 @@ A v3 stream is compatible with a v2 stream, but mandates the presense of a
|
||||
STATIC_DATA_END record ahead of any memory/register content. This is to ease
|
||||
the introduction of new static configuration records over time.
|
||||
|
||||
A v3-compatible reciever interpreting a v2 stream should infer the position of
|
||||
A v3-compatible receiver interpreting a v2 stream should infer the position of
|
||||
STATIC_DATA_END based on finding the first X86_PV_P2M_FRAMES record (for PV
|
||||
guests), or PAGE_DATA record (for HVM guests) and behave as if STATIC_DATA_END
|
||||
had been sent.
|
||||
@@ -807,7 +807,7 @@ never change size or location.
|
||||
Errata
|
||||
======
|
||||
|
||||
1. For compatibility with older code, the receving side of a stream should
|
||||
1. For compatibility with older code, the receiving side of a stream should
|
||||
tolerate and ignore variable sized records with zero content. Xen releases
|
||||
between 4.6 and 4.8 could end up generating valid HVM_PARAMS or
|
||||
X86_PV_VCPU_{EXTENDED,XSAVE,MSRS} records with zero-length content.
|
||||