Javadoc typo fixes

No code and no semantic change, just fixing Javadoc that
caused errors.

Author: cstamas

maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples/ResolveTransitiveDependenciesParallel.java

@@ -40,8 +40,9 @@
 
 /**
  * Resolves the transitive (compile) LARGE dependencies of an imaginary artifact in parallel.
- * This is the reproducer for locking issues: <a href="https://github.com/apache/maven-resolver/issues/1644>GH-1644</a>
- * This code does NOT run as part of build/tests, it is meant to be ad-hoc run from IDE or alike. */
+ * This is the reproducer for locking issues: <a href="https://github.com/apache/maven-resolver/issues/1644">GH-1644</a>.
+ * This code does NOT run as part of build/tests, it is meant to be ad-hoc run from IDE or alike.
+ */
 public class ResolveTransitiveDependenciesParallel {
 
     /**

maven-resolver-spi/src/main/java/org/eclipse/aether/spi/locking/LockingInhibitor.java

@@ -28,7 +28,7 @@
  */
 public interface LockingInhibitor {
     /**
-     * Should return {@code true for artifacts that needs lock inhibition.
+     * Should return {@code true} for artifacts that needs lock inhibition.
      * <p>
      * <em>Warning: you do not want to override this method, or if you do, think twice.</em>
      */

maven-resolver-spi/src/main/java/org/eclipse/aether/spi/locking/LockingInhibitorFactory.java

@@ -31,7 +31,7 @@
  * artifact locking inhibition is given as option, it should never happen in fact, as aforementioned conditions
  * never stand for them. On the other hand, good examples of resources may be needing locking inhibition are
  * archetype catalogs and RRF prefix files, as both are metadata, hence their remotely fetched cache entries do not
- * conflict locally, furthermore both are produced by remote entities only, and are just cached and read by Maven.
+ * conflict locally, furthermore both are produced by remote entities only, and are just cached and read by Maven.</em>
  *
  * @since 2.0.14
  */