Update links

Author: SougandhS

development/scripts/readme/readme_eclipse.html

@@ -188,7 +188,7 @@ <h2 id="TargetOperatingEnvironments2">
   </p>
   <p>
     Eclipse 4.38 is tested and validated on a number of reference platforms. For the complete list, see <a
-      href="https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_37.xml#target_environments">Target Environments in the
+      href="https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_38.xml#target_environments">Target Environments in the
       4.38 Plan</a>.
   </p>
   <p>
@@ -219,20 +219,20 @@ <h3>
     <a
       class="mozTocH3"
       name="mozTocId324309"> <strong>API Contract Compatibility:</strong> Eclipse SDK 4.38 is upwards contract-compatible with Eclipse SDK 4.37 except in those areas noted in the
-    </a><a href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_37_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension points
+    </a><a href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_38_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension points
     will need to be ported to Eclipse SDK 4.38 APIs. Downward contract compatibility is not supported. There is no guarantee that compliance with Eclipse SDK 4.38 APIs would ensure compliance with
     Eclipse SDK 4.37 APIs. Refer to <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs"><em>Evolving Java-based APIs</em></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.38 is upwards binary-compatible with Eclipse SDK 4.37 except in those areas noted in the <a
-      href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_37_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em> </a>. Downward plug-in compatibility is not supported.
+      href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_38_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em> </a>. Downward plug-in compatibility is not supported.
     Plug-ins for Eclipse SDK 4.38 will not be usable in Eclipse SDK 4.37. Refer to <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs"> <em>Evolving Java-based APIs</em></a> for a discussion of
     the kinds of API changes that maintain binary compatibility.
   </p>
   <p>
     <strong>Source Compatibility:</strong> Eclipse SDK 4.38 is upwards source-compatible with Eclipse SDK 4.37 except in the areas noted in the <a
-      href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_37_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em> </a>. This means that source files written to use Eclipse
+      href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_38_porting_guide.html"><em>Eclipse 4.38 Plug-in Migration Guide</em> </a>. This means that source files written to use Eclipse
     SDK 4.38 APIs might successfully compile and run against Eclipse SDK 4.37 APIs, although this is not guaranteed. Downward source compatibility is not supported. If source files use new Eclipse SDK
     APIs, they will not be usable with an earlier version of the Eclipse SDK.
   </p>