From 668ff6242ff682fb24c7b78fe28028013531dafe Mon Sep 17 00:00:00 2001
From: Karle3 <web@dentrich.de>
Date: Fri, 25 Oct 2024 13:49:41 +0200
Subject: [PATCH] A comment explains the link anchor.

---
 doc/versioning/submod_versioning.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/versioning/submod_versioning.md b/doc/versioning/submod_versioning.md
index ab80ab4..c126435 100644
--- a/doc/versioning/submod_versioning.md
+++ b/doc/versioning/submod_versioning.md
@@ -545,7 +545,7 @@ If new entries appear in .gitmodules with the pull, they will not be processed a
 the sequence of pull and "submodule update".
 
 
-(changing-a-submodule-branch)=
+(Changing a Submodule Branch)= <!-- !!! keep this link anchor, because referenced later !!! -->
 #### Changing a Submodule Branch
 
 This scenario describes the change of a submodule to another existing
@@ -903,6 +903,7 @@ To use the new version in the base repository, use the commands
 from [Changing a Submodule Branch](#changing-a-submodule-branch) and use
 the new branch name there.
 
+
 #### Creating a New System Version
 
 Creating a complete system version starts by creating a new version for