Avoided the use of the term 'eventual' for the meaning 'if applicable'.

libisoburn/trunk/doc/faq.wiki

@@ -128,7 +128,7 @@ address 16*2048 and to let start partition 1 at this address. The second
 superblock leads to a second directory tree which takes into account the
 address difference between partition 1 and the base device. So the image
 gets mountable via both devices and reserves 32 kB for boot manager software
-where it eventually can manipulate and augment the MBR.
+where it may manipulate and augment the MBR.
 (See [http://libburnia-project.org/wiki/PartitionOffset Partition Offset Wiki]
 for examples.)
 

libisoburn/trunk/doc/partition_offset.wiki

@@ -10,7 +10,7 @@ via the partition device file. E.g. on GNU/Linux: /dev/sdb and /dev/sdb1.
 This is achieved by two distinct sets of meta-data which refer to the same
 file content.
 
-The dual-mount feature supports Rock Ridge and eventually Joliet too.
+The dual-mount feature supports Rock Ridge and Joliet too.
 It is capable of multi-session.
 
 Currently only offset 32 kB seems to make sense. Smaller offsets are prohibited
@@ -176,8 +176,8 @@ E.g. by 402 kB to 2 MB.
 Open questions:
 
 - Shall the partition of an isohybrid image be marked bootable ?
-Currently xorriso keeps the 0x80 mark of an eventually imported MBR
-resp. the 0x80 mark which xorriso eventually sets by its own MBR
+Currently xorriso keeps the 0x80 mark of an imported MBR
+resp. the 0x80 mark which xorriso sets by its own MBR
 preparations.
   - If not to be marked bootable:
     What equipment would the partition need to justify having the mark ?