[nasm:nasm-2.16.xx] doc: one instance of a __foo__ macro didn't get updated to __?foo?__

[nasm-bot for H. Peter Anvin]

Commit-ID:  94b053a59ce54d3ab42e6cba4397079caa1205dc
Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=94b053a59ce54d3ab42e6cba4397079caa1205dc
Author:     H. Peter Anvin <hpa at zytor.com>
AuthorDate: Fri, 13 Oct 2023 21:28:36 -0700
Committer:  H. Peter Anvin <hpa at zytor.com>
CommitDate: Fri, 13 Oct 2023 21:28:36 -0700

doc: one instance of a __foo__ macro didn't get updated to __?foo?__

__USE_package__ should be __?USE_package?__.

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


---
 doc/nasmdoc.src | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 76f8e4e1..561bc222 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -4750,7 +4750,7 @@ Include Test
 
 When a standard macro package (see \k{macropkg}) is included with the
 \c{%use} directive (see \k{use}), a single-line macro of the form
-\c{__USE_}\e{package}\c{__} is automatically defined.  This allows
+\c{__?USE_}\e{package}\c{?__} is automatically defined.  This allows
 testing if a particular package is invoked or not.
 
 For example, if the \c{altreg} package is included (see