From b70d5d9a44e60eaf084e2e8e11321e5b5f17af93 Mon Sep 17 00:00:00 2001
From: sant0s <919197+sant0s@users.noreply.github.com>
Date: Mon, 20 Jul 2026 11:36:12 +0100
Subject: [PATCH] Update fundamentals.adoc

Add missing referenced sections.

Signed-off-by: sant0s <919197+sant0s@users.noreply.github.com>
---
 src/docs/antora/modules/ROOT/pages/fundamentals.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/antora/modules/ROOT/pages/fundamentals.adoc b/src/docs/antora/modules/ROOT/pages/fundamentals.adoc
index 8340d92c4..2fd4bf391 100644
--- a/src/docs/antora/modules/ROOT/pages/fundamentals.adoc
+++ b/src/docs/antora/modules/ROOT/pages/fundamentals.adoc
@@ -45,7 +45,7 @@ val modules = ApplicationModules.of(Application::class.java)
 The `modules` will contain an in-memory representation of the application module arrangement derived from the codebase.
 Which parts of that will be detected as a module depends on the Java package structure underneath the package the class pointed to resides in.
 Find out more about the arrangement expected by default in xref:fundamentals.adoc#modules.simple[].
-Advanced arrangements and customization options are described in xref:fundamentals.adoc#modules.advanced[] and
+Advanced arrangements and customization options are described in xref:fundamentals.adoc#modules.advanced[], xref:fundamentals.adoc#modules.nested[] and xref:fundamentals.adoc#modules.open[].
 
 To get an impression of what the analyzed arrangement looks like, we can just write the individual modules contained in the overall model to the console: