From: H. Peter Anvin Date: Sun, 5 Jul 2009 22:44:38 +0000 (-0700) Subject: doc: use the term "extensions" to mean of-specific anything X-Git-Tag: nasm-2.11.05~927 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fc87e65aecc12ce8986be79ac5fb1dd1ed87d825;p=platform%2Fupstream%2Fnasm.git doc: use the term "extensions" to mean of-specific anything We seem to use the term "extensions" to mean anything that is specific to an object format, so continue to do so. Signed-off-by: H. Peter Anvin --- diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index ceb599e..77d58ab 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -4572,7 +4572,7 @@ The \c{ith} file format produces Intel Hex-format files. Just as the relocation or linking. It is usually used with ROM programmers and similar utilities. -All options supported by the \c{bin} file format is also supported by +All extensions supported by the \c{bin} file format is also supported by the \c{ith} file format. \c{ith} provides a default output file-name extension of \c{.ith}. @@ -4585,7 +4585,7 @@ The \c{srec} file format produces Intel Hex-format files. Just as the relocation or linking. It is usually used with ROM programmers and similar utilities. -All options supported by the \c{bin} file format is also supported by +All extensions supported by the \c{bin} file format is also supported by the \c{srec} file format. \c{srec} provides a default output file-name extension of \c{.srec}.