diff --git a/docs/src/meshes/p4est_mesh.md b/docs/src/meshes/p4est_mesh.md
index db75346cab3..3b35ffcad6f 100644
--- a/docs/src/meshes/p4est_mesh.md
+++ b/docs/src/meshes/p4est_mesh.md
@@ -55,7 +55,7 @@ This heading is used to indicate to the mesh constructor which of the above mapp
 create a curvilinear mesh.
 If the Abaqus file header is **not** present then the `P4estMesh` is created with the first strategy above.
 
-#### <a name="nodes"></a>List of corner nodes
+#### [List of corner nodes](@id corner-node-list)
 
 Next, prefaced with `*NODE`, comes a list of the physical `(x,y,z)` coordinates of all the corners.
 The first integer in the list of the corners provides its id number.
@@ -71,7 +71,7 @@ Thus, for the two-dimensional example mesh this block of corner information is
 7, 3.0, -1.0, 0.0
 ```
 
-#### <a name="elements"></a>List of elements
+#### [List of elements](@id element-list)
 
 The element connectivity is given after the list of corners. The header for this information block is
 ```
@@ -237,7 +237,7 @@ For completeness, we provide the entire Abaqus mesh file for the example mesh in
 As an alternative to an Abaqus mesh generated by `HOHQMesh`, `.inp` files with boundary information encoded as nodesets `*NSET,NSET=` can be used to construct a `p4est` mesh.
 This is especially useful for usage of existing meshes (consisting of bilinear elements) which could stem from the popular [`gmsh`](https://gmsh.info/) meshing software.
 
-In addition to the list of [nodes](#nodes) and [elements](#elements) given above, there are nodesets of the form 
+In addition to the list of [nodes](@ref corner-node-list) and [elements](@ref element-list) given above, there are nodesets of the form 
 ```
 *NSET,NSET=PhysicalLine1
 1, 4, 52, 53, 54, 55, 56, 57, 58,