--- a/doc/interpreter/install.txi
+++ b/doc/interpreter/install.txi
@@ -286,7 +286,7 @@
 @itemize @bullet
 @item
 On some SCO systems, @code{info} fails to compile if
-@code{HAVE_TERMIOS_H} is defined in @file{config.h}.  Simply removing
+@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.
 
 @item
@@ -310,7 +310,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
-@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
@@ -348,7 +348,7 @@
 @example
 @group
 warning: ANSI C++ prohibits conversion from `(int)' 
-         to `(...)'
+         to `(@dots{})'
 @end group
 @end example
 
@@ -356,10 +356,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, Ultrix 4.2 needs proper declarations for the
-@code{signal} function and the @code{SIG_IGN} macro in the file
+@code{signal} function and the @w{@code{SIG_IGN}} macro in the file
 @file{signal.h}.
 
-On some systems the @code{SIG_IGN} macro is defined to be something like
+On some systems the @w{@code{SIG_IGN}} macro is defined to be something like
 this:
 
 @example
@@ -375,7 +375,7 @@
 
 @noindent
 to match the prototype declaration for the @code{signal} function.  This
-change should also be made for the @code{SIG_DFL} and @code{SIG_ERR}
+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.
 
@@ -440,7 +440,7 @@
 @item
 Some people have reported that calls to shell_cmd and the pager do not
 work on SunOS systems.  This is apparently due to having
-@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
@@ -489,7 +489,7 @@
 If your system does not support IEEE arithmetic but Octave's configure
 script incorrectly determined that it does, you can work around the
 problem by editing the file @file{config.h} to not define
-@code{HAVE_ISINF}, @code{HAVE_FINITE}, and @code{HAVE_ISNAN}.
+@w{@code{HAVE_ISINF}}, @w{@code{HAVE_FINITE}}, and @w{@code{HAVE_ISNAN}}.
 
 In any case, please report this as a bug since it might be possible to
 modify Octave's configuration script to automatically determine the