From c61c00b1f7e3d6cf23501cd02b429474e4d22c73 Mon Sep 17 00:00:00 2001
From: Steve Waldman <swaldman@mchange.com>
Date: Fri, 15 Mar 2019 23:15:51 -0700
Subject: [PATCH] Fix one missing word in docs...

---
 src/doc/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/doc/index.html b/src/doc/index.html
index 56c0e37b..844ddd01 100644
--- a/src/doc/index.html
+++ b/src/doc/index.html
@@ -2757,7 +2757,7 @@ <h4><a name="locating_configuration_information">Locating and Resolving Configur
     </p>
     <p>
       Due to <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-20433">security concerns surrounding liberal parsing of XML references</a>,
-      c3p0 now XML files extremely restrictively by default. Among other things, it <i>no longer expands entity references in XML config files.
+      c3p0 now parses XML files extremely restrictively by default. Among other things, it <i>no longer expands entity references in XML config files.
       Entity references may be silently ignored!</i> It also no longer support xml includes, and tries to disable any use of inline document type definitions if the JVM's underlying
       XML library supports that.
       In the <i>very rare cases</i> where configurations intentionally rely upon entity reference expansion, DTDs, XML include, or other dangerous features, you can turn