remove Mozilla Rhino-related docs (#121)

Author: hegemonic

about-commandline.html

@@ -67,7 +67,7 @@ <h2>Table of Contents</h2>
         <tr>
           <td><code>--debug</code>
           </td>
-          <td>Log information that can help debug issues in JSDoc itself. On Rhino, launches the debugger when passed as the first option.</td>
+          <td>Log information that can help debug issues in JSDoc itself.</td>
         </tr>
         <tr>
           <td><code>-e &lt;value&gt;</code>, <code>--encoding &lt;value&gt;</code>

about-plugins.html

@@ -79,8 +79,7 @@ <h3 id="event-handlers">Event Handlers</h3>
 };
 </code></pre>
     </figure>
-    <p>On Node.js, JSDoc fires events in the same order as the underlying code. On Mozilla Rhino, JSDoc fires all of the <code>jsdocCommentFound</code> events at once
-      as soon as it starts parsing a file; all other events are fired in the same order as the underlying code.</p>
+    <p>JSDoc fires events in the same order as the underlying code.</p>
     <p>An event-handler plugin can stop later plugins from running by setting a <code>stopPropagation</code> property on the event object (<code>e.stopPropagation = true</code>).
       A plugin can stop the event from firing by setting a <code>preventDefault</code> property (<code>e.preventDefault = true</code>).</p>
     <h4 id="event-parsebegin">Event: parseBegin</h4>
@@ -282,9 +281,6 @@ <h3 id="node-visitors">Node Visitors</h3>
       <li><code>parser</code>: The JSDoc parser instance.</li>
       <li><code>currentSourceName</code>: The name of the file being parsed.</li>
     </ul>
-    <p>If you run JSDoc on Mozilla Rhino, you can also export a <code>nodeVisitor</code> object that contains a
-      <code>visitNode</code> function. The <code>visitNode</code> function receives the same parameters as for <code>astNodeVisitor</code> objects, but the <code>node</code>      parameter is a Rhino AST node, which is a Java object, rather than an Esprima-style JavaScript object. Rhino node visitors are deprecated as of JSDoc 3.3.0,
-      and support will be removed in a future version of JSDoc.</p>
     <h4 id="making-things-happen">Making things happen</h4>
     <p>The primary reasons to implement a node visitor are to be able to document things that aren&#39;t normally documented (like function calls that create classes)
       or to auto generate documentation for code that isn&#39;t documented. For instance, a plugin might look for calls to a <code>_trigger</code> method since it

content/en/about-commandline.md

@@ -24,7 +24,7 @@ Option|Description
 `-a <value>`, `--access <value>`|Only display symbols with the given `access` property: `private`, `protected`, `public`, or `undefined`, or `all` for all access levels. By default, all except `private` symbols are shown.
 `-c <value>`, `--configure <value>`|The path to a JSDoc [configuration file][config-file]. Defaults to `conf.json` or `conf.json.EXAMPLE` in the directory where JSDoc is installed.
 `-d <value>`, `--destination <value>`|The path to the output folder for the generated documentation. For JSDoc's built-in Haruki template, use `console` to dump data to the console. Defaults to `./out`.
-`--debug`|Log information that can help debug issues in JSDoc itself. On Rhino, launches the debugger when passed as the first option.
+`--debug`|Log information that can help debug issues in JSDoc itself.
 `-e <value>`, `--encoding <value>`|Assume this encoding when reading all source files. Defaults to `utf8`.
 `-h`, `--help`|Display information about JSDoc's command-line options, then exit.
 `--match <value>`|Only run tests whose names contain `value`.

content/en/about-plugins.md

@@ -57,9 +57,7 @@ exports.handlers = {
 ```
 {% endexample %}
 
-On Node.js, JSDoc fires events in the same order as the underlying code. On Mozilla Rhino, JSDoc
-fires all of the `jsdocCommentFound` events at once as soon as it starts parsing a file; all other
-events are fired in the same order as the underlying code.
+JSDoc fires events in the same order as the underlying code.
 
 An event-handler plugin can stop later plugins from running by setting a `stopPropagation` property
 on the event object (`e.stopPropagation = true`). A plugin can stop the event from firing by setting
@@ -344,12 +342,6 @@ empty object on which to set various properties.
 + `parser`: The JSDoc parser instance.
 + `currentSourceName`: The name of the file being parsed.
 
-If you run JSDoc on Mozilla Rhino, you can also export a `nodeVisitor` object that contains a
-`visitNode` function. The `visitNode` function receives the same parameters as for `astNodeVisitor`
-objects, but the `node` parameter is a Rhino AST node, which is a Java object, rather than an
-Esprima-style JavaScript object. Rhino node visitors are deprecated as of JSDoc 3.3.0, and support
-will be removed in a future version of JSDoc.
-
 [esprima-parser]: http://esprima.org/demo/parse.html
 
 #### Making things happen