--- a/doc/interpreter/basics.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/basics.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -86,7 +86,7 @@
 @cindex @sortas{options, Octave command --doc-cache-file} @ @ @code{--doc-cache-file @var{filename}}
 Specify the name of the documentation cache file to use.  The value of
 @var{filename} specified on the command line will override any value of
-@w{@env{OCTAVE_DOC_CACHE_FILE}} found in the environment, but not any commands
+@w{@env{OCTAVE_DOC_CACHE_FILE}}@ found in the environment, but not any commands
 in the system or user startup files that use the @code{doc_cache_file}
 function.
 
@@ -106,9 +106,9 @@
 @cindex @sortas{options, Octave command --exec-path} @ @ @code{--exec-path @var{path}}
 Specify the path to search for programs to run.  The value of @var{path}
 specified on the command line will override any value of
-@w{@env{OCTAVE_EXEC_PATH}} found in the environment, but not any commands
+@w{@env{OCTAVE_EXEC_PATH}}@ found in the environment, but not any commands
 in the system or user startup files that call the
-@w{@env{EXEC_PATH}} function.
+@w{@env{EXEC_PATH}}@ function.
 
 @item  --gui
 @itemx -g
@@ -125,15 +125,15 @@
 @cindex @sortas{options, Octave command --image-path} @ @ @code{--image-path @var{path}}
 Add path to the head of the search path for images.  The value of
 @var{path} specified on the command line will override any value of
-@w{@env{OCTAVE_IMAGE_PATH}} found in the environment, but not any commands
-in the system or user startup files that call the @w{@env{IMAGE_PATH}}
+@w{@env{OCTAVE_IMAGE_PATH}}@ found in the environment, but not any commands
+in the system or user startup files that call the @w{@env{IMAGE_PATH}}@
 function.
 
 @item --info-file @var{filename}
 @cindex @sortas{options, Octave command --info-file} @ @ @code{--info-file @var{filename}}
 Specify the name of the info file to use.  The value of @var{filename}
 specified on the command line will override any value of
-@w{@env{OCTAVE_INFO_FILE}} found in the environment, but not any commands
+@w{@env{OCTAVE_INFO_FILE}}@ found in the environment, but not any commands
 in the system or user startup files that use the @code{info_file}
 function.
 
@@ -141,7 +141,7 @@
 @cindex @sortas{options, Octave command --info-program} @ @ @code{--info-program @var{program}}
 Specify the name of the info program to use.  The value of @var{program}
 specified on the command line will override any value of
-@w{@env{OCTAVE_INFO_PROGRAM}} found in the environment, but not any
+@w{@env{OCTAVE_INFO_PROGRAM}}@ found in the environment, but not any
 commands in the system or user startup files that use the
 @code{info_program} function.
 
@@ -218,7 +218,7 @@
 @cindex @sortas{options, Octave command -p} @ @ @code{-p @var{path}}
 Add path to the head of the search path for function files.  The
 value of @var{path} specified on the command line will override any value
-of @w{@env{OCTAVE_PATH}} found in the environment, but not any commands in the
+of @w{@env{OCTAVE_PATH}}@ found in the environment, but not any commands in the
 system or user startup files that set the internal load path through one
 of the path functions.
 

--- a/doc/interpreter/external.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/external.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -172,14 +172,14 @@
 @item The string to use for the help text of the function.
 @end enumerate
 
-The return type of functions defined with @w{@code{DEFUN_DLD}} is always
+The return type of functions defined with @w{@code{DEFUN_DLD}}@ is always
 @code{octave_value_list}.
 
 There are a couple of important considerations in the choice of function name.
 First, it must be a valid Octave function name and so must be a sequence of
 letters, digits, and underscores not starting with a digit.  Second, as Octave
 uses the function name to define the filename it attempts to find the function
-in, the function name in the @w{@code{DEFUN_DLD}} macro must match the filename
+in, the function name in the @w{@code{DEFUN_DLD}}@ macro must match the filename
 of the oct-file.  Therefore, the above function should be in a file
 @file{helloworld.cc}, and would be compiled to an oct-file using the command
 
@@ -189,9 +189,9 @@
 
 This will create a file called @file{helloworld.oct} that is the compiled
 version of the function.  It should be noted that it is perfectly acceptable to
