Fixed an incorrect statement (thanks, Felix!).
authorRyan C. Gordon <icculus@icculus.org>
Sun, 28 Dec 2014 01:51:09 -0500
changeset 109 5b6da1d6be5a
parent 108 0a4566740a98
child 110 28288e5c8745
Fixed an incorrect statement (thanks, Felix!).
docs/fatelf-specification.txt
--- a/docs/fatelf-specification.txt	Thu Nov 22 12:39:53 2012 -0500
+++ b/docs/fatelf-specification.txt	Sun Dec 28 01:51:09 2014 -0500
@@ -56,9 +56,9 @@
 Each record starts with an unsigned, 16-bit value that represents the machine
 architecture for this record. This field maps to e_machine in the ELF header.
 Next come four unsigned, 8-bit values. These represent, in order, the OSABI,
-OSABI version, byte order and word size of the referenced ELF binary. These
+OSABI version, word size and byte order of the referenced ELF binary. These
 fields map to e_ident[EI_OSABI], e_ident[EI_ABIVERSION], e_ident[EI_CLASS] and 
-e_ident[EI_DATA in the ELF header. Please note that the FatELF structures
+e_ident[EI_DATA] in the ELF header. Please note that the FatELF structures
 themselves are always little endian and aligned to Elf64 standards, no matter
 what these fields contain.