Mentioned -append_partition in manual about --mbr-force-bootable

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.7, Feb 26, 2017"
+@c man .TH XORRISO 1 "Version 1.4.7, Jun 29, 2017"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -4117,9 +4117,13 @@ indicate production of a bootable MBR.
 These options normally cause the flag to be set if there is an
 MBR partition of type other than 0xee or 0xef.
 If no such partition exists, then no bootflag is set, unless
-mbr_force_bootable= forces creation of a dummy partition
+mbr_force_bootable="on" forces creation of a dummy partition
 of type 0x00 which covers only the first block of the ISO image.
 @*
+If no bootable MBR is indicated and a partition gets created by
+-append_partition, then mbr_force_bootable="on" causes a bootflag like it
+would do with a bootable MBR.
+@*
 @cindex MIPS boot file, activation
 @strong{mips_path=}iso_rr_path declares a data file in the image to be a
 MIPS Big Endian boot file and causes production of a MIPS Big Endian Volume
@@ -7064,7 +7068,7 @@ The default setting of -check_media abort_file= is:
 @chapter Environ
 The following environment variables influence the program behavior:
 @*
-HOME is used to find xorriso and mkisofs startup files.
+HOME is used to find startup files of xorriso and mkisofs.
 @*
 SOURCE_DATE_EPOCH belongs to the specs of reproducible-builds.org.
 It is supposed to be either undefined or to contain a decimal number