-have more than one @w{@code{DEFUN_DLD}} function in a source file.  However,
+have more than one @w{@code{DEFUN_DLD}}@ function in a source file.  However,
 there must either be a symbolic link to the oct-file for each of the functions
-defined in the source code with the @w{@code{DEFUN_DLD}} macro or the
+defined in the source code with the @w{@code{DEFUN_DLD}}@ macro or the
 @code{autoload} (@ref{Function Files}) function should be used.
 
 The rest of the function shows how to find the number of input arguments, how
@@ -348,7 +348,7 @@
 @code{solve}, etc.
 
 The typical way to extract a matrix or array from the input arguments of
-@w{@code{DEFUN_DLD}} function is as follows
+@w{@code{DEFUN_DLD}}@ function is as follows
 
 @example
 @group
@@ -874,10 +874,10 @@
 
 Global variables allow variables in the global scope to be accessed.  Global
 variables can be accessed within oct-files by using the support functions
-@w{@code{global_varval}} and @w{@code{global_assign}} from the current
+@w{@code{global_varval}}@ and @w{@code{global_assign}}@ from the current
 interpreter's symbol table.  Both functions take as first argument a string
 representing the variable name to be obtained or assigned.  The second
-argument of @w{@code{global_assign}} is the value to be assigned.  An
+argument of @w{@code{global_assign}}@ is the value to be assigned.  An
 example of the use of these two functions is
 
 @example
@@ -1120,7 +1120,7 @@
 Allocating memory within an oct-file might seem easy, as the C++ new/delete
 operators can be used.  However, in that case great care must be taken to avoid
 memory leaks.  The preferred manner in which to allocate memory for use locally
-is to use the @w{@code{OCTAVE_LOCAL_BUFFER}} macro.  An example of its use is
+is to use the @w{@code{OCTAVE_LOCAL_BUFFER}}@ macro.  An example of its use is
 
 @example
 OCTAVE_LOCAL_BUFFER (double, tmp, len)
@@ -1194,19 +1194,19 @@
 @end group
 @end example
 
-The presence of the @w{@code{OCTAVE_QUIT}} macro in the inner loop allows
+The presence of the @w{@code{OCTAVE_QUIT}}@ macro in the inner loop allows
 Octave to detect and acknowledge a @key{Control-C} key sequence.  Without this
 macro, the user must either wait for the oct-file function to return before the
 interrupt is processed, or the user must press @key{Control-C} three times
 which will force Octave to exit completely.
 
-The @w{@code{OCTAVE_QUIT}} macro does impose a very small performance penalty;
+The @w{@code{OCTAVE_QUIT}}@ macro does impose a very small performance penalty;
 For loops that are known to be small it may not make sense to include
 @w{@code{OCTAVE_QUIT}}.
 
 When creating an oct-file that uses an external library, the function might
 spend a significant portion of its time in the external library.  It is not
-generally possible to use the @w{@code{OCTAVE_QUIT}} macro in this case.  The
+generally possible to use the @w{@code{OCTAVE_QUIT}}@ macro in this case.  The
 alternative code in this case is
 
 @example
@@ -1221,7 +1221,7 @@
 internally, then this memory might be lost during an interrupt, without being
 deallocated.  Therefore, ideally Octave itself should allocate any memory that
 is needed by the foreign code, with either the @nospell{@code{rwdata}}
-method or the @w{@code{OCTAVE_LOCAL_BUFFER}} macro.
+method or the @w{@code{OCTAVE_LOCAL_BUFFER}}@ macro.
 
 The Octave @code{unwind_protect} mechanism (@ref{The unwind_protect Statement})
 can also be used in oct-files.  In conjunction with the exception handling of
@@ -1251,7 +1251,7 @@
 @subsection Documentation and Testing of Oct-Files
 
 The documentation for an oct-file is contained in the fourth string parameter
-of the @w{@code{DEFUN_DLD}} macro.  This string can be formatted in the same
+of the @w{@code{DEFUN_DLD}}@ macro.  This string can be formatted in the same
 manner as the help strings for user functions, however there are some issues
 that are particular to the formatting of help strings within oct-files.
 
