From 420dc8ecd540f3358d46e79fcd1031b69b099793 Mon Sep 17 00:00:00 2001
From: sant0s <919197+sant0s@users.noreply.github.com>
Date: Mon, 20 Jul 2026 10:48:48 +0100
Subject: [PATCH] Update fundamentals.adoc

Improve text

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..4a62e42c3 100644
--- a/src/docs/antora/modules/ROOT/pages/fundamentals.adoc
+++ b/src/docs/antora/modules/ROOT/pages/fundamentals.adoc
@@ -258,7 +258,7 @@ class ModuleMetadata {}
 Declaring an application module as open will cause the following changes to the verification:
 
 * Access to application module internal types from other modules is generally allowed.
-* All types, also ones residing in sub-packages of the application module base package are added to the xref:fundamentals.adoc#modules.named-interfaces[unnamed named interface], unless explicitly assigned to a named interface.
+* All types, including the ones residing in sub-packages of the application module base package are added to the xref:fundamentals.adoc#modules.named-interfaces[unnamed named interface], unless explicitly assigned to a named interface.
 
 NOTE: This feature is intended to be primarily used with code bases of existing projects gradually moving to the Spring Modulith recommended packaging structure.
 In a fully-modularized application, using open application modules usually hints at sub-optimal modularization and packaging structures.