Mentioned that partition_entry=gpt_basdat and -isohybrid-gpt-basdat create invalid GPT but also a valid MBR partition table

xorriso/xorrisofs.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 XORRISOFS 1 "Version 1.5.3, Nov 23, 2019"
+@c man .TH XORRISOFS 1 "Version 1.5.3, Sep 11, 2020"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -1614,13 +1614,14 @@ For the meaning of special disk_path "." see option -G.
 @item -isohybrid-gpt-basdat
 @kindex -isohybrid-gpt-basdat   Mark boot image in GPT
 @cindex Bootability, mark boot image in GPT, -isohybrid-gpt-basdat
-Mark the current El Torito boot image (see options -b and -e) in GPT as
-partition of type Basic Data. This works only with -isohybrid-mbr and
-has the same impact on the system area as -efi-boot-part. It cannot be
-combined with -efi-boot-part or -hfsplus.
+Mark the current El Torito boot image (see options -b and -e) in an actually
+invalid GPT as partition of type Basic Data. This works only with
+-isohybrid-mbr and has the same impact on the system area as -efi-boot-part.
+It cannot be combined with -efi-boot-part or -hfsplus.
 @*
 The first three boot images which are marked by GPT will also show up
-as partition entries of type 0xef in MBR. 
+as partition entries in MBR. The MBR partition of type 0xEF is what actually
+is used by EFI firmware for booting from USB stick.
 The MBR partition for PC-BIOS gets type 0x00 rather than 0x17 in this case.
 Often the further MBR entries are the ones which actually get used by EFI.
 @c man .TP