@@ -2163,7 +2163,7 @@
 @file{HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\JRE} or
 @file{HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment} on
 Windows.  The default path to the JVM can be overridden by setting the
-environment variable @w{@env{JAVA_HOME}} to the path where the JVM is
+environment variable @w{@env{JAVA_HOME}}@ to the path where the JVM is
 installed.  On Windows that might be, for example,
 @file{C:\Program Files\Java\jre-10.0.2}.  Make sure that you select a directory
 that contains the JVM with a @nospell{bit-ness} that matches Octave's.

--- a/doc/interpreter/install.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/install.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -885,7 +885,7 @@
 @itemize @bullet
 @item
 On some @nospell{SCO} systems, @code{info} fails to compile if
-@w{@code{HAVE_TERMIOS_H}} is defined in @file{config.h}.  Simply
+@w{@code{HAVE_TERMIOS_H}}@ is defined in @file{config.h}.  Simply
 removing the definition from @file{info/config.h} should allow it to
 compile.
 
@@ -910,7 +910,7 @@
 library, resulting in floating point errors and/or segmentation faults
 in the linear algebra routines called by Octave.  If you encounter such
 problems, then you should modify the configure script so that
-@w{@code{SPECIAL_MATH_LIB}} is not set to @code{-ldxml}.
+@w{@code{SPECIAL_MATH_LIB}}@ is not set to @code{-ldxml}.
 
 @item
 On FreeBSD systems Octave may hang while initializing some internal
@@ -956,10 +956,10 @@
 while compiling @file{sighandlers.cc}, you may need to edit some files
 in the @code{gcc} include subdirectory to add proper prototypes for
 functions there.  For example, @nospell{Ultrix} 4.2 needs proper declarations
-for the @code{signal} function and the @w{@code{SIG_IGN}} macro in the file
+for the @code{signal} function and the @w{@code{SIG_IGN}}@ macro in the file
 @file{signal.h}.
 
-On some systems the @w{@code{SIG_IGN}} macro is defined to be something
+On some systems the @w{@code{SIG_IGN}}@ macro is defined to be something
 like this:
 
 @example
@@ -975,8 +975,8 @@
 
 @noindent
 to match the prototype declaration for the @code{signal} function.  This
-change should also be made for the @w{@code{SIG_DFL}} and
-@w{@code{SIG_ERR}} symbols.  It may be necessary to change the
+change should also be made for the @w{@code{SIG_DFL}}@ and
+@w{@code{SIG_ERR}}@ symbols.  It may be necessary to change the
 definitions in @file{sys/signal.h} as well.
 
 The @code{gcc} @code{fixincludes} and @code{fixproto} scripts should
@@ -1040,7 +1040,7 @@
 @item
 Some people have reported that calls to system() and the pager do not
 work on @nospell{SunOS} systems.  This is apparently due to having
-@w{@code{G_HAVE_SYS_WAIT}} defined to be 0 instead of 1 when compiling
+@w{@code{G_HAVE_SYS_WAIT}}@ defined to be 0 instead of 1 when compiling
 @code{libg++}.
 
 @item

--- a/doc/interpreter/package.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/package.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -227,7 +227,7 @@
 @anchor{XREFPKG_ADD}
 @item package/PKG_ADD
 An optional file that includes commands that are run when the package
-is added to the users path.  Note that @w{@code{PKG_ADD}} directives in the
+is added to the users path.  Note that @w{@code{PKG_ADD}}@ directives in the
 source code of the package will also be added to this file by the
 Octave package manager.  Note that symbolic links are to be avoided in
 packages, as symbolic links do not exist on some file systems, and so
@@ -245,17 +245,17 @@
 @end example
 
 @noindent
-@xref{PKG_ADD and PKG_DEL Directives}, for details on @w{@code{PKG_ADD}}
+@xref{PKG_ADD and PKG_DEL Directives}, for details on @w{@code{PKG_ADD}}@
 directives.
 
 @cindex PKG_DEL
 @anchor{XREFPKG_DEL}
 @item package/PKG_DEL
 An optional file that includes commands that are run when the package
-is removed from the users path.  Note that @w{@code{PKG_DEL}} directives in
+is removed from the users path.  Note that @w{@code{PKG_DEL}}@ directives in
 the source code of the package will also be added to this file by the
 Octave package manager.
