Small corrections and enhancements in man xorriso

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.9, Nov 12, 2017"
+@c man .TH XORRISO 1 "Version 1.4.9, Mar 23, 2018"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -1032,10 +1032,14 @@ Examples:
 @*
 If a track of a CD starts at block 123456 and gets copied to a disk file
 where it begins at block 0, then this copy can be loaded with
--displacement -123456.
+  -displacement -123456
 @*
 If an ISO image was written onto a partition with offset of 640000 blocks of
-512 bytes, then it can be loaded from the base device by -displacement 160000.
+512 bytes, then it can be loaded from the base device by
+  -load sbsector 160000 -displacement 160000
+@*
+(If the partition start address is not divisible by 4, then you will have
+to employ a loop device instead.)
 @*
 In both cases, the ISO sessions should be self contained, i.e. not add-on
 sessions to an ISO image outside their track or partition.
@@ -3715,12 +3719,12 @@ can assume overwriteable media.
 Normally the boot images are data files inside the ISO filesystem. By
 special path "--interval:appended_partition_NNN:all::" it is possible to
 refer to an appended partition. The number NNN gives the partition number 
-as used with the corresponding option -append_partition.
+as used with the corresponding command -append_partition.
 E.g.:
 @*
   -append_partition 2 0xef /tmp/efi.img
 @* 
-  -e --interval:appended_partition_2:all::
+  -boot_image any efi_path=--interval:appended_partition_2:all::
 @*
 There are booting mechanisms which do not use an El Torito record but rather
 start at the first bytes of the image: PC-BIOS MBR or EFI GPT for