Fixup upgrading documentation module

diff --git a/doc/antora/antora.yml b/doc/antora/antora.yml
index 72dd4de0f54de580cf201df864fa409ffe39b63d..b7770a032cce779bb21980629c87b480f3d3b53f 100644 (file)
--- a/doc/antora/antora.yml
+++ b/doc/antora/antora.yml
@@ -11,3 +11,4 @@ nav:
 - modules/ROOT/nav.adoc
 - modules/unlang/nav.adoc
 - modules/developers/nav.adoc
+- modules/upgrade/nav.adoc

diff --git a/doc/antora/modules/upgrade/nav.adoc b/doc/antora/modules/upgrade/nav.adoc
new file mode 100644 (file)
index 0000000..912e5f0
--- /dev/null
+++ b/doc/antora/modules/upgrade/nav.adoc
@@ -0,0 +1 @@
+* xref:index.adoc[Upgrading from v3 to v4]

diff --git a/doc/antora/modules/upgrade/pages/index.adoc b/doc/antora/modules/upgrade/pages/index.adoc
index fad0c6f71355802750c033b90c270a88105039fa..3b08d2b276f5b49c2b8daac6b26809ad794213a1 100644 (file)
--- a/doc/antora/modules/upgrade/pages/index.adoc
+++ b/doc/antora/modules/upgrade/pages/index.adoc
@@ -58,7 +58,7 @@ section.
 The `+log+` section has been updated to remove many configuration items
 which are specific to RADIUS, and to Access-Request packets. Please see
 `+sites-available/default+`, and look for the `+Access-Request+`
-subsection there. See also <<templates.conf.adoc#,`+templates.conf+`>>
+subsection there. See also xref:raddb/templates.conf.adoc[`templates.conf`]
 for a way to regain one global configuration for `+Access-Request+`
 packets.
 
@@ -120,7 +120,7 @@ For `+udp+`, the configuration entries are largley the same as for v3.
 e.g. `+ipaddr+`, `+port+`, etc.
 
 The `+listen+` section then compiles each
-link:#processing-sections[Processing Section] based on the named packet
+<<Processing Sections,Processing Section>> based on the named packet
 types. It has a `+recv+` section for receiving packets, and a `+send+`
 section for sending packets. e.g.
 
@@ -139,7 +139,7 @@ This configuration is different from v3. The benefit is that it is much
 easier to understand. Instead of using things like
 `+Post-Auth-Type Reject+`, we now have just `+send Access-Reject+`.
 
-See also link:#processing-sections[Processing Sections] for how the
+See also <<Processing Sections,Processing Sections>> for how the
 `+unlang+` statements are parsed.
 
 === Clients