-@xref{PKG_ADD and PKG_DEL Directives}, for details on @w{@code{PKG_DEL}}
+@xref{PKG_ADD and PKG_DEL Directives}, for details on @w{@code{PKG_DEL}}@
 directives.
 
 @item package/pre_install.m
@@ -308,7 +308,7 @@
 
 @item package/bin
 An optional directory containing files that will be added to the
-Octave @w{@env{EXEC_PATH}} when the package is loaded.  This might contain
+Octave @w{@env{EXEC_PATH}}@ when the package is loaded.  This might contain
 external scripts, etc., called by functions within the package.
 @end table
 
@@ -561,15 +561,15 @@
 @node PKG_ADD and PKG_DEL Directives
 @subsection PKG_ADD and PKG_DEL Directives
 
-If the package contains files called @w{@code{PKG_ADD}} or @w{@code{PKG_DEL}}
+If the package contains files called @w{@code{PKG_ADD}}@ or @w{@code{PKG_DEL}}@
 the commands in these files will be executed when the package is
 added or removed from the users path.  In some situations such files
 are a bit cumbersome to maintain, so the package manager supports
 automatic creation of such files.  If a source file in the package
-contains a @w{@code{PKG_ADD}} or @w{@code{PKG_DEL}} directive they will be
-added to either the @w{@code{PKG_ADD}} or @w{@code{PKG_DEL}} files.
+contains a @w{@code{PKG_ADD}}@ or @w{@code{PKG_DEL}}@ directive they will be
+added to either the @w{@code{PKG_ADD}}@ or @w{@code{PKG_DEL}}@ files.
 
-In @code{m}-files a @w{@code{PKG_ADD}} directive looks like this
+In @code{m}-files a @w{@code{PKG_ADD}}@ directive looks like this
 
 @example
 ## PKG_ADD: some_octave_command
@@ -577,7 +577,7 @@
 
 @noindent
 Such lines should be added before the @code{function} keyword.
-In C++ files a @w{@code{PKG_ADD}} directive looks like this
+In C++ files a @w{@code{PKG_ADD}}@ directive looks like this
 
 @example
 // PKG_ADD: some_octave_command
@@ -585,10 +585,10 @@
 
 @noindent
 In both cases @code{some_octave_command} should be replaced by the
-command that should be placed in the @w{@code{PKG_ADD}} file.
-@w{@code{PKG_DEL}} directives work in the same way, except the
-@w{@code{PKG_ADD}} keyword is replaced with @w{@code{PKG_DEL}} and the commands
-get added to the @w{@code{PKG_DEL}} file.
+command that should be placed in the @w{@code{PKG_ADD}}@ file.
+@w{@code{PKG_DEL}}@ directives work in the same way, except the
+@w{@code{PKG_ADD}}@ keyword is replaced with @w{@code{PKG_DEL}}@ and the
+commands get added to the @w{@code{PKG_DEL}}@ file.
 
 @node Missing Components
 @subsection Missing Components

--- a/doc/interpreter/plot.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/plot.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -307,13 +307,12 @@
 The @code{xlim}, @code{ylim}, and @code{zlim} functions may be used to
 get or set individual axis limits.  Each has the same form.
 
-@c Add cross-references and function index entries for other limit functions.
-@anchor{XREFylim}
-@anchor{XREFzlim}
-@findex ylim
-@findex zlim
 @DOCSTRING(xlim)
 
+@DOCSTRING(ylim)
+
+@DOCSTRING(zlim)
+
 The @code{xticks}, @code{yticks}, @code{zticks}, @code{rticks}, and
 @code{thetaticks} functions may be used to get or set the tick mark locations
 and modes on the respective axis.  Each has the same form, although mode
@@ -321,16 +320,16 @@
 
 @c FIXME: Update this section if polarplot and polar axes changes change the
 @c        associated axis properties.
-@anchor{XREFyticks}
-@anchor{XREFzticks}
-@anchor{XREFrticks}
-@anchor{XREFthetaticks}
-@findex yticks
-@findex zticks
-@findex rticks
-@findex thetaticks
 @DOCSTRING(xticks)
 
