DOCSP-13914 fix broken spidermonkey links, 3.2 and 2.4 legacy

Author: andf-mongodb

source/release-notes/2.4-javascript.txt

@@ -80,15 +80,15 @@ Removed Non-Standard SpiderMonkey Features
 ------------------------------------------
 
 V8 does **not** support the following *non-standard* `SpiderMonkey
-<https://developer.mozilla.org/en-US/docs/SpiderMonkey>`_ JavaScript
+<https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey>`_ JavaScript
 extensions, previously supported by MongoDB's use of SpiderMonkey as
 its JavaScript engine.
 
 E4X Extensions
 ~~~~~~~~~~~~~~
 
 V8 does not support the *non-standard* `E4X
-<https://developer.mozilla.org/en-US/docs/E4X>`_ extensions. E4X
+<https://developer.mozilla.org/en-US/docs/Archive/Web/E4X>`_ extensions. E4X
 provides a native `XML
 <https://developer.mozilla.org/en-US/docs/E4X/Processing_XML_with_E4X>`_
 object to the JavaScript language and adds the syntax for embedding

source/release-notes/3.2-javascript.txt

@@ -12,7 +12,7 @@ JavaScript Changes in MongoDB 3.2
 
 In MongoDB 3.2, the javascript engine used for both the :binary:`~bin.mongo` shell
 and for server-side javascript in :binary:`~bin.mongod` changed from V8 to
-`SpiderMonkey <https://developer.mozilla.org/en-US/docs/SpiderMonkey>`_.
+`SpiderMonkey <https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey>`_.
 
 To confirm which JavaScript engine you are using, you can use either
 :js:func:`interpreterVersion()` method in the :binary:`~bin.mongo` shell and the