From 16d5663e0ee7c6231a47a94e14ba883cd6811ac5 Mon Sep 17 00:00:00 2001 From: Andrew Feierabend Date: Tue, 12 Jan 2021 11:39:05 -0500 Subject: [PATCH] DOCSP-13914 fix broken spidermonkey links, 3.2 and 2.4 legacy --- source/release-notes/2.4-javascript.txt | 4 ++-- source/release-notes/3.2-javascript.txt | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/source/release-notes/2.4-javascript.txt b/source/release-notes/2.4-javascript.txt index 6cc4ebcf5fd..335bae621e0 100644 --- a/source/release-notes/2.4-javascript.txt +++ b/source/release-notes/2.4-javascript.txt @@ -80,7 +80,7 @@ Removed Non-Standard SpiderMonkey Features ------------------------------------------ V8 does **not** support the following *non-standard* `SpiderMonkey -`_ JavaScript +`_ JavaScript extensions, previously supported by MongoDB's use of SpiderMonkey as its JavaScript engine. @@ -88,7 +88,7 @@ E4X Extensions ~~~~~~~~~~~~~~ V8 does not support the *non-standard* `E4X -`_ extensions. E4X +`_ extensions. E4X provides a native `XML `_ object to the JavaScript language and adds the syntax for embedding diff --git a/source/release-notes/3.2-javascript.txt b/source/release-notes/3.2-javascript.txt index 771c9be9479..bc471987221 100644 --- a/source/release-notes/3.2-javascript.txt +++ b/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 `_. +`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