+@DOCSTRING(yticks)
+
+@DOCSTRING(zticks)
+
+@DOCSTRING(rticks)
+
+@DOCSTRING(thetaticks)
+
 The @code{xticklabels}, @code{yticklabels}, and @code{zticklabels} functions
 may be used to get or set the label assigned to each tick location and the
 labeling mode on the respective axis.  Each has the same form.
@@ -338,22 +337,22 @@
 @c FIXME: Update this section if polarplot and polar axes changes change the
 @c        associated axis properties.
 @c        Matlab also implements rticklabels and thetaticklabels.
-@anchor{XREFyticklabels}
-@anchor{XREFzticklabels}
-@findex yticklabels
-@findex zticklabels
 @DOCSTRING(xticklabels)
 
+@DOCSTRING(yticklabels)
+
+@DOCSTRING(zticklabels)
+
 The @code{xtickangle}, @code{ytickangle}, and @code{ztickangle} functions
 may be used to get or set the rotation angle of labels for the respective axis.
 Each has the same form.
 
-@anchor{XREFytickangle}
-@anchor{XREFztickangle}
-@findex ytickangle
-@findex ztickangle
 @DOCSTRING(xtickangle)
 
+@DOCSTRING(ytickangle)
+
+@DOCSTRING(ztickangle)
+
 @node Two-dimensional Function Plotting
 @subsubsection Two-dimensional Function Plotting
 @cindex plotting, two-dimensional functions
@@ -604,13 +603,12 @@
 
 @DOCSTRING(text)
 
-@c Add cross-references and function index entries for other label functions.
-@anchor{XREFylabel}
-@anchor{XREFzlabel}
-@findex ylabel
-@findex zlabel
 @DOCSTRING(xlabel)
 
+@DOCSTRING(ylabel)
+
+@DOCSTRING(zlabel)
+
 @DOCSTRING(clabel)
 
 @DOCSTRING(box)
@@ -2304,9 +2302,8 @@
 @DOCSTRING(refreshdata)
 
 @anchor{XREFlinkdata}
-@c add the description of the linkdata function here when it is written
-@c remove the explicit anchor when you add the corresponding @DOCSTRING
-@c command
+@c FIXME: Add the description of the linkdata function here when it is written.
+@c Remove the explicit anchor when you add the corresponding @DOCSTRING command.
 
 @node Area Series
 @subsubsection Area Series

--- a/doc/interpreter/testfun.txi	Mon Feb 19 14:08:00 2024 -0800
+++ b/doc/interpreter/testfun.txi	Tue Feb 20 09:56:58 2024 -0800
@@ -340,9 +340,9 @@
 @itemx %!testif HAVE_XXX, HAVE_YYY @dots{}; RUNTIME_COND
 @itemx %!testif @dots{} <MESSAGE>
 Check block only if Octave was compiled with feature @w{@code{HAVE_XXX}}.
-@w{@code{RUNTIME_COND}} is an optional expression to evaluate to check
+@w{@code{RUNTIME_COND}}@ is an optional expression to evaluate to check
 whether some condition is met when the test is executed.  If
-@w{@code{RUNTIME_COND}} is false, the test is skipped.  If @code{<MESSAGE>}
+@w{@code{RUNTIME_COND}}@ is false, the test is skipped.  If @code{<MESSAGE>}
 is present, the test block is interpreted as for @code{xtest}.
 
 @item  %!xtest

--- a/libinterp/corefcn/environment.cc	Mon Feb 19 14:08:00 2024 -0800
+++ b/libinterp/corefcn/environment.cc	Tue Feb 20 09:56:58 2024 -0800
@@ -164,9 +164,9 @@
 @deftypefnx {} {@var{old_val} =} EDITOR (@var{new_val}, "local")
 Query or set the internal variable that specifies the default text editor.
 
-The default value is taken from the environment variable @w{@env{EDITOR}}
+The default value is taken from the environment variable @w{@env{EDITOR}}@
 when Octave starts.  If the environment variable is not initialized,
-@w{@env{EDITOR}} will be set to @qcode{"emacs"}.
+@w{@env{EDITOR}}@ will be set to @qcode{"emacs"}.
 
 When called from inside a function with the @qcode{"local"} option, the
 variable is changed locally for the function and any subroutines it calls.

