[Getfem-commits] (no subject)

[Tetsuo Koyama]

branch: fixmisspell
commit 0ddc3c4abbe3d2e3cde9318297bd482602670cc5
Author: Tetsuo Koyama <address@hidden>
Date:   Fri Jul 12 21:33:50 2019 +0900

    Fix typo in docs
---
 doc/sphinx/source/biblio.rst                     | 2 +-
 doc/sphinx/source/glossary.rst                   | 2 +-
 doc/sphinx/source/matlab/examples.rst            | 2 +-
 doc/sphinx/source/screenshots/shots.rst          | 2 +-
 doc/sphinx/source/tutorial/install.rst           | 2 +-
 doc/sphinx/source/userdoc/appendixB.rst          | 4 ++--
 doc/sphinx/source/userdoc/gasm_high.rst          | 4 ++--
 doc/sphinx/source/userdoc/model_continuation.rst | 6 +++---
 doc/sphinx/source/userdoc/parallel.rst           | 4 ++--
 9 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/doc/sphinx/source/biblio.rst b/doc/sphinx/source/biblio.rst
index cfc818b..0b8831f 100644
--- a/doc/sphinx/source/biblio.rst
+++ b/doc/sphinx/source/biblio.rst
@@ -38,7 +38,7 @@ References
    *Fictitious domain finite element methods using cut elements: I. A 
stabilized Lagrange multiplier method*. Computer Methods in Applied Mechanics, 
199:41-44, 2680-2686, 2010.
 
 .. [ca-re-so1994] D. Calvetti, L. Reichel and D.C. Sorensen.
-   *An implicitely restarted Lanczos method for large symmetric eigenvalue 
problems*. Electronic Transaction on Numerical Analysis}. 2:1-21, 1994.
+   *An implicitly restarted Lanczos method for large symmetric eigenvalue 
problems*. Electronic Transaction on Numerical Analysis}. 2:1-21, 1994.
 
 .. [CH-LA-RE2008] E. Chahine, P. Laborde, Y. Renard.
    *Crack-tip enrichment in the Xfem method using a cut-off function*. Int. J. 
Numer. Meth. Engng., 75(6):629-646, 2008.
diff --git a/doc/sphinx/source/glossary.rst b/doc/sphinx/source/glossary.rst
index d31009a..0a1ad68 100644
--- a/doc/sphinx/source/glossary.rst
+++ b/doc/sphinx/source/glossary.rst
@@ -54,7 +54,7 @@ Glossary
       The mesh_fem object is a mesh with a **finite element method** defined
       on each **element**. This
       represent a finite element space on which a unknown or a data on the
-      considered domain will be discribed.
+      considered domain will be described.
 
    Mesh_Im
       The mesh_im object is a mesh with a **cubature method** defined on
diff --git a/doc/sphinx/source/matlab/examples.rst 
b/doc/sphinx/source/matlab/examples.rst
index 276119a..55de4f4 100644
--- a/doc/sphinx/source/matlab/examples.rst
+++ b/doc/sphinx/source/matlab/examples.rst
@@ -138,7 +138,7 @@ The array ``border`` has two rows, on the first row is a 
convex number, on the
 second row is a face number (which is local to the convex, there is no global
 numbering of faces). Then this set of faces is assigned to the region number 
42.
 
-At this point, we just have to desribe the model and run the solver to get the
+At this point, we just have to describe the model and run the solver to get the
 solution! The ":envvar:`model`" is created with the ``gf_model`` (or 
``gfModel``)
 constructor. A model is basically an object which build a global linear system
 (tangent matrix for non-linear problems) and its associated right hand side.
diff --git a/doc/sphinx/source/screenshots/shots.rst 
b/doc/sphinx/source/screenshots/shots.rst
index 76794fc..aaaff82 100644
--- a/doc/sphinx/source/screenshots/shots.rst
+++ b/doc/sphinx/source/screenshots/shots.rst
@@ -145,7 +145,7 @@ A 3D crack, made via level-set
 ------------------------------
 
 In this example, the mesh was a simple cartesian mesh 20x20x1, and the crack 
geometry was
-defined implicitely via a levelset.
+defined implicitly via a levelset.
 
 .. |im-crack3d| image:: images/fissure_3d_de_traviole.*
 
diff --git a/doc/sphinx/source/tutorial/install.rst 
b/doc/sphinx/source/tutorial/install.rst
index 1d98fb3..d4fd81e 100644
--- a/doc/sphinx/source/tutorial/install.rst
+++ b/doc/sphinx/source/tutorial/install.rst
@@ -9,7 +9,7 @@
 How to install
 ==============
 
-Since |gf| is developed on linux (Ubuntu), the installation is simpler on 
linux, especially on Debian-based distributions (Debian/Ubuntu/Mint). However, 
|gf| can be installed also on other linux distributions, on Mac os X and 
Windows. In order to compile |gf| from sources, you need a recent C++ complier 
(supporting C++ 11 standard) and a recent version of python.
+Since |gf| is developed on linux (Ubuntu), the installation is simpler on 
linux, especially on Debian-based distributions (Debian/Ubuntu/Mint). However, 
|gf| can be installed also on other linux distributions, on Mac os X and 
Windows. In order to compile |gf| from sources, you need a recent C++ complier 
(supporting C++ 14 standard) and a recent version of python.
 
 The main dependences of |Gf| on other libraries are
 
