(commons-csv) 01/03: Javadoc

[gg...@apache.org]

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

ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-csv.git

commit db6aacc575fb6d6d671d4ea40273c6d5c430e19f
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Thu Mar 13 11:18:09 2025 -0400

    Javadoc
---
 src/test/java/org/apache/commons/csv/CSVParserTest.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/test/java/org/apache/commons/csv/CSVParserTest.java b/src/test/java/org/apache/commons/csv/CSVParserTest.java
index 7b5b0c4f..f95c0e07 100644
--- a/src/test/java/org/apache/commons/csv/CSVParserTest.java
+++ b/src/test/java/org/apache/commons/csv/CSVParserTest.java
@@ -65,7 +65,7 @@ import org.junit.jupiter.params.provider.EnumSource;
 import org.junit.jupiter.params.provider.ValueSource;
 
 /**
- * CSVParserTest
+ * Tests {@link CSVParser}.
  *
  * The test are organized in three different sections: The 'setter/getter' section, the lexer section and finally the parser section. In case a test fails, you
  * should follow a top-down approach for fixing a potential bug (its likely that the parser itself fails if the lexer has problems...).