X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fsmesh.git;a=blobdiff_plain;f=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fconstructing_meshes.rst;h=f5aca445734b3be786822858befb1c7d4acac3c5;hp=d26102f43049ac47f650011b1a9ad51a4ed9c41d;hb=3f36e2f8be3687a5c1b48595f878df46c4d81e74;hpb=2954414714f5ae826ec1cc40eeb512e93304e311

diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.rst b/doc/salome/gui/SMESH/input/constructing_meshes.rst
index d26102f43..f5aca4457 100644
--- a/doc/salome/gui/SMESH/input/constructing_meshes.rst
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.rst
@@ -217,7 +217,11 @@ These elements can be kept in the mesh.
 Changing sub-mesh priority
 ##########################
 
-If the mesh contains concurrent :ref:`sub-meshes <constructing_submeshes_page>`, it is possible to change the priority of their computation, i.e. to change the priority of applying algorithms to the shared sub-shapes of the Mesh shape.
+If the mesh contains concurrent :ref:`sub-meshes <constructing_submeshes_page>`, it is possible to change their :ref:`default priority <submesh_priority>`. Changing priority works in two ways:
+
+* For sub-meshes with assigned algorithms of same dimension generating mesh of *several dimensions*, it sets the order in which the sub-meshes are computed.
+* For the rest sub-meshes, it sets the order in which the sub-meshes are checked when looking for  meshing parameters to apply to a sub-shape. Examples below present this way. To impose the order in which sub-meshes with uni-dimensional algorithms are computed, invoke **Compute Sub-mesh** command on sub-meshes in a desired order.
+
 
 *To change sub-mesh priority:*