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

garydgregory pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/commons-secure-xml.git

commit 59690abd96fd7d9229fac9185be755d462103b81
Author: Gary Gregory <[email protected]>
AuthorDate: Mon Sep 14 16:38:30 2026 -0700

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

diff --git a/src/test/java/org/apache/commons/xml/secure/ResetSecureTest.java 
b/src/test/java/org/apache/commons/xml/secure/ResetSecureTest.java
index f9e471d..9d376b4 100644
--- a/src/test/java/org/apache/commons/xml/secure/ResetSecureTest.java
+++ b/src/test/java/org/apache/commons/xml/secure/ResetSecureTest.java
@@ -41,7 +41,7 @@
  *
  * <p>The JAXP reset contract returns an object to its just-created state, and 
the stock JDK / Xerces implementations take that literally: they re-install
  * their initial (null) resolvers, silently removing any floor the secure 
wrappers installed after creation. Each test resets a secure object and asserts
- * that an external reference is still either blocked at parse or resolved to 
empty content afterwards; the tests are skipped on platforms whose
+ * that an external reference is still either blocked during parsing or 
resolved to empty content afterward; the tests are skipped on platforms whose
  * implementation does not support {@code reset()} at all (there the securing 
cannot be stripped in the first place).</p>
  */
 class ResetSecureTest {

Reply via email to