Small doc patch

[David Bateman]

The FAQ still references LOADPATH. This patch fixes that and fixes a few
typos in dynamic.txi

D>

Index: doc/faq/Octave-FAQ.texi
===================================================================
RCS file: /usr/local/cvsroot/octave/doc/faq/Octave-FAQ.texi,v
retrieving revision 1.21
diff -c -r1.21 Octave-FAQ.texi
*** doc/faq/Octave-FAQ.texi     26 Apr 2007 15:41:29 -0000      1.21
--- doc/faq/Octave-FAQ.texi     7 May 2007 16:17:23 -0000
***************
*** 69,75 ****
  command history is saved, so that commands entered during previous
  sessions are not lost.
  
! The Octave distribution includes a 500+ page Texinfo manual.  Access
  to the complete text of the manual is available via the help command
  @c really, the *complete* text?
  at the Octave prompt.
--- 69,75 ----
  command history is saved, so that commands entered during previous
  sessions are not lost.
  
! The Octave distribution includes a 550+ page Texinfo manual.  Access
  to the complete text of the manual is available via the help command
  @c really, the *complete* text?
  at the Octave prompt.
***************
*** 198,207 ****
  
  @item better support for both msvc and mingw
  
- @item many many other minor features and compatibility changes
- 
  @item a fully compatiable MEX interface
  
  @end itemize
  
  Here are some features that have been around since 2.1.NN
--- 198,207 ----
  
  @item better support for both msvc and mingw
  
  @item a fully compatiable MEX interface
  
+ @item many many other minor features and compatibility changes
+ 
  @end itemize
  
  Here are some features that have been around since 2.1.NN
***************
*** 592,607 ****
  @item
  Octave takes a long time to find symbols.
  
! Octave is probably spending this time recursively searching directories for
! function files.  Check the value of the internal variable LOADPATH,
! accessible through the Octave fucntion @code{path}.  For those
! elements that end in @samp{//}, do any name a very large directory tree?
! Does it contain directories that have a mixture of files and 
! directories?  In order for the recursive directory searching code to 
! work efficiently, directories that are to be searched recursively should
! have either function files only, or subdirectories only, but not a
! mixture of both.  Check to make sure that Octave's standard set of
! function files is installed this way.
  @end itemize
  
  @node How do I ...?
--- 592,601 ----
  @item
  Octave takes a long time to find symbols.
  
! Octave uses the @code{genpath} function to recursively add directories
! to the list of directories searched for function files. Check the list
! of directories with the @code{path} command. If the path list is very
! long check your use of the @code{genpath} function.
  @end itemize
  
  @node How do I ...?
Index: doc/interpreter/dynamic.txi
===================================================================
RCS file: /usr/local/cvsroot/octave/doc/interpreter/dynamic.txi,v
retrieving revision 1.8
diff -c -r1.8 dynamic.txi
*** doc/interpreter/dynamic.txi 27 Apr 2007 08:08:19 -0000      1.8
--- doc/interpreter/dynamic.txi 7 May 2007 16:17:23 -0000
***************
*** 1099,1105 ****
  
  The major issue is that the help string will typically be longer than a
  single line of text, and so the formatting of long help strings need to
! be taken into account.  There are several manner in which to happen this
  issue, but the most common is illustrated in the following example
  
  @example
--- 1099,1105 ----
  
  The major issue is that the help string will typically be longer than a
  single line of text, and so the formatting of long help strings need to
! be taken into account.  There are several manner in which to treat this
  issue, but the most common is illustrated in the following example
  
  @example
***************
*** 1130,1138 ****
  and demonstration code.  This is equally a requirement for
  oct-files.  Furthermore the test and demonstration code must be included
  in a comment block of the compiled code to avoid it being interpreted by
! the compiler.  Finally, he Octave test and demonstration code must have
  access to the source code of the oct-file and not just the compiled code
! as th<e tests are stripped from the compiled code.  An example in an
  oct-file might be
  
  @example
--- 1130,1138 ----
  and demonstration code.  This is equally a requirement for
  oct-files.  Furthermore the test and demonstration code must be included
  in a comment block of the compiled code to avoid it being interpreted by
! the compiler.  Finally, the Octave test and demonstration code must have
  access to the source code of the oct-file and not just the compiled code
! as the tests are stripped from the compiled code.  An example in an
  oct-file might be
  
  @example