Mercurial > hg > octave-nkf
diff doc/interpreter/sparse.txi @ 18985:322eb69e30ad stable
doc: Fix some Latin wording in documentation.
* external.txi, interp.txi, sparse.txi: Use "a priori" rather than "a-priori".
Don't use "Firstly".
author | Rik <rik@octave.org> |
---|---|
date | Mon, 02 Jun 2014 08:59:26 -0700 |
parents | d63878346099 |
children | f550c37a9e9c 446c46af4b42 |
line wrap: on
line diff
--- a/doc/interpreter/sparse.txi +++ b/doc/interpreter/sparse.txi @@ -47,7 +47,7 @@ problems where only the non-zero elements of the matrix are stored. Not only does this reduce the amount of memory to store the matrix, but it also means that operations on this type of matrix can -take advantage of the a-priori knowledge of the positions of the +take advantage of the a priori knowledge of the positions of the non-zero elements to accelerate their calculations. A matrix type that stores only the non-zero elements is generally called @@ -73,7 +73,7 @@ There are many different means of storing sparse matrix data. What all of the methods have in common is that they attempt to reduce the complexity -and storage given a-priori knowledge of the particular class of problems +and storage given a priori knowledge of the particular class of problems that will be solved. A good summary of the available techniques for storing sparse matrix is given by Saad @footnote{Y. Saad "SPARSKIT: A basic toolkit for sparse matrix computation", 1994, @@ -573,7 +573,7 @@ same manner as there full counterparts. However, there are certain differences and especially differences with other products sparse implementations. -Firstly, the @qcode{"./"} and @qcode{".^"} operators must be used with care. +First, the @qcode{"./"} and @qcode{".^"} operators must be used with care. Consider what the examples @example