--- a/libinterp/corefcn/file-io.cc	Mon Feb 19 14:08:00 2024 -0800
+++ b/libinterp/corefcn/file-io.cc	Tue Feb 20 09:56:58 2024 -0800
@@ -756,10 +756,10 @@
 Set the file pointer to the location @var{offset} within the file @var{fid}.
 
 The pointer is positioned @var{offset} characters from the @var{origin}, which
-may be one of the predefined variables @w{@qcode{SEEK_SET}} (beginning),
-@w{@qcode{SEEK_CUR}} (current position), or @w{@qcode{SEEK_END}} (end of file)
+may be one of the predefined variables @w{@qcode{SEEK_SET}}@ (beginning),
+@w{@qcode{SEEK_CUR}}@ (current position), or @w{@qcode{SEEK_END}}@ (end of file)
 or strings @nospell{@qcode{"bof"}}, @nospell{@qcode{"cof"}}, or
-@nospell{@qcode{"eof"}}.  If @var{origin} is omitted, @w{@qcode{SEEK_SET}} is
+@nospell{@qcode{"eof"}}.  If @var{origin} is omitted, @w{@qcode{SEEK_SET}}@ is
 assumed.  @var{offset} may be positive, negative, or zero but not all
 combinations of @var{origin} and @var{offset} can be realized.
 
@@ -3108,7 +3108,7 @@
 is then created with mode read/write and permissions that are system
 dependent (on GNU/Linux systems, the permissions will be 0600 for versions
 of glibc 2.0.7 and later).  The file is opened in binary mode and with the
-@w{@code{O_EXCL}} flag.
+@w{@code{O_EXCL}}@ flag.
 
 If the optional argument @var{delete} is supplied and is true, the file will
 be deleted automatically when Octave exits.

