Enhance clarity in HeatConduction2DFin.html and HeatConduction2DFinGmsh.html by adding code formatting for boundary condition descriptions and linking to example Gmsh .geo file.

Author: nikoscham

tutorials/HeatConduction2DFin.html

@@ -173,14 +173,15 @@ <h2 id="solvingwithfeascript"><a name="Solving with FEAScript"></a>Solving with
 &lt;/body&gt;</pre
     >
     <p>
-      In the boundary condition definition, the numbers at the left side (from 0 to 3) indicate the boundaries
-      of the geometry (the mesh generator of FEAScript has assigned numbers to the boundaries, starting from
-      the bottom boundary and proceeding clockwise). The "constantTemp" condition sets a constant temperature
-      value. The "symmetry" boundary condition represents a zero-flux type. Finally, the "convection"
-      condition describes a convective heat transfer scenario. In addition, the second argument of the
-      "constantTemp" boundary condition corresponds to the constant temperature value. For a "convection"
-      boundary condition, the second argument represents the \({\frac{h}{k}}\) value, and the third argument
-      indicates the external temperature \(T_0\).
+      In the boundary condition definition, the numbers at the left side (from <code>"0"</code> to
+      <code>"3"</code>) indicate the boundaries of the geometry (the mesh generator of FEAScript has assigned
+      numbers to the boundaries, starting from the bottom boundary and proceeding clockwise). The
+      <code>"constantTemp"</code> condition sets a constant temperature value. The
+      <code>"symmetry"</code> boundary condition represents a zero-flux type. Finally, the
+      <code>"convection"</code> condition describes a convective heat transfer scenario. In addition, the
+      second argument of the <code>"constantTemp"</code> boundary condition corresponds to the constant
+      temperature value. For a <code>"convection"</code> boundary condition, the second argument represents
+      the \({\frac{h}{k}}\) value, and the third argument indicates the external temperature \(T_0\).
     </p>
     <p>
       After solving the case, the results are shown in a 2D contour plot. To visualize it, include an HTML

tutorials/HeatConduction2DFinGmsh.html

@@ -169,15 +169,17 @@ <h2 id="gmshfileimport"><a name="gmshfileimport"></a>Gmsh File Import</h2>
     <p>Important notes about the Gmsh workflow:</p>
     <ul>
       <li>
-        <strong>Physical Groups in Gmsh:</strong> In your <code>.geo</code> file, you need to define physical
-        groups for boundaries using commands like <code>Physical Line("bottom") = {1};</code>. These are
-        mapped to tags in the imported mesh.
+        <strong>Physical Groups in Gmsh:</strong> In your <code>.geo</code> file (see
+        <a href="#gmshgeofile">Example Gmsh <code>.geo</code> File</a>), you need to define physical groups
+        for boundaries using commands like <code>Physical Line("bottom") = {1};</code>. These are mapped to
+        tags in the imported mesh.
       </li>
       <li>
         <strong>Boundary Condition Mapping and Tag Indexing:</strong> When using Gmsh meshes in FEAScript, you
         need to subtract 1 from the Gmsh physical group tag numbers. For example, if your Gmsh file has
-        physical groups with tags "1", "2", "3", "4", you would reference them in FEAScript as "0", "1", "2",
-        "3", respectively. For example:
+        physical groups with tags <code>"1"</code>, <code>"2"</code>, <code>"3"</code>, <code>"4"</code>, you
+        would reference them in FEAScript as <code>"0"</code>, <code>"1"</code>, <code>"2"</code>,
+        <code>"3"</code>, respectively. For example:
         <code>model.addBoundaryCondition("0", ["constantTemp", 200]); // Gmsh physical group tag 1</code>.
         This conversion is necessary because Gmsh uses 1-based indexing while FEAScript uses 0-based indexing.
       </li>