Corrected interpretation of RFC 4122 UUID strings for GPT. Thanks Andrei Borzenkov.

xorriso/xorriso.texi

@@ -50,7 +50,7 @@
 @c man .\" First parameter, NAME, should be all caps
 @c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
 @c man .\" other parameters are allowed: see man(7), man(1)
-@c man .TH XORRISO 1 "Version 1.4.5, Aug 12, 2016"
+@c man .TH XORRISO 1 "Version 1.4.5, Aug 14, 2016"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -3901,9 +3901,11 @@ Value "random" is default. Value "volume_date_uuid" produces a low quality
 GUID from the value set by -volume_date "uuid".
 @*
 A string of 32 hex digits, or a RFC 4122 compliant GUID string may be used to
-set the disk GUID directly.
+set the disk GUID directly. UEFI prescribes the first three components of
+a RFC 4122 GUID string to be byte-swapped in the binary representation:
 @*
 E.g. gpt_disk_guid=2303cd2a-73c7-424a-a298-25632da7f446
+equals gpt_disk_guid=2acd0323c7734a42a29825632da7f446
 @*
 The partition GUIDs get generated by minimally varying the disk GUID.
 @*
@@ -4797,7 +4799,7 @@ file with the path given after the colon. Compute the GPT compliant CRC number
 and print it to the result channel. The number is shown like "0x690fd979".
 The special disk_path "-" causes reading from standard input.
 @*
-With mode @strong{make_guid} print a pseudo-random GUID in RFC 4122 format
+With mode @strong{make_guid} print a pseudo-random GUID in RFC 4122 text format
 to result channel.
 @end table
 @c man .TP