diff --git a/doc/sphinx/source/userdoc/appendixB.rst 
b/doc/sphinx/source/userdoc/appendixB.rst
index 5443344..04050b4 100644
--- a/doc/sphinx/source/userdoc/appendixB.rst
+++ b/doc/sphinx/source/userdoc/appendixB.rst
@@ -651,11 +651,11 @@ Others methods are:
        - 90
 
      * - ``"IM_CUBE4D(5)"``
-       - 4D parallelepipeded
+       - 4D parallelepiped
        - 24
 
      * - ``"IM_CUBE4D(9)"``
-       - 4D parallelepipeded
+       - 4D parallelepiped
        - 145
 
 
diff --git a/doc/sphinx/source/userdoc/gasm_high.rst 
b/doc/sphinx/source/userdoc/gasm_high.rst
index 6c8d4e2..718ef78 100644
--- a/doc/sphinx/source/userdoc/gasm_high.rst
+++ b/doc/sphinx/source/userdoc/gasm_high.rst
@@ -789,9 +789,9 @@ A specific transformation (see previous section) is defined 
in order to allows t
   add_element_extrapolation_transformation
   (workspace, transname, my_mesh, std::map<size_type, size_type> &elt_corr);
 
-The map elt_corr should contain the correspondances between the elements where 
the transformation is to be applied and the respective elements where the 
extrapolation has to be made. On the element not listed in the map, no 
transformation is applied and the evaluation is performed normally on the 
current element.
+The map elt_corr should contain the correspondences between the elements where 
the transformation is to be applied and the respective elements where the 
extrapolation has to be made. On the element not listed in the map, no 
transformation is applied and the evaluation is performed normally on the 
current element.
 
-The following functions allow to change the element correspondance of a 
previously added element extrapolation transformation::
+The following functions allow to change the element correspondence of a 
previously added element extrapolation transformation::
 
   set_element_extrapolation_correspondance
   (model, transname, std::map<size_type, size_type> &elt_corr);
diff --git a/doc/sphinx/source/userdoc/model_continuation.rst 
b/doc/sphinx/source/userdoc/model_continuation.rst
index 8ea2b2d..5e999f7 100644
--- a/doc/sphinx/source/userdoc/model_continuation.rst
+++ b/doc/sphinx/source/userdoc/model_continuation.rst
@@ -169,7 +169,7 @@ piece.
 Having this approximation at our disposal, we restart the predictor-corrector
 with :math:`(Y_{j}, r \tilde{T})`.
 
-In |gf|, the continuation is implemented for two ways of parametrisation of the
+In |gf|, the continuation is implemented for two ways of parameterization of 
the
 model:
 
 1. The parameter :math:`\lambda` is directly a scalar datum, which the model
@@ -222,7 +222,7 @@ A point :math:`\bar{Y}` is called a *bifurcation point* of 
the system
 curves pass through it. The following result gives a test for *smooth*
 bifurcation points (see, e.g., [Georg2001]_):
 
-Let :math:`s \mapsto Y(s)` be a parametrisation of a solution curve and
+Let :math:`s \mapsto Y(s)` be a parameterization of a solution curve and
 :math:`\bar{Y} := Y(\bar{s})` be a bifurcation point. Moreover, let
 :math:`T^{\top} \dot{Y}(\bar{s}) > 0`,
 :math:`B \notin \mathrm{Im}(J(\bar{Y}))`,
@@ -423,7 +423,7 @@ or even tools for non-smooth ones do. The real numbers 
``delta_max``,
 ``ndir`` and ``nspan`` stand for :math:`n_{\mathrm{dir}}` and
 :math:`n_{\mathrm{span}}`, respectively.
 
-Optionally, parametrisation by a vector datum is then declared by::
+Optionally, parameterization by a vector datum is then declared by::
 
   S.set_parametrised_data_names(initdata_name, finaldata_name, 
currentdata_name);
 
diff --git a/doc/sphinx/source/userdoc/parallel.rst 
b/doc/sphinx/source/userdoc/parallel.rst
index 87a7045..b429990 100644
--- a/doc/sphinx/source/userdoc/parallel.rst
+++ b/doc/sphinx/source/userdoc/parallel.rst
@@ -33,7 +33,7 @@ be used to drive the parallel version of getfem (the other 
interfaces has
 not been parallelized for the moment). See demo_parallel_laplacian.py in
 the interface/test/python directory.
 
-With the option ``-D GETFEM_PARA_LEVEL=2``, each mesh used is implicitely
+With the option ``-D GETFEM_PARA_LEVEL=2``, each mesh used is implicitly
 partitionned (using METIS) into a
 number of regions corresponding to the number of processors and the assembly
 procedures are parallelized. This means that the tangent matrix and the
@@ -68,7 +68,7 @@ Parallelization of getfem is still considered a "work in 
progress". A certain nu
 
   Most of assembly procedures (in :file:`getfem/getfem_assembling.h`) have a 
parameter corresponding to the region in which the assembly is to be computed. 
They are not parallelized themselves but aimed to be called with a different 
region in each process to distribute the job. Note that the file 
:file:`getfem/getfem_config.h` contains a procedures called 
MPI_SUM_SPARSE_MATRIX allowing to gather the contributions of a distributed 
sparse matrix.
 
-  The following assembly procedures are implicitely parallelized using the 
option ``-D GETFEM_PARA_LEVEL=2``:
+  The following assembly procedures are implicitly parallelized using the 
option ``-D GETFEM_PARA_LEVEL=2``:
 
   * computation of norms (``asm_L2_norm``, ``asm_H1_norm``, ``asm_H2_norm`` 
..., in :file:`getfem/getfem_assembling.h`),