--- a/doc/nashorn/JavaScriptingProgrammersGuide.html	Fri Sep 29 10:00:58 2017 +0200
+++ b/doc/nashorn/JavaScriptingProgrammersGuide.html	Fri Sep 29 16:37:36 2017 +0530
@@ -127,7 +127,7 @@
 <hr>
 <span><a name="package" id="package"></a></span>
 <h2><span>Scripting Package</span></h2>
-<p><span>The Java Scripting functionality is in the <code><a href="http://docs.oracle.com/javase/6/docs/api/javax/script/package-summary.html">javax.script</a></code>
+<p><span>The Java Scripting functionality is in the <code><a href="http://docs.oracle.com/javase/9/docs/api/javax/script/package-summary.html">javax.script</a></code>
 package. This is a relatively small, simple API. The starting point
 of the scripting API is the <code>ScriptEngineManager</code> class.
 A ScriptEngineManager object can discover script engines through

--- a/src/jdk.scripting.nashorn/share/classes/module-info.java	Fri Sep 29 10:00:58 2017 +0200
+++ b/src/jdk.scripting.nashorn/share/classes/module-info.java	Fri Sep 29 16:37:36 2017 +0530
@@ -44,8 +44,7 @@
 </pre>
  *
  * and then use it just as you would any other JSR-223 script engine. See
- * <a href="jdk/nashorn/api/scripting/package-summary.html">
- * {@code jdk.nashorn.api.scripting}</a> package for details.
+ * {@link jdk.nashorn.api.scripting} package for details.
  * <h1>Compatibility</h1>
  * Nashorn is 100% compliant with the
  * <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"