From 9504e4e2164064ccae228de1c1b9e308f8277dbd Mon Sep 17 00:00:00 2001 From: Daniel_Doehring Date: Fri, 8 Mar 2024 11:39:23 +0100 Subject: [PATCH] typo --- docs/src/meshes/p4est_mesh.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/meshes/p4est_mesh.md b/docs/src/meshes/p4est_mesh.md index 6a21258d92c..2740f335111 100644 --- a/docs/src/meshes/p4est_mesh.md +++ b/docs/src/meshes/p4est_mesh.md @@ -256,7 +256,7 @@ By doing so, only nodesets with a label present in `boundary_symbols` are treate Other nodesets that could be used for diagnostics are not treated as external boundaries. Note that there is a leading colon `:` compared to the label in the `.inp` mesh file. This is required to turn the label into a [`Symbol`](https://docs.julialang.org/en/v1/manual/metaprogramming/#Symbols). -**Important**: In JUlia, a symbol _cannot_ contain a hyphen/dash `-`, i.e., `:BC-1` is _not_ a valid symbol. +**Important**: In Julia, a symbol _cannot_ contain a hyphen/dash `-`, i.e., `:BC-1` is _not_ a valid symbol. Keep this in mind when importing boundaries, you might have to convert hyphens/dashes `-` to underscores `_`, i.e., `BC_1`. A 2D example for this mesh, which is read-in for an unstructured mesh file created with `gmsh`, is presented in