Skip to content

Fix minor grammatical errors in modules.md #1034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elharo merged 1 commit into from
Feb 16, 2026
+3 −3
Merged

Fix minor grammatical errors in modules.md #1034

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/site/markdown/modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.
Expand Down
Loading