diff src/oct-parse.yy @ 12973:b80b18f537ca

doc: Correct various Texinfo warnings about incorrect use of macros. * install.txi: Change @strong{Note:} to @strong{Note}: to move colon outside of macro. * edit.m: Change "WARNING!" to "Warning:" for consistency with other instances. * wilcoxon_test.m: Change "Warning:" to "Caution:" to more accurately reflect level of concern. * strmatch.m: Change @strong{Note:} to @strong{Caution:} to stop spurious cross-reference creation. * datenum.m: Change "Warning:" to "Caution:" to more accurately reflect level of concern. * oct-parse.yy: Change @xref to an @pxref to suppress warning about incorrect usage.
author Rik <octave@nomad.inbox5.com>
date Tue, 16 Aug 2011 10:03:33 -0700
parents ae88a81e5d5c
children 00235a6446da
line wrap: on
line diff
--- a/src/oct-parse.yy
+++ b/src/oct-parse.yy
@@ -4216,10 +4216,10 @@
 calls the function @code{acos} with the argument @samp{-1}.\n\
 \n\
 The function @code{feval} can also be used with function handles of\n\
-any sort. @xref{Function Handles} Historically, @code{feval} was\n\
+any sort (@pxref{Function Handles}).  Historically, @code{feval} was\n\
 the only way to call user-supplied functions in strings, but\n\
 function handles are now preferred due to the cleaner syntax they\n\
-offer. For example,\n\
+offer.  For example,\n\
 \n\
 @example\n\
 @group\n\
@@ -4232,7 +4232,7 @@
 @end example\n\
 \n\
 @noindent\n\
-are equivalent ways to call the function referred to by @var{f}. If it\n\
+are equivalent ways to call the function referred to by @var{f}.  If it\n\
 cannot be predicted beforehand that @var{f} is a function handle or the\n\
 function name in a string, @code{feval} can be used instead.\n\
 @end deftypefn")