Fix spelling errors and apply clarification proposed by copilot.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: desruisseaux

src/it/multirelease-on-classpath/pom.xml

@@ -23,7 +23,7 @@
   <artifactId>multirelease-on-classpath</artifactId>
   <version>1.0-SNAPSHOT</version>
   <packaging>jar</packaging>
-  <name>Mulirelease in Maven 4</name>
+  <name>Multirelease in Maven 4</name>
 
   <build>
     <plugins>

src/it/multirelease-with-modules/pom.xml

@@ -23,7 +23,7 @@
   <artifactId>multirelease-with-modules</artifactId>
   <version>1.0-SNAPSHOT</version>
   <packaging>jar</packaging>
-  <name>Mulirelease with modules</name>
+  <name>Multirelease with modules</name>
 
   <build>
     <plugins>

src/main/java/org/apache/maven/plugin/compiler/SourcesForRelease.java

@@ -83,7 +83,7 @@ final class SourcesForRelease implements Closeable {
     Map<PathType, List<Path>> dependencySnapshot;
 
     /**
-     * The output directory for the release. This is either base base output directory or a sub-directory
+     * The output directory for the release. This is either the base output directory or a sub-directory
      * in {@code META-INF/versions/}. This field is not used by this class, but made available for making
      * easier to write the {@code target/javac.args} debug file.
      */

src/main/java/org/apache/maven/plugin/compiler/ToolExecutor.java

@@ -667,7 +667,8 @@ public boolean compile(final JavaCompiler compiler, final Options configuration,
                     Iterable<? extends JavaFileObject> sources = fileManager.getJavaFileObjectsFromPaths(c.files);
                     StandardJavaFileManager workaround = fileManager;
                     boolean workaroundNeedsClose = false;
-                    if (WorkaroundForPatchModule.ENABLED) { // Test alone for making clear everything inside is a hack.
+                    // Check flag separately to clearly indicate this entire block is a workaround hack.
+                    if (WorkaroundForPatchModule.ENABLED) {
                         if (workaround instanceof WorkaroundForPatchModule wp) {
                             workaround = wp.getFileManagerIfUsable();
                             if (workaround == null) {

src/main/java/org/apache/maven/plugin/compiler/WorkaroundForPatchModule.java

@@ -41,7 +41,7 @@
  * Workaround for a {@code javax.tools} method which seems not yet supported on all compilers.
  * At least with OpenJDK 24, an {@link UnsupportedOperationException} may occur during the call to
  * {@code fileManager.setLocationForModule(StandardLocation.PATCH_MODULE_PATH, moduleName, paths)}.
- * The workaround is to format the paths in a {@code --path-module} option instead.
+ * The workaround is to format the paths in a {@code --patch-module} option instead.
  * The problem is that we can specify this option only once per file manager instance.
  *
  * <p>We may remove this workaround in a future version of the Maven Compiler Plugin