[Getfem-commits] (no subject)

[Tetsuo Koyama]

branch: fixmisspell
commit 2724335a1aa78c6b297253af7db0b3d3ba1c6081
Author: Tetsuo Koyama <address@hidden>
Date:   Sat Feb 2 23:38:17 2019 +0900

    Fix typo in docs
---
 doc/sphinx/source/gmm/blas.rst                       | 2 +-
 doc/sphinx/source/project/appendixA.rst              | 2 +-
 doc/sphinx/source/project/libdesc_event.rst          | 2 +-
 doc/sphinx/source/project/libdesc_low_gen_assemb.rst | 6 +++---
 doc/sphinx/source/project/libdesc_model.rst          | 2 +-
 doc/sphinx/source/tutorial/install.rst               | 2 +-
 doc/sphinx/source/tutorial/thermo_coupling.rst       | 4 ++--
 doc/sphinx/source/tutorial/wheel.rst                 | 2 +-
 8 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/sphinx/source/gmm/blas.rst b/doc/sphinx/source/gmm/blas.rst
index b21ef1c..405aa31 100644
--- a/doc/sphinx/source/gmm/blas.rst
+++ b/doc/sphinx/source/gmm/blas.rst
@@ -10,7 +10,7 @@ Basic linear algebra operations
 ========================================
 
 
-The same choice has been made as in MTL to provide basic operations as 
functions not as operators. The advantages are that it is clearer to see where 
are the linear algebra operations in the program and the programming of 
optimized basic linear operations is greatly simplified.
+The same choice has been made as in MTL to provide basic operations as 
functions not as operators. The advantages are that it is clearer to see where 
are the linear algebra operations in the program and the programming of 
optimized basic linear algebra operations is greatly simplified.
 
 
 scale and scaled
diff --git a/doc/sphinx/source/project/appendixA.rst 
b/doc/sphinx/source/project/appendixA.rst
index 3307c85..8220f42 100644
--- a/doc/sphinx/source/project/appendixA.rst
+++ b/doc/sphinx/source/project/appendixA.rst
@@ -182,7 +182,7 @@ number of reductions have to be made:
   reduction with respect to :math:`i_4` with the matrix :math:`B`.
 
 * Concerning the third term (:math:`\partial^2_{i_7 / P, i_7\mbox{ mod }P}
-  \varphi_{i_6}^{i_5}`)` a reduction of :math:`\widehat{t}_0` with respect to 
:math:`i_7`
+  \varphi_{i_6}^{i_5}`) a reduction of :math:`\widehat{t}_0` with respect to 
:math:`i_7`
   with the matrix :math:`B_3` and a reduction of :math:`\widehat{t}_1` with 
respect also
   to :math:`i_7` with the matrix :math:`B_3 B_2`
 
diff --git a/doc/sphinx/source/project/libdesc_event.rst 
b/doc/sphinx/source/project/libdesc_event.rst
index a889a53..32813e8 100644
--- a/doc/sphinx/source/project/libdesc_event.rst
+++ b/doc/sphinx/source/project/libdesc_event.rst
@@ -70,7 +70,7 @@ has changed between two calls.
 Perspectives
 ^^^^^^^^^^^^
 
-The event management of some objects should be analysed with care  This is the 
case for instance of|mls|, |mfls|, |pmf|, etc.
+The event management of some objects should be analysed with care  This is the 
case for instance of |mls|, |mfls|, |pmf|, etc.
 
 The event management still have to be improved to be a fully reactive system.
 
diff --git a/doc/sphinx/source/project/libdesc_low_gen_assemb.rst 
b/doc/sphinx/source/project/libdesc_low_gen_assemb.rst
index a1a2b19..e5a60f0 100644
--- a/doc/sphinx/source/project/libdesc_low_gen_assemb.rst
+++ b/doc/sphinx/source/project/libdesc_low_gen_assemb.rst
@@ -23,9 +23,9 @@ Files
    :header: "File(s)", "Description"
    :widths: 8, 15
 
-   :file:`getfem_mat_elem_type.h` and:file:` getfem_mat_elem_type.cc, "Defines 
base type for components of an elementary matrix."
-   :file:`getfem_mat_elem.h` and:file:` getfem_mat_elem.cc, "Describes an 
compute elementary matrices."
-   :file:`getfem_assembling_tensors.h` 
and:file:`getfem_assembling_tensors.cc`, "Performs the assembly."
+   :file:`getfem_mat_elem_type.h` and :file:` getfem_mat_elem_type.cc, 
"Defines base type for components of an elementary matrix."
+   :file:`getfem_mat_elem.h` and :file:` getfem_mat_elem.cc, "Describes an 
compute elementary matrices."
+   :file:`getfem_assembling_tensors.h` and 
:file:`getfem_assembling_tensors.cc`, "Performs the assembly."
    :file:`getfem_assembling.h`, "Various assembly terms (linear elasticity, 