--- a/libinterp/corefcn/interpreter.cc	Mon Feb 19 14:08:00 2024 -0800
+++ b/libinterp/corefcn/interpreter.cc	Tue Feb 20 09:56:58 2024 -0800
@@ -311,7 +311,7 @@
 DEFMETHOD (__traditional__, interp, , ,
            doc: /* -*- texinfo -*-
 @deftypefn {} {@var{tf} =} __traditional__ ()
-Return true if Octave was invoked with the @w{@env{--traditional}} option.
+Return true if Octave was invoked with the @w{@env{--traditional}}@ option.
 @end deftypefn */)
 {
   return ovl (interp.traditional ());

--- a/libinterp/corefcn/nproc.cc	Mon Feb 19 14:08:00 2024 -0800
+++ b/libinterp/corefcn/nproc.cc	Tue Feb 20 09:56:58 2024 -0800
@@ -55,7 +55,7 @@
 
 @item overridable
 same as @code{current}, but overridable through the
-@w{@env{OMP_NUM_THREADS}} environment variable.
+@w{@env{OMP_NUM_THREADS}}@ environment variable.
 @end table
 @end deftypefn */)
 {

--- a/libinterp/corefcn/syscalls.cc	Mon Feb 19 14:08:00 2024 -0800
+++ b/libinterp/corefcn/syscalls.cc	Tue Feb 20 09:56:58 2024 -0800
@@ -426,7 +426,7 @@
 
 @item F_SETFL
 Set the file status flags for @var{fid} to the value specified by @var{arg}.
- The only flags that can be changed are @w{@code{O_APPEND}} and
+The only flags that can be changed are @w{@code{O_APPEND}}@ and
 @w{@code{O_NONBLOCK}}.
 @end vtable
 
@@ -824,7 +824,7 @@
 @item mode
 File mode, as an integer.  Use the functions @w{@code{S_ISREG}},
 @w{@code{S_ISDIR}}, @w{@code{S_ISCHR}}, @w{@code{S_ISBLK}},
-@w{@code{S_ISFIFO}}, @w{@code{S_ISLNK}}, or @w{@code{S_ISSOCK}} to extract
+@w{@code{S_ISFIFO}}, @w{@code{S_ISLNK}}, or @w{@code{S_ISSOCK}}@ to extract
 information from this value.
 
 @item modestr

--- a/scripts/general/bitset.m	Mon Feb 19 14:08:00 2024 -0800
+++ b/scripts/general/bitset.m	Tue Feb 20 09:56:58 2024 -0800
@@ -28,8 +28,8 @@
 ## @deftypefnx {} {@var{B} =} bitset (@var{A}, @var{n}, @var{val})
 ## Set or reset bit(s) at position @var{n} of the unsigned integers in @var{A}.
 ##
-## The least significant bit is @var{n} = 1.  @w{@var{val} = 0} resets bits and
-## @w{@var{val} = 1} sets bits.  If no @var{val} is specified it defaults to
+## The least significant bit is @var{n} = 1.  @w{@var{val} = 0}@ resets bits and
+## @w{@var{val} = 1}@ sets bits.  If no @var{val} is specified it defaults to
 ## 1 (set bit).  All inputs must be the same size or scalars.
 ##
 ## Example 1: Set multiple bits

--- a/scripts/miscellaneous/mkoctfile.m	Mon Feb 19 14:08:00 2024 -0800
+++ b/scripts/miscellaneous/mkoctfile.m	Tue Feb 20 09:56:58 2024 -0800
@@ -137,9 +137,9 @@
 ## purposes only.  Except for @samp{OCTAVE_HOME} and @samp{OCTAVE_EXEC_HOME},
 ## users may not override these variables.
 ##
-## If @w{@env{OCTAVE_HOME}} or @w{@env{OCTAVE_EXEC_HOME}} are set in the
+## If @w{@env{OCTAVE_HOME}}@ or @w{@env{OCTAVE_EXEC_HOME}}@ are set in the
 ## environment, then other variables are adjusted accordingly with
-## @w{@env{OCTAVE_HOME}} or @w{@env{OCTAVE_EXEC_HOME}} substituted for the
+## @w{@env{OCTAVE_HOME}}@ or @w{@env{OCTAVE_EXEC_HOME}}@ substituted for the
 ## original value of the directory specified by the @option{--prefix} or
 ## @option{--exec-prefix} options that were used when Octave was configured.
 ##

--- a/scripts/miscellaneous/version.m	Mon Feb 19 14:08:00 2024 -0800
+++ b/scripts/miscellaneous/version.m	Tue Feb 20 09:56:58 2024 -0800
@@ -66,7 +66,7 @@
 ## when Octave was built instead of which library is currently used.
 ##
 ## The variant with no input and output argument is an alias for the function
-## @w{@env{OCTAVE_VERSION}} provided for compatibility.
+## @w{@env{OCTAVE_VERSION}}@ provided for compatibility.
 ## @seealso{OCTAVE_VERSION, ver}
 ## @end deftypefn
 

--- a/scripts/path/matlabroot.m	Mon Feb 19 14:08:00 2024 -0800
+++ b/scripts/path/matlabroot.m	Tue Feb 20 09:56:58 2024 -0800
@@ -27,7 +27,7 @@
 ## @deftypefn {} {@var{dir} =} matlabroot ()
 ## Return the name of the top-level Octave installation directory.
 ##
-## This is an alias for the function @w{@code{OCTAVE_HOME}} provided for
+## This is an alias for the function @w{@code{OCTAVE_HOME}}@ provided for
 ## compatibility.
 ## @seealso{OCTAVE_HOME}
 ## @end deftypefn

--- a/scripts/plot/appearance/view.m	Mon Feb 19 14:08:00 2024 -0800
+++ b/scripts/plot/appearance/view.m	Tue Feb 20 09:56:58 2024 -0800
@@ -37,10 +37,10 @@
 ## arguments or as 2-element vector.  The viewpoint can also be specified with
 ## Cartesian coordinates @var{x}, @var{y}, and @var{z}.
 ##
-## The call @code{view (2)} sets the viewpoint to @w{@var{azimuth} = 0}
+## The call @code{view (2)} sets the viewpoint to @w{@var{azimuth} = 0}@
 ## and @w{@var{elevation} = 90}, which is the default for 2-D graphs.
 ##
-## The call @code{view (3)} sets the viewpoint to @w{@var{azimuth} = -37.5}
+## The call @code{view (3)} sets the viewpoint to @w{@var{azimuth} = -37.5}@
 ## and @w{@var{elevation} = 30}, which is the default for 3-D graphs.
 ##
 ## If the first argument @var{hax} is an axes handle, then operate on