Mercurial > hg > octave-lojdl
changeset 8325:b93ac0586e4b
spelling corrections
Here is a patch with some spelling corrections to the manual.
changeset: 8308:aeaf884ea9af
user: Brian Gough <bjg@gnu.org>
date: Fri Nov 07 09:26:17 2008 -0500
summary: [docs] assoicated => associated
author | Brian Gough<bjg@network-theory.co.uk> |
---|---|
date | Mon, 17 Nov 2008 11:38:39 +0100 |
parents | 1e9cf8ff48f8 |
children | 545b9f62adcf |
files | doc/faq/Octave-FAQ.texi doc/interpreter/func.txi doc/interpreter/image.txi doc/interpreter/install.txi doc/interpreter/interp.txi doc/interpreter/nonlin.txi doc/interpreter/numbers.txi doc/interpreter/package.txi doc/interpreter/plot.txi scripts/general/accumarray.m scripts/general/sortrows.m scripts/image/gmap40.m scripts/image/image.m scripts/miscellaneous/warning_ids.m scripts/plot/area.m scripts/plot/contourc.m scripts/plot/pie.m scripts/sparse/spdiags.m scripts/testfun/assert.m scripts/time/datetick.m src/DLD-FUNCTIONS/matrix_type.cc src/DLD-FUNCTIONS/rand.cc src/bitfcns.cc src/load-path.cc src/variables.cc |
diffstat | 25 files changed, 31 insertions(+), 31 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/faq/Octave-FAQ.texi +++ b/doc/faq/Octave-FAQ.texi @@ -1085,7 +1085,7 @@ @sc{Matlab}, however rethrow and lasterror are only available in Octave 2.9.10 and later. Note that using @code{try}/@code{catch} combined with @samp{rethrow -(lasterror ())} can not guarentee that global variables will be +(lasterror ())} can not guarantee that global variables will be correctly reset, as it won't catch user interrupts with Ctrl-C. For example
--- a/doc/interpreter/func.txi +++ b/doc/interpreter/func.txi @@ -1236,7 +1236,7 @@ Image processing tools. These functions require the X Window System. @item io -Input-ouput functions. +Input-output functions. @item linear-algebra Functions for linear algebra.
--- a/doc/interpreter/image.txi +++ b/doc/interpreter/image.txi @@ -99,7 +99,7 @@ images, RGB images, binary images, and indexed images. A gray-scale image is represented with an M-by-N matrix in which each element corresponds to the intensity of a pixel. An RGB image is -represented with an M-by-N-by3 array where each +represented with an M-by-N-by-3 array where each 3-vector corresponds to the red, green, and blue intensities of each pixel.
--- a/doc/interpreter/install.txi +++ b/doc/interpreter/install.txi @@ -35,7 +35,7 @@ @strong{Note:} This file is automatically generated from @file{doc/interpreter/install.txi} in the Octave sources, so to make -changes to this documenation file, change that source file. +changes to this documentation file, change that source file. @node Installation @chapter Installing Octave @@ -66,7 +66,7 @@ @item --enable-bounds-check Enable bounds checking for indexing operators in the internal array classes. This option is primarily used for debugging Octave. Building -Octave with this option has a negative impact on performace and is not +Octave with this option has a negative impact on performance and is not recommended for general use. @item --enable-64 @@ -271,7 +271,7 @@ @itemize @bullet @item On some SCO systems, @code{info} fails to compile if -@code{HAVE_TERMIOS_H} is defined int @file{config.h}. Simply removing +@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
--- a/doc/interpreter/interp.txi +++ b/doc/interpreter/interp.txi @@ -77,7 +77,7 @@ @float Figure,fig:interpderiv2 @image{interpderiv2,8cm} -@caption{Comparison of the second derivate of the 'phcip' and 'spline' +@caption{Comparison of the second derivative of the 'phcip' and 'spline' interpolation methods for a step function} @end float @end ifnotinfo
--- a/doc/interpreter/nonlin.txi +++ b/doc/interpreter/nonlin.txi @@ -40,7 +40,7 @@ using the function @code{fsolve}, which is based on the @sc{Minpack} subroutine @code{hybrd}. This is an iterative technique so a starting point will have to be provided. This also has the consequence that -convergence is not guarantied even if a solution exists. +convergence is not guaranteed even if a solution exists. @DOCSTRING(fsolve)
--- a/doc/interpreter/numbers.txi +++ b/doc/interpreter/numbers.txi @@ -582,7 +582,7 @@ @DOCSTRING(bitxor) -The bitwise 'not' operator is unary operator that performs a logial +The bitwise 'not' operator is unary operator that performs a logical negation of each of the bits of the value. For this to make sense, the mask against which the value is negated must be defined. Octave's bitwise 'not' operator is @code{bitcmp}.
--- a/doc/interpreter/package.txi +++ b/doc/interpreter/package.txi @@ -400,7 +400,7 @@ @noindent The developer is free to add additional arguments to the @code{DESCRIPTION} file for their own purposes. One further detail to -aid the packager is that the @code{SystemRequirments} and +aid the packager is that the @code{SystemRequirements} and @code{BuildRequires} keywords can have distribution dependent section, and the automatic build process will use these. An example of the format of this is
--- a/doc/interpreter/plot.txi +++ b/doc/interpreter/plot.txi @@ -864,7 +864,7 @@ @itemx xldata @itemx xudata The data to be plotted. The @code{ldata} and @code{udata} elements are -for errobars in the y direction, and the @code{xldata} and @code{xudata} +for errorbars in the y direction, and the @code{xldata} and @code{xudata} elements are for errorbars in the x direction. @item color @@ -941,7 +941,7 @@ characters are also inserted with a code starting with the back-slash (\) character, as in the table @ref{tab:extended}. -In addition, the formating of the text can be changed within the string +In addition, the formatting of the text can be changed within the string with the codes @multitable @columnfractions .2 .2 .6 .2 @@ -1641,7 +1641,7 @@ @item xdata @itemx ydata The x and y coordinates of the original columns of the data passed to -@code{area} prior to the cummulative summation used in the @code{area} +@code{area} prior to the cumulative summation used in the @code{area} function. @item xdatasource
--- a/scripts/general/accumarray.m +++ b/scripts/general/accumarray.m @@ -35,7 +35,7 @@ ## column vector and returns a scalar. The result of the function should not ## depend on the order of the subscripts. ## -## The elements of the returned array that have no subscripts assoicated with +## The elements of the returned array that have no subscripts associated with ## them are set to zero. Defining @var{fillval} to some other value allows ## these values to be defined. ##
--- a/scripts/general/sortrows.m +++ b/scripts/general/sortrows.m @@ -21,7 +21,7 @@ ## Sort the rows of the matrix @var{a} according to the order of the ## columns specified in @var{c}. If @var{c} is omitted, a ## lexicographical sort is used. By default ascending order is used -## however if elements of @var{c} are negative then the corrosponding +## however if elements of @var{c} are negative then the corresponding ## column is sorted in descending order. ## @end deftypefn
--- a/scripts/image/gmap40.m +++ b/scripts/image/gmap40.m @@ -19,7 +19,7 @@ ## -*- texinfo -*- ## @deftypefn {Function File} {} gmap40 (@var{n}) ## Create a color colormap. The colormap is red, green, blue, yellow, -## magneta and cyan. These are the colors that are allowed with patch +## magenta and cyan. These are the colors that are allowed with patch ## objects using gnuplot 4.0, and so this colormap function is specially ## designed for users of gnuplot 4.0. The argument @var{n} should be ## a scalar. If it is omitted, a length of 6 is assumed. Larger values
--- a/scripts/image/image.m +++ b/scripts/image/image.m @@ -22,7 +22,7 @@ ## @deftypefnx {Function File} {} image (@var{x}, @var{y}, @var{img}) ## Display a matrix as a color image. The elements of @var{x} are indices ## into the current colormap, and the colormap will be scaled so that the -## extremes of @var{x} are mapped to the extremes of teh colormap. +## extremes of @var{x} are mapped to the extremes of the colormap. ## ## It first tries to use @code{gnuplot}, then @code{display} from ## @code{ImageMagick}, then @code{xv}, and then @code{xloadimage}.
--- a/scripts/miscellaneous/warning_ids.m +++ b/scripts/miscellaneous/warning_ids.m @@ -202,7 +202,7 @@ ## automatically in literal matrices. ## ## @item Octave:single-quote-string -## Print warning if a signle quote character is used to introduce a +## Print warning if a single quote character is used to introduce a ## string constant. ## ## @item Octave:str-to-num
--- a/scripts/plot/area.m +++ b/scripts/plot/area.m @@ -23,12 +23,12 @@ ## @deftypefnx {Function File} {} area (@var{y}, @dots{}) ## @deftypefnx {Function File} {} area (@var{h}, @dots{}) ## @deftypefnx {Function File} {@var{h} =} area (@dots{}) -## Area plot of cummulative sum of the columns of @var{y}. This shows the +## Area plot of cumulative sum of the columns of @var{y}. This shows the ## contributions of a value to a sum, and is functionally similar to ## @code{plot (@var{x}, cumsum (@var{y}, 2))}, except that the area under ## the curve is shaded. ## -## If the @var{x} argument is ommitted it is assumed to be given by +## If the @var{x} argument is omitted it is assumed to be given by ## @code{1 : rows (@var{y})}. A value @var{lvl} can be defined that determines ## where the base level of the shading under the curve should be defined. ##
--- a/scripts/plot/contourc.m +++ b/scripts/plot/contourc.m @@ -18,7 +18,7 @@ ## -*- texinfo -*- ## @deftypefn {Function File} {[@var{c}, @var{lev}] =} contourc (@var{x}, @var{y}, @var{z}, @var{vn}) -## Compute isolines (countour lines) of the matrix @var{z}. +## Compute isolines (contour lines) of the matrix @var{z}. ## Parameters @var{x}, @var{y} and @var{vn} are optional. ## ## The return value @var{lev} is a vector of the contour levels.
--- a/scripts/plot/pie.m +++ b/scripts/plot/pie.m @@ -24,7 +24,7 @@ ## @deftypefnx {Function File} {@var{h} =} pie (@dots{}); ## Produce a pie chart. ## -## Called with a single vector arrgument, produces a pie chart of the +## Called with a single vector argument, produces a pie chart of the ## elements in @var{x}, with the size of the slice determined by percentage ## size of the values of @var{x}. ##
--- a/scripts/sparse/spdiags.m +++ b/scripts/sparse/spdiags.m @@ -33,7 +33,7 @@ ## Otherwise a matrix of @var{m} by @var{n} is created with the ## diagonals given by @var{v}. ## -## Negative values of @var{c} representive diagonals below the main +## Negative values of @var{c} represent diagonals below the main ## diagonal, and positive values of @var{c} diagonals above the main ## diagonal. ##
--- a/scripts/testfun/assert.m +++ b/scripts/testfun/assert.m @@ -42,7 +42,7 @@ ## ## @item assert(@var{observed}, @var{expected}, @var{tol}) ## Accept a tolerance when comparing numbers. -## If @var{tol} is possitive use it as an absolute tolerance, will produce an error if +## If @var{tol} is positive use it as an absolute tolerance, will produce an error if ## @code{abs(@var{observed} - @var{expected}) > abs(@var{tol})}. ## If @var{tol} is negative use it as a relative tolerance, will produce an error if ## @code{abs(@var{observed} - @var{expected}) > abs(@var{tol} * @var{expected})}.
--- a/scripts/time/datetick.m +++ b/scripts/time/datetick.m @@ -24,7 +24,7 @@ ## @deftypefnx {Function File} {} datetick (@dots{ax}, @dots{}) ## Adds date formatted tick labels to an axis. The axis the apply the ## ticks to is determined by @var{axis} that can take the values "x", -## "y" or "z". The default value is "x". The formating of the labels is +## "y" or "z". The default value is "x". The formatting of the labels is ## determined by the variable @var{form}, that can either be a string in ## the format needed by @code{dateform}, or a positive integer that can ## be accepted by @code{datestr}.
--- a/src/DLD-FUNCTIONS/matrix_type.cc +++ b/src/DLD-FUNCTIONS/matrix_type.cc @@ -99,7 +99,7 @@ matrix type.\n\ \n\ Also the test for positive definiteness is a low cost test for a hermitian\n\ -matrix with a real positive diagonal. This does not guarentee that the matrix\n\ +matrix with a real positive diagonal. This does not guarantee that the matrix\n\ is positive definite, but only that it is a probable candidate. When such a\n\ matrix is factorized, a Cholesky factorization is first attempted, and if\n\ that fails the matrix is then treated with an LU factorization. Once the\n\
--- a/src/DLD-FUNCTIONS/rand.cc +++ b/src/DLD-FUNCTIONS/rand.cc @@ -341,7 +341,7 @@ available, otherwise from cpu time, wall clock time and the current\n\ fraction of a second.\n\ \n\ -To compute the psuedo-random sequence, @code{rand} uses the Mersenne\n\ +To compute the pseudo-random sequence, @code{rand} uses the Mersenne\n\ Twister with a period of 2^19937-1 (See M. Matsumoto and T. Nishimura,\n\ ``Mersenne Twister: A 623-dimensionally\n\ equidistributed uniform pseudorandom number generator'', ACM Trans. on\n\ @@ -884,7 +884,7 @@ @item For matrix @var{l} > 10, use patchwork rejection method.\n\ Stadlober E., et al., WinRand source code, available via FTP, or\n\ H. Zechner, 'Efficient sampling from continuous and discrete\n\ -unimodal distributions', Doctoral Dissertaion, 156pp., Technical\n\ +unimodal distributions', Doctoral Dissertation, 156pp., Technical\n\ University Graz, Austria, 1994.\n\ @item For @var{l} > 1e8, use normal approximation.\n\ L. Montanet, et al., 'Review of Particle Properties', Physical Review\n\
--- a/src/bitfcns.cc +++ b/src/bitfcns.cc @@ -513,7 +513,7 @@ "-*- texinfo -*-\n\ @deftypefn {Built-in Function} {} bitmax ()\n\ Return the largest integer that can be represented as a floating point\n\ -value. On IEEE-754 compatiable systems, @code{bitmax} is @code{2^53 - 1}.\n\ +value. On IEEE-754 compatible systems, @code{bitmax} is @code{2^53 - 1}.\n\ @end deftypefn") { octave_value retval;
--- a/src/load-path.cc +++ b/src/load-path.cc @@ -1701,7 +1701,7 @@ DEFUN (genpath, args, , "-*- texinfo -*-\n\ @deftypefn {Built-in Function} {} genpath (@var{dir})\n\ -Return a path constructed from @var{dir} and all its subdiretories.\n\ +Return a path constructed from @var{dir} and all its subdirectories.\n\ @end deftypefn") { octave_value retval;
--- a/src/variables.cc +++ b/src/variables.cc @@ -2345,7 +2345,7 @@ The arguments are treated as regular expressions as any variables that\n\ match will be cleared.\n\ @end table\n\ -With the execption of @code{exclusive}, all long options can be used \n\ +With the exception of @code{exclusive}, all long options can be used \n\ without the dash as well.\n\ @end deffn") {