From: ana <ana@opencascade.com>
Date: Fri, 13 Jan 2012 14:37:34 +0000 (+0000)
Subject: Fix for the bug IPAL22851: Sub-shapes spelling
X-Git-Tag: V6_5_0a1~206
X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=61b2416dce7a9d806427f28939e11d7f250265a6;p=modules%2Fsmesh.git

Fix for the bug IPAL22851: Sub-shapes spelling
---

diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc
index 5f7466998..fc818ab5b 100644
--- a/doc/salome/gui/SMESH/input/constructing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc
@@ -132,7 +132,7 @@ failure is provided.
 
 \image html meshcomputationfail.png
 
-After you select the error, <b>Show Subshape</b> button allows
+After you select the error, <b>Show Sub-shape</b> button allows
 visualizing the geometrical entity that causes it.
 
 \image html failed_computation.png "Example of the invalid input mesh"
@@ -144,7 +144,7 @@ computation reporting. There are the following possibilities: always
 show information box, only if an error occurs or never. 
 By default, the information box is always shown after mesh computation operation.
 
-<b>Publish Subshape</b> button publishes the subshape, whose meshing
+<b>Publish Sub-shape</b> button publishes the sub-shape, whose meshing
 failed, in GEOM component as a child of the mesh geometry, which
 allows analyzing the problem geometry and creating a submesh on it in
 order to locally tune hypotheses.
@@ -171,7 +171,7 @@ evaluation will be displayed in the following information box:
 <li>
 If the mesh contains concurrent submeshes, it is possible to change
 the priority of their computation, i.e. to change the priority of
-applying algorithms to the shared subshapes of the Mesh shape.</li>
+applying algorithms to the shared sub-shapes of the Mesh shape.</li>
 
 <em>To change submesh priority:</em>
 
@@ -205,7 +205,7 @@ is:
 <li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b>
 (Number of Segments = 12)</li>
 </ul>
-The submeshes become concurrent if they share subshapes that can be meshed 
+The submeshes become concurrent if they share sub-shapes that can be meshed 
 with different algorithms (or different hypothesises).
 In the example, we have three submeshes with concurrent algorithms,
 because they have different hypotheses. 
diff --git a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
index 470d6c5fe..7ffb53e05 100644
--- a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
+++ b/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
@@ -14,7 +14,7 @@ import BLSURFPlugin
 box = geompy.MakeBoxDXDYDZ(200., 200., 200.)
 geompy.addToStudy(box, "box")
 
-# get subshapes
+# get sub-shapes
 Face_1   = geompy.SubShapeAllSorted(box, geompy.ShapeType["FACE"])[0]
 Edge_1   = geompy.SubShapeAllSorted(box, geompy.ShapeType["EDGE"])[0]
 Vertex_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["VERTEX"])[0]