GH-743 - Correct spelling in documentation.

src/docs/antora/modules/ROOT/pages/documentation.adoc

@@ -82,7 +82,7 @@ Rel_D(Modulith.Application.order, Modulith.Application.catalog, "depends on", $t
 SHOW_LEGEND()
 ....
 
-The second call will create additional diagrams that only include the individual module and the ones they directly depend on on the canvas.
+The second call will create additional diagrams that only include the individual module and the ones they directly depend on the canvas.
 
 .A subset of application modules and their relationships starting from the order module rendered as C4 component diagram
 [plantuml, c4-individual-modules, svg]

src/docs/antora/modules/ROOT/pages/fundamentals.adoc

@@ -508,7 +508,7 @@ The annotation exposes the following attributes to customize:
 |The human readable name of the application to be used in generated xref:documentation.adoc#documentation[documentation].
 
 |`sharedModules`
-|Declares the application modules with the given names as shared modules, which means that they will be always included in xref:testing.adoc#testing[application module integration tests].
+|Declares the application modules with the given names as shared modules, which means that they will always be included in xref:testing.adoc#testing[application module integration tests].
 
 |`additionalPackages`
 |Instructs Spring Modulith to treat the configured packages as additional root application packages. In other words, application module detection will be triggered for those as well.

src/docs/antora/modules/ROOT/pages/testing.adoc

@@ -4,7 +4,7 @@
 Spring Modulith allows to run integration tests bootstrapping individual application modules in isolation or combination with others.
 To achieve this, place a JUnit test class in an application module package or any sub-package of that and annotate it with `@ApplicationModuleTest`:
 
-.A application module integration test class
+.An application module integration test class
 [tabs]
 ======
 Java::
@@ -36,7 +36,7 @@ class OrderIntegrationTests {
 This will run your integration test similar to what `@SpringBootTest` would have achieved but with the bootstrap actually limited to the application module the test resides in.
 If you configure the log level for `org.springframework.modulith` to `DEBUG`, you will see detailed information about how the test execution customizes the Spring Boot bootstrap:
 
-.The log output of a application module integration test bootstrap
+.The log output of an application module integration test bootstrap
 [source, text, subs="macros"]
 ----
   .   ____          _            __ _ _
@@ -62,7 +62,7 @@ If you configure the log level for `org.springframework.modulith` to `DEBUG`, yo
 ----
 
 Note, how the output contains the detailed information about the module included in the test run.
-It creates the application module module, finds the module to be run and limits the application of auto-configuration, component and entity scanning to the corresponding packages.
+It creates the application module, finds the module to be run and limits the application of auto-configuration, component and entity scanning to the corresponding packages.
 
 [[bootstrap-modes]]
 == Bootstrap Modes