Fix typos

src/3rdParty/salomesmesh/src/StdMeshers/StdMeshers_Penta_3D.cpp

@@ -1046,7 +1046,7 @@ void StdMeshers_Penta_3D::MakeBlock()
           if (iCnt>1) {
             // \begin{E.A.}
             // The current algorithm fails if there is more that one
-            // face wich contains triangles ...
+            // face which contains triangles ...
             // In that case, replace return by break to try another
             // method (coded in "if (iCnt != 1) { ... }")
             //

src/Mod/Arch/Resources/ui/preferences-arch.ui

@@ -440,7 +440,7 @@
         <item>
          <widget class="QLabel" name="label">
           <property name="text">
-           <string>Hidden geomety pattern</string>
+           <string>Hidden geometry pattern</string>
           </property>
          </widget>
         </item>

src/Mod/Assembly/App/opendcm/core/clustergraph.hpp

@@ -215,7 +215,7 @@ struct 	GlobalEdge {
  * This is basically a boost adjacency_list with single linked lists 'listS' as storage for vertices and
  * edges. The edges are undirected. This allows to use all boost graph algorithms and provides therefore
  * an comprehensive way for analysing and manipulating its content. It further extends the class with the
- * possibility to cluster its content and to add properties and objects to all entitys. For more
+ * possibility to cluster its content and to add properties and objects to all entities. For more
  * information, see the module ClusterGraph
  *
  * @tparam edge_prop a mpl::vector with properties which are added to local edges

src/Mod/Assembly/App/opendcm/core/property.hpp

@@ -67,7 +67,7 @@ namespace dcm {
  * retrieving it's reference with get-methods.
  *
  * Propertys are further designed to fit in the concept of compile-time modularisation. To allow the extension
- * of all data-holding entitys with new data types, propertys store their own purpose. Thats
+ * of all data-holding entities with new data types, propertys store their own purpose. Thats
  * done by extending the property struct with a second typedef which is named kind and which specifies of which
  * kind the property is. That means, that this typedef defines when the property shall be used and for which
  * context it is designed for. Dependend on the propertys kind, it will be added to different places inside the dcm.

src/Mod/Assembly/Gui/CommandConstraints.cpp

@@ -537,7 +537,7 @@ CmdAssemblyConstraintAlignment::CmdAssemblyConstraintAlignment()
 {
     sAppModule      = "Assembly";
     sGroup          = QT_TR_NOOP("Assembly");
-    sMenuText       = QT_TR_NOOP("Constraint allignment...");
+    sMenuText       = QT_TR_NOOP("Constraint alignment...");
     sToolTipText    = QT_TR_NOOP("Align the selected entities");
     sWhatsThis      = sToolTipText;
     sStatusTip      = sToolTipText;

src/Mod/Assembly/Gui/TaskAssemblyConstraints.ui

@@ -233,7 +233,7 @@
          </sizepolicy>
         </property>
         <property name="toolTip">
-         <string>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p&gt;Setthe distance between first and second geometrie. Note that in many cases the shortes distance is used (e.g. line - line)&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</string>
+         <string>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p&gt;Set the distance between first and second geometry. Note that in many cases the shortest distance is used (e.g. line - line)&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</string>
         </property>
         <property name="text">
          <string>Distance</string>

src/Mod/ReverseEngineering/App/AppReverseEngineering.cpp

@@ -58,7 +58,7 @@ Dependency of pcl components:
 common: none
 features: common, kdtree, octree, search, (range_image)
 filters: common, kdtree, octree, sample_consenus, search
-geomety: common
+geometry: common
 io: common, octree
 kdtree: common
 keypoints: common, features, filters, kdtree, octree, search, (range_image)