summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2009-07-05 15:45:45 -0700
committerH. Peter Anvin <hpa@zytor.com>2009-07-05 15:45:45 -0700
commitd78fc550b816eb3c57a81df6132d1e56bd651e24 (patch)
treef8502b7f0b11a26e09fb42415db25c4a5f805490
parentfc87e65aecc12ce8986be79ac5fb1dd1ed87d825 (diff)
downloadnasm-d78fc550b816eb3c57a81df6132d1e56bd651e24.tar.gz
doc: srec produces S-records, not Intel hex...
Copy and paste accident... Signed-off-by: H. Peter Anvin <hpa@zytor.com>
-rw-r--r--doc/nasmdoc.src2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 77d58abc..4a3e1653 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -4580,7 +4580,7 @@ the \c{ith} file format.
\H{srecfmt} \i\c{srec}: \i{Motorola S-Record} Output
-The \c{srec} file format produces Intel Hex-format files. Just as the
+The \c{srec} file format produces Motorola S-record files. Just as the
\c{bin} format, this is a flat memory image format with no support for
relocation or linking. It is usually used with ROM programmers and
similar utilities.