From 800a3c4bc03543c68073c03409ab37aa844c895e Mon Sep 17 00:00:00 2001 From: "Ryan C. Gordon" Date: Sun, 28 Dec 2014 01:51:09 -0500 Subject: [PATCH] Fixed an incorrect statement (thanks, Felix!). --- docs/fatelf-specification.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/fatelf-specification.txt b/docs/fatelf-specification.txt index 7789490..1fd50aa 100644 --- a/docs/fatelf-specification.txt +++ b/docs/fatelf-specification.txt @@ -56,9 +56,9 @@ The record format is as follows. 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.