[nasm:nasm-2.16.xx] doc: slightly more wordsmithing

[nasm-bot for H. Peter Anvin]

Commit-ID:  6198a2396c1af7791e10d41d77ba4f2016c0b1b1
Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=6198a2396c1af7791e10d41d77ba4f2016c0b1b1
Author:     H. Peter Anvin <hpa at zytor.com>
AuthorDate: Fri, 13 Oct 2023 17:09:25 -0700
Committer:  H. Peter Anvin <hpa at zytor.com>
CommitDate: Fri, 13 Oct 2023 17:09:25 -0700

doc: slightly more wordsmithing

Tidy up the new text for the bin format a little more.

Signed-off-by: H. Peter Anvin <hpa at zytor.com>


---
 doc/nasmdoc.src | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 6da2b7b7..b16d1964 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -5772,10 +5772,10 @@ into a binary file called \c{binprog}.
 
 It is extremely important to understand that the binary output format
 is simply nothing other than \e{a linker built into the NASM
-executable.} As such, NASM behaves just as it does when given any
-other output format; notably the list file reflects the code output
-\e{before} relocation, and addresses in the list file are addresses
-relative to the start of the output section.
+executable.} As such, NASM behaves just as it does when producing any
+other output format: notably the list file reflects the code output
+\e{before} relocation, and the addresses in the list file are
+addresses relative to the start of the current output section.
 
 
 \S{org} \i\c{ORG}: Binary File \i{Program Origin}