Fix version in Binary Compatibility to version 4.18

Change-Id: Ib1380d957bd5e91537dca522c494184c3ea1cb82
Signed-off-by: Thomas Watson <tjwatson@us.ibm.com>

development/plans/eclipse_project_plan_4_19.xml

diff --git a/development/plans/eclipse_project_plan_4_19.xml b/development/plans/eclipse_project_plan_4_19.xml
index 3313616..cc1fca3 100644
--- a/development/plans/eclipse_project_plan_4_19.xml
+++ b/development/plans/eclipse_project_plan_4_19.xml
@@ -16,7 +16,7 @@
 <p:introduction>
 <div>
 <p>
-Last revised 11:10 EST December 2, 2020.
+Last revised 11:10 EST February 12, 2021.
 
 <!--
 <img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" />
@@ -332,7 +332,7 @@
   </a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
   
 <p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.19 will be upwards
-  binary-compatible with Eclipse SDK 4.16 except in those areas noted in the
+  binary-compatible with Eclipse SDK 4.18 except in those areas noted in the
   <a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_19_porting_guide.html" target="_top">
     <em>Eclipse 4.19 Plug-in Migration Guide</em>
   </a>. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK