Update documentation to add 4.0.0 in place of 3.3.0
diff --git a/doc/releases_plan.xml b/doc/releases_plan.xml
index 42a3414..a8c0d66 100644
--- a/doc/releases_plan.xml
+++ b/doc/releases_plan.xml
@@ -24,7 +24,8 @@
<p>This document highlights the release plan for &XercesCName;.</p>
<s3 title="Next Target Release">
- <p>There has been some discussion of incorporating some improvements and modernizing the code base a bit in 3.3.0 release.</p>
+ <p>There has been some discussion of incorporating some improvements and modernizing the code to use
+ C++11 features in a 4.0.0 release.</p>
<p>There will be no further releases in the Xerces-C++ 2-series.</p>
</s3>
diff --git a/doc/source-repository.xml b/doc/source-repository.xml
index 58c26e6..163acf8 100644
--- a/doc/source-repository.xml
+++ b/doc/source-repository.xml
@@ -35,7 +35,7 @@
<p>A writeable mirror of the same official repository is also present in GitHub at <jump href="https://github.com/apache/xerces-c/">https://github.com/apache/xerces-c/</jump> but the official mechanism for contributions remains attaching patches to issues filed in the Apache Jira instance at <jump href="https://issues.apache.org/jira/projects/XERCESC">https://issues.apache.org/jira/projects/XERCESC</jump></p>
- <p>Development generally takes place on the master branch, with legacy branches left open or closed depending on the status of older releases. At present, the master branch and the xerces-3.2 branches are open. Proposed work for a V3.3.0 release may be occurring on master.</p>
+ <p>Development generally takes place on the master branch, with legacy branches left open or closed depending on the status of older releases. At present, the master branch and the xerces-3.2 branches are open. Proposed work for a V4.0.0 release is currently occurring on master.</p>
</s2>
</s1>