generic elliptic term, Dirichlet condition ..."
 
 State
diff --git a/doc/sphinx/source/project/libdesc_model.rst 
b/doc/sphinx/source/project/libdesc_model.rst
index b0e3e24..7910665 100644
--- a/doc/sphinx/source/project/libdesc_model.rst
+++ b/doc/sphinx/source/project/libdesc_model.rst
@@ -37,7 +37,7 @@ Files
 State
 ^^^^^
 
-Constant evolution to includes nex models.
+Constant evolution to includes next models.
 
 Perspectives
 ^^^^^^^^^^^^
diff --git a/doc/sphinx/source/tutorial/install.rst 
b/doc/sphinx/source/tutorial/install.rst
index a3bbca0..1b06631 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 2.
+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.
 
 The main dependences of |Gf| on other libraries are
 
diff --git a/doc/sphinx/source/tutorial/thermo_coupling.rst 
b/doc/sphinx/source/tutorial/thermo_coupling.rst
index df5c9ab..7659e22 100644
--- a/doc/sphinx/source/tutorial/thermo_coupling.rst
+++ b/doc/sphinx/source/tutorial/thermo_coupling.rst
@@ -199,7 +199,7 @@ Mesh generation
 
 |gf| has some limited meshing facilities which are described here. We are 
going to use them. However, there is no guaranty of the quality and conformity 
of the obtained mesh, so it is better to verify the mesh if you use |gf| 
meshing facilities. You can also use external meshers (GiD or Gmsh for 
instance) and import them (see :ref:`ud-load_save_mesh`).
 
-The geometry of the domain is supposed to be a rectangle with three circular 
holes (see :ref:`tut-fig-meshthermo`). The geometry is described thanks to some 
geometrical primitives and union/setminus operations (see 
:file:`src/getfem/getfem)_mesher.h` file. In the following, `h` stands for the 
mesh size and `2` is the degree of the mesh (this means that the transformation 
is of degree two, we used curved edges).
+The geometry of the domain is supposed to be a rectangle with three circular 
holes (see :ref:`tut-fig-meshthermo`). The geometry is described thanks to some 
geometrical primitives and union/setminus operations (see 
:file:`src/getfem/getfem_mesher.h` file). In the following, `h` stands for the 
mesh size and `2` is the degree of the mesh (this means that the transformation 
is of degree two, we used curved edges).
 
 
 ========== 
===========================================================================
@@ -767,7 +767,7 @@ Another option to solve the problem is to solve first the 
thermal and electric p
 Export/visualization of the solution
 ************************************
 
-The finite element problem is now solved. We can plot the solution as follows. 
Note that for the C++ and Python programs, it is necessary to use an external 
external graphical post-processor. Note also that arbitrary quantities can be 
post-processed using the generic interpolation (see 
`ga_interpolation_Lagrange_fem` below). It is also possible to make complex 
exports and slices (see :ref:`ud-export`).
+The finite element problem is now solved. We can plot the solution as follows. 
Note that for the C++ and Python programs, it is necessary to use an external 
graphical post-processor. Note also that arbitrary quantities can be 
post-processed using the generic interpolation (see 
`ga_interpolation_Lagrange_fem` below). It is also possible to make complex 
exports and slices (see :ref:`ud-export`).
 
 ========== 
=====================================================================================================================================================
 **C++**    .. code-block:: c++                             
diff --git a/doc/sphinx/source/tutorial/wheel.rst 
b/doc/sphinx/source/tutorial/wheel.rst
index 963f71f..d1121db 100644
--- a/doc/sphinx/source/tutorial/wheel.rst
+++ b/doc/sphinx/source/tutorial/wheel.rst
@@ -195,7 +195,7 @@ We need a multiplier to prescribe the displacement on the 
rim boundary:
 
   md.add_filtered_fem_variable('lambda_D', mflambda, HOLE_BOUND)
 
-This multiplier represents the boundary stress that is necessary to prescribe 
the vertical displacement to be :math`(0, -\alpha_D)`. The constraint we want 
to apply on this multiplier is that its integral over the rim boundary is the 
vertical force we want to apply. The corresponding weak formulation term to be 
added to the rest of the weak formulation reads
+This multiplier represents the boundary stress that is necessary to prescribe 
the vertical displacement to be :math:`(0, -\alpha_D)`. The constraint we want 
to apply on this multiplier is that its integral over the rim boundary is the 
vertical force we want to apply. The corresponding weak formulation term to be 
added to the rest of the weak formulation reads
 
 .. math::