From: eap <eap@opencascade.com>
Date: Wed, 29 May 2013 13:36:40 +0000 (+0000)
Subject: Some improvements
X-Git-Tag: V7_3_0a1~382
X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fsmesh.git;a=commitdiff_plain;h=6609664fc375eddcb621f040249b0cee65d3f4e6

Some improvements
---

diff --git a/doc/salome/gui/SMESH/input/about_hypo.doc b/doc/salome/gui/SMESH/input/about_hypo.doc
index 4453a7b8d..e4bf36ca0 100644
--- a/doc/salome/gui/SMESH/input/about_hypo.doc
+++ b/doc/salome/gui/SMESH/input/about_hypo.doc
@@ -5,13 +5,12 @@
 \b Hypotheses represent boundary conditions which will be taken into
 account at calculations of meshes or sub-meshes basing on geometrical
 objects. These hypotheses allow you to manage the level of detail of
-the resulting meshes or submeshes: when applying different hypotheses
-with different parameters you can preset the quantity of meshing
+the resulting meshes or sub-meshes: when applying different hypotheses
+with different parameters you can preset the quantity or size of
 elements which will compose your mesh. So, it will be possible to
 generate a coarse or a more refined mesh or sub-mesh.
 
-In \b MESH there are the following Basic Hypotheses (to introduce
-them, you operate numerical values):
+In \b MESH there are the following Basic Hypotheses:
 <ul>
 <li>\subpage a1d_meshing_hypo_page "1D Hypotheses" (for meshing of 
 <b>edges</b>):</li>
@@ -49,9 +48,8 @@ with other hypotheses:
 
 The choice of a hypothesis depends on:
 <ul>
-<li>the geometrical object (shape) which will be meshed</li>
 <li>the algorithm, which will be selected for meshing of this geometrical object (shape)</li>
+<li>the geometrical object (shape) which will be meshed</li>
 </ul>
 
- 
 */
diff --git a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
index 5aed468f1..142ca62f4 100644
--- a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
+++ b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
@@ -30,13 +30,13 @@ quadrangular elements.</li>
 
 \image html image124.gif "Example of a quadrangular 2D mesh"
 
-<li>For meshing of 3D entities (<b>volume objects</b>):</li>
+<li>For meshing of 3D entities (<b>solid objects</b>):</li>
 
 <ul>
-<li>Hexahedron meshing algorithm (i,j,k) - 6-sided Volumes are split into
+<li>Hexahedron meshing algorithm (i,j,k) - 6-sided Solids are split into
 hexahedral (cubic) elements.</li>
 <li>\subpage cartesian_algo_page</li>
-- internal parts of Volumes are split into hexahedral elements forming a
+- internal parts of Solids are split into hexahedral elements forming a
 Cartesian grid; polyhedra and other types of elements are generated
 where the geometrical boundary intersects Cartesian cells.</li>
 </ul>
diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc
index 126dcfbd9..2255641b3 100644
--- a/doc/salome/gui/SMESH/input/constructing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc
@@ -251,7 +251,7 @@ And the last mesh computation is made with:
 <em>"Result mesh with order SubMesh_3, SubMesh_2, SubMesh_1 "</em></center>
 
 As we can see, each mesh computation has a different number of result
-elements and a different mesh discretisation on the shared edges (the edges 
+elements and a different mesh discretization on the shared edges (the edges 
 that are shared between <b>Face_1</b>, <b>Face_2</b> and <b>Face_3</b>)
 
 Additionally, submesh priority (the order of applied algorithms) can