feat(objectionary#3332): format puzzles and javadocs

eo-parser/src/main/java/org/eolang/parser/ParsingErrors.java

@@ -86,7 +86,8 @@ public void syntaxError(
         // @checkstyle MethodBodyCommentsCheck (20 lines)
         // @todo #3332:30min Add more specific error messages.
         //  Currently we write just "error: no viable alternative at input" for all errors.
-        //  It's better to use {@link #recognizer} to get more specific error messages.
+        //  It's better to use 'Recognizer<?, ?> recognizer' parameter of the current method
+        //  to retrieve more specific error messages.
         if (error instanceof NoViableAltException) {
             final Token token = (Token) symbol;
             this.errors.add(

eo-parser/src/main/java/org/eolang/parser/UnderlinedMessage.java

@@ -27,14 +27,18 @@
 
 /**
  * Underlined message.
+ * <p>
  * For example, if you have a message "Problem is here" and you want to underline
  * the word "is", you can create an instance of this class with the following
  * parameters: origin="Problem is here", from=8, length=2.
+ * </p>
+ * <p>
  * The result will be:
  * {@code
  * Problem is here
  *         ^^
  * }
+ * </p>
  * @since 0.50
  * @todo #3332:30min Add more decorators for the error message.
  *  For example, {@link ParsingErrors} currently contains logic related to the message formatting.