(maven-compiler-plugin) branch master updated: Fix minor grammatical errors in modules.md (#1034)

[el...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new eed5b75  Fix minor grammatical errors in modules.md (#1034)
eed5b75 is described below

commit eed5b75a05064eda76a03cc70bc1d275f3289b7f
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Mon Feb 16 19:36:59 2026 +0000

    Fix minor grammatical errors in modules.md (#1034)
---
 src/site/markdown/modules.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/site/markdown/modules.md b/src/site/markdown/modules.md
index b9b4724..03f2260 100644
--- a/src/site/markdown/modules.md
+++ b/src/site/markdown/modules.md
@@ -118,9 +118,9 @@ src
 ```
 
 Note that the output directory also contains an `org.foo.bar` directory level.
-That directory level is generated by `javac`, this is not a convention invented by Maven.
+That directory level is generated by `javac`. This is not a convention invented by Maven.
 
-Above layout can be declared with the following fragment in the `pom.xml` file.
+The above layout can be declared with the following fragment in the `pom.xml` file.
 Since this example uses the default directory layout for modular projects,
 the `<directory>` elements do not need to be specified.
 
@@ -141,7 +141,7 @@ the `<directory>` elements do not need to be specified.
 ## Black Box testing
 
 "Black Box testing" refers to tests executed without access to the internal code of the project to test.
-Internal codes include package-private classes, interfaces, methods and fields, and also all non-exported packages.
+Internal code includes package-private classes, interfaces, methods and fields, and also all non-exported packages.
 Because the module source hierarchy allows any number of Java modules in the same Maven sub-project,
 it is easy to add an `org.foo.bar.test` module which will test the `org.foo.bar` module as if it was
 an ordinary client application.