Docsp 15981 update node links (#175)

biniona-mongodb · kyuan-mongodb · web-flow · commit b15273c1ba58 · 2021-06-08T12:12:58.000-04:00
Co-authored-by: kyuan-mongodb &lt;78768401+kyuan-mongodb@users.noreply.github.com&gt;
diff --git a/source/faq.txt b/source/faq.txt
@@ -29,7 +29,7 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
 
        .. tip::
 
-          To modify the allowed time for :node-api:`MongoClient.connect <MongoClient.html#.connect>` to establish a
+          To modify the allowed time for :node-api-4.0:`MongoClient.connect </classes/mongoclient.html#.connect>` to establish a
           connection to a MongoDB server, use the ``serverSelectionTimeoutMS`` option instead.
 
        **Default:** 10000
@@ -39,7 +39,7 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
        never time out the socket. This option applies only to sockets that
        have already been connected.
    * - maxTimeMS
-     - :node-api:`maxTimeMS </Cursor.html#maxTimeMS>` is the maximum
+     - :node-api-4.0:`maxTimeMS </classes/findcursor.html#maxtimems>` is the maximum
        amount of time the server should wait for an operation to complete
        after it has reached the server. If an operation runs over the
        specified time limit, it returns a timeout error.
diff --git a/source/fundamentals/collations.txt b/source/fundamentals/collations.txt
@@ -284,7 +284,7 @@ contains the following documents:
 Aggregation Example
 ```````````````````
 
-To use collation with the :node-api:`aggregate </Collection.html#aggregate>`
+To use collation with the :node-api-4.0:`aggregate </classes/collection.html#aggregate>`
 operation, pass the collation document in the options field, after the
 array of pipeline stages.
 
diff --git a/source/fundamentals/connection.txt b/source/fundamentals/connection.txt
@@ -313,5 +313,4 @@ URI to specify the behavior of the client.
 
 
 
-For a complete list of options, see the :node-api:`MongoClient
-<MongoClient.html>` API reference page.
+For a complete list of options, see the :node-api-4.0:`MongoClient </classes/mongoclient.html>` API reference page.
diff --git a/source/fundamentals/crud/compound-operations.txt b/source/fundamentals/crud/compound-operations.txt
@@ -42,15 +42,15 @@ Built-in Methods
 
 There are three major compound operations:
 
-- :node-api:`findOneAndDelete() </Collection.html#findOneAndDelete>`
+- :node-api-4.0:`findOneAndDelete() </classes/collection.html#findoneanddelete>`
   matches multiple documents to a supplied query and removes the first
   of those matched documents.
 
-- :node-api:`findOneAndUpdate() </Collection.html#findOneAndUpdate>`
+- :node-api-4.0:`findOneAndUpdate() </classes/collection.html#findoneandupdate>`
   matches multiple documents to a supplied query and updates the first
   of those matched documents using the provided update document.
 
-- :node-api:`findOneAndReplace() </Collection.html#findOneAndReplace>`
+- :node-api-4.0:`findOneAndReplace() </classes/collection.html#findoneandreplace>`
   matches multiple documents to a supplied query and replaces the first
   of those matched documents using the provided replacement document.
 
diff --git a/source/fundamentals/crud/read-operations/cursor.txt b/source/fundamentals/crud/read-operations/cursor.txt
@@ -16,9 +16,8 @@ Overview
 Read operations that return multiple documents do not immediately return
 all values matching the query. Because a query can potentially match
 very large sets of documents, these operations rely upon an
-object called a :node-api:`cursor <Cursor.html>`
-that fetches documents in batches to reduce both memory consumption and
-network bandwidth usage. Cursors are highly configurable and offer
+object called a cursor. A cursor fetches documents in batches to reduce both
+memory consumption and network bandwidth usage. Cursors are highly configurable and offer
 multiple interaction paradigms for different use cases.
 
 The following functions directly return cursors:
@@ -72,8 +71,7 @@ pulling all matching documents into a collection in process memory.
 For Each Functional Iteration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can pass a function to the :node-api:`forEach()
-<Cursor.html#forEach>` method of any cursor to iterate through
+You can pass a function to the :node-api-4.0:`forEach() </classes/findcursor.html#foreach>` method of any cursor to iterate through
 results in a functional style:
 
 .. literalinclude:: /code-snippets/crud/cursor.js
@@ -96,9 +94,9 @@ allows you to use cursors in ``for``...``await`` loops:
 Manual Iteration
 ~~~~~~~~~~~~~~~~
 
-You can use the :node-api:`hasNext() <Cursor.html#hasNext>`
+You can use the :node-api-4.0:`hasNext() </classes/findcursor.html#hasnext>`
 method to check if a cursor can provide additional data, and then use
-the :node-api:`next() <Cursor.html#next>`
+the :node-api-4.0:`next() </classes/findcursor.html#next>`
 method to retrieve the subsequent element of the cursor:
 
 .. literalinclude:: /code-snippets/crud/cursor.js
@@ -132,10 +130,9 @@ Fetch All Documents At Once
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 For use cases that require all documents matched by a query to be held
-in memory at the same time, use :node-api:`toArray()
-<Cursor.html#toArray>`. Note that large sets of
-matched documents can cause performance issues or even failures due to
-exceeding memory constraints.
+in memory at the same time, use :node-api-4.0:`toArray() </classes/findcursor.html#toarray>`. 
+Note that large sets of matched documents can cause performance issues or even
+failures due to exceeding memory constraints.
 
 .. literalinclude:: /code-snippets/crud/cursor.js
    :language: javascript
@@ -150,7 +147,7 @@ Count
 ~~~~~
 
 For an estimated count of the number of documents referenced by the
-cursor, use :node-api:`count() <Cursor.html#count>`:
+cursor, use :node-api-4.0:`count() </classes/findcursor.html#count>`:
 
 .. literalinclude:: /code-snippets/crud/cursor.js
    :language: javascript
@@ -161,7 +158,7 @@ Rewind
 ~~~~~~
 
 To reset a cursor to its initial position in the set of returned
-documents, use :node-api:`rewind() <Cursor.html#rewind>`.
+documents, use :node-api-4.0:`rewind() </classes/findcursor.html#rewind>`.
 
 .. literalinclude:: /code-snippets/crud/cursor.js
    :language: javascript
@@ -173,7 +170,7 @@ Close
 
 Cursors consume memory and network resources both in the client
 application and in the connected instance of MongoDB. Use
-:node-api:`close() <Cursor.html#close>`
+:node-api-4.0:`close() </classes/findcursor.html#close>`
 to free up a cursor's resources in both the client application
 and the MongoDB server:
 
diff --git a/source/fundamentals/crud/read-operations/limit.txt b/source/fundamentals/crud/read-operations/limit.txt
@@ -91,7 +91,7 @@ calls are equivalent:
 
 For more information on the ``options`` settings for the ``find()``
 method, see the
-:node-api:`API documentation on find() <Collection.html#find>`.
+:node-api-4.0:`API documentation on find() </classes/collection.html#find>`.
 
 Skip
 ----
diff --git a/source/fundamentals/logging.txt b/source/fundamentals/logging.txt
@@ -222,4 +222,4 @@ The output of the example resembles the following:
    }
 
 For more information on the methods available on the ``Logger``, see the
-:node-api:`Logger API documentation <Logger.html>`.
+:node-api-4.0:`Logger API documentation </classes/logger.html>`.
diff --git a/source/fundamentals/promises.txt b/source/fundamentals/promises.txt
@@ -92,7 +92,7 @@ a ``catch()`` method to the end of a Promise chain.
 
    Certain methods in the driver such as ``find()`` return a ``Cursor``
    instead of a Promise. To determine what type each method returns, refer to
-   the :node-api:`Node.js API documentation <>`.
+   the :node-api-4.0:`Node.js API documentation <>`.
 
 Await
 ~~~~~
@@ -153,7 +153,7 @@ snippet:
    );
 
 For more information on the callback method signature for the specific
-driver method, see the :node-api:`API documentation <>`.
+driver method, see the :node-api-4.0:`API documentation <>`.
 
 .. note::
 
diff --git a/source/index.txt b/source/index.txt
@@ -13,7 +13,7 @@ MongoDB Node Driver
   /quick-start
   /fundamentals
   /usage-examples
-  API Documentation <http://mongodb.github.io/node-mongodb-native/3.6/api/>
+  API Documentation <https://mongodb.github.io/node-mongodb-native/4.0/>
   Release Notes <https://github.com/mongodb/node-mongodb-native/releases/>
   View the Source <https://github.com/mongodb/node-mongodb-native/>
   /faq
@@ -83,7 +83,7 @@ this section for users that are new to the MongoDB Node.js driver.
 
 API
 ---
-See the :node-api:`API documentation <>` if you are looking for
+See the :node-api-4.0:`API documentation <>` if you are looking for
 technical information about classes, methods, and configuration objects
 within the MongoDB Node.js driver.
 
diff --git a/source/usage-examples/bulkWrite.txt b/source/usage-examples/bulkWrite.txt
@@ -9,7 +9,7 @@ Perform Bulk Operations
    do not specify one, this method returns a ``Promise`` that resolves to
    the result object when it completes. See our guide on :doc:`Promises
    and Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <BulkWriteResult.html>` for information on
+   :node-api-4.0:`API documentation </classes/bulkwriteresult.html>` for information on
    the result object.
 
 The ``bulkWrite()`` method performs batch write operations against a
@@ -33,7 +33,7 @@ The ``bulkWrite()`` method accepts the following parameters:
 - ``operations``: specifies the bulk write operations to
   perform. Pass each operation to ``bulkWrite()`` as an object in
   an array. For examples that show the syntax for each write operation, see
-  the :node-api:`bulkWrite API documentation <Collection.html#bulkWrite>`.
+  the :node-api-4.0:`bulkWrite API documentation </classes/collection.html#bulkwrite>`.
 
 - ``options``: *optional* settings that affect the execution
   of the operation, such as whether the write operations should execute in
diff --git a/source/usage-examples/changeStream.txt b/source/usage-examples/changeStream.txt
@@ -25,7 +25,7 @@ In the example below, the ``$match`` stage will match all change event documents
 The ``watch()`` method accepts an ``options`` object as the second parameter. Refer to the links at the end of this
 section for more information on the settings you can configure with this object.
 
-The ``watch()`` method returns an instance of a :node-api:`ChangeStream </ChangeStream.html>`. You can read events from
+The ``watch()`` method returns an instance of a :node-api-4.0:`ChangeStream </classes/changestream.html>`. You can read events from
 change streams by iterating over them or listening for events. Select the tab that corresponds to the way you want to
 read events from the change stream below.
 
@@ -63,7 +63,7 @@ read events from the change stream below.
 
       You can control the change stream by calling ``pause()`` to stop emitting events or ``resume()`` to continue to emit events.
 
-      To stop processing change events, call the :node-api:`close() </ChangeStream.html#close>` method on the
+      To stop processing change events, call the :node-api-4.0:`close() </classes/changestream.html#close>` method on the
       ``ChangeStream`` instance. This closes the change stream and frees resources.
 
       .. code-block:: javascript
@@ -77,10 +77,10 @@ methods presented above:
 - :manual:`Change events </reference/change-events/>`
 - :manual:`Aggregation pipeline </reference/operator/aggregation-pipeline/>`
 - :manual:`Aggregation stages </changeStreams/#modify-change-stream-output>`
-- :node-api:`ChangeStream class API documentation </ChangeStream.html>`
-- :node-api:`Collection.watch() </Collection.html#watch>`,
-- :node-api:`Db.watch() </Db.html#watch>`,
-- :node-api:`MongoClient.watch() API documentation </MongoClient.html#watch>`
+- :node-api-4.0:`ChangeStream class API documentation </classes/changestream.html>`
+- :node-api-4.0:`Collection.watch() </classes/collection.html#watch>`,
+- :node-api-4.0:`Db.watch() </classes/db.html#watch>`,
+- :node-api-4.0:`MongoClient.watch() API documentation </classes/mongoclient.html#watch>`
 
 .. note::
 
diff --git a/source/usage-examples/command.txt b/source/usage-examples/command.txt
@@ -9,11 +9,11 @@ Run a Command
    not specify one, this method returns a ``Promise`` that resolves to the
    result object when it completes. See our guide on :doc:`Promises and
    Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Db.html#~resultCallback>` for
+   :node-api-4.0:`API documentation </classes/db.html#~resultcallback>` for
    information on the result object.
 
-You can run all raw database operations using the :node-api:`db.command()
-<Db.html#~command>` method. Call the ``command()`` method with
+You can run all raw database operations using the
+:node-api-4.0:`db.command() </classes/db.html#~command>` method. Call the ``command()`` method with
 your command object on an instance of a database for diagnostic and
 administrative tasks such as fetching server stats or initializing a replica
 set.
@@ -25,8 +25,8 @@ set.
 You can specify additional options in the ``options`` object passed in
 the second parameter of the ``command()`` method. For more information
 on the options you can pass, see the
-:node-api:`db.command() API documentation <Db.html#~command>`. You can
-also pass a :node-api:`callback method <Admin.html#~resultCallback>` as an
+:node-api-4.0:`db.command() API documentation </classes/db.html#~command>`. You can
+also pass a :node-api-4.0:`callback method </classes/admin.html#~resultcallback>` as an
 optional third parameter.
 
 Example
diff --git a/source/usage-examples/count.txt b/source/usage-examples/count.txt
@@ -10,20 +10,18 @@ Count Documents
    this method returns a ``Promise`` that resolves to the result object
    when it completes. See our guide on :doc:`Promises and Callbacks
    </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Collection.html#~countCallback>` for
+   :node-api-4.0:`API documentation </classes/collection.html#~countcallback>` for
    information on the result object.
 
 The Node.js driver provides two methods for counting documents in a
 collection:
 
-- :node-api:`collection.countDocuments()
-  <Collection.html#countDocuments>` returns the number of documents in
+- :node-api-4.0:`collection.countDocuments() </classes/collection.html#countdocuments>` returns the number of documents in
   the collection that match the specified query. If you specify an empty
   query document, ``countDocuments()`` returns the total number of
   documents in the collection.
 
-- :node-api:`collection.estimatedDocumentCount()
-  <Collection.html#estimatedDocumentCount>` returns an
+- :node-api-4.0:`collection.estimatedDocumentCount() </classes/collection.html#estimateddocumentcount>` returns an
   **estimation** of the number of documents in the collection based on
   collection metadata.
 
diff --git a/source/usage-examples/deleteMany.txt b/source/usage-examples/deleteMany.txt
@@ -9,24 +9,24 @@ Delete Multiple Documents
    do not specify one, this method returns a ``Promise`` that resolves to the
    result object when it completes. See our guide on :doc:`Promises and
    Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Collection.html#~deleteWriteOpResult>` for
+   :node-api-4.0:`API documentation </classes/collection.html#~deletewriteopresult>` for
    information on the result object.
 
 You can delete several documents in a collection at once using the
-:node-api:`collection.deleteMany() <Collection.html#deleteMany>` method.
+:node-api-4.0:`collection.deleteMany() </classes/collection.html#deletemany>` method.
 Pass a query document to the ``deleteMany()`` method to specify a subset
 of documents in the collection to delete. If you do not provide a query
 document (or if you provide an empty document), MongoDB matches all documents
 in the collection and deletes them. While you can use ``deleteMany()``
 to delete all documents in a collection, consider using
-:node-api:`drop() <Collection.html#drop>` instead for better performance
+:node-api-4.0:`drop() </classes/collection.html#drop>` instead for better performance
 and clearer code.
 
 You can specify additional options in the ``options`` object passed in
 the second parameter of the ``deleteMany()`` method. You can also pass a
 callback method as the optional third parameter. For more detailed 
 information, see the 
-:node-api:`deleteMany() API documentation <Collection.html#deleteMany>`.
+:node-api-4.0:`deleteMany() API documentation </classes/collection.html#deletemany>`.
 
 Example
 -------
diff --git a/source/usage-examples/deleteOne.txt b/source/usage-examples/deleteOne.txt
@@ -9,7 +9,7 @@ Delete a Document
    do not specify one, this method returns a ``Promise`` that resolves to the
    result object when it completes. See our guide on :doc:`Promises and
    Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Collection.html#~deleteWriteOpResult>` for
+   :node-api-4.0:`API documentation </classes/collection.html#~deletewriteopresult>` for
    information on the result object.
 
 You can delete a single document in a collection with
@@ -23,17 +23,16 @@ deletes the first match.
 You can specify additional query options using the
 ``options`` object passed as the second parameter of the
 ``deleteOne`` method. You can also pass a
-:node-api:`callback method <Collection.html#~deleteWriteOpCallback>`
+:node-api-4.0:`callback method </classes/collection.html#~deletewriteopcallback>`
 as an optional third parameter. For more information on this method,
 see the
-:node-api:`deleteOne() API documentation <Collection.html#deleteOne>`.
+:node-api-4.0:`deleteOne() API documentation </classes/collection.html#deleteone>`.
 
 .. note::
 
   If your application requires the deleted document after deletion,
   consider using the
-  :node-api:`collection.findOneAndDelete()
-  <Collection.html#findOneAndDelete>`.
+  :node-api-4.0:`collection.findOneAndDelete() </classes/collection.html#findoneanddelete>`.
   method, which has a similar interface to ``deleteOne()`` but also
   returns the deleted document.
 
diff --git a/source/usage-examples/distinct.txt b/source/usage-examples/distinct.txt
@@ -9,12 +9,13 @@ Retrieve Distinct Values of a Field
    not specify one, this method returns a ``Promise`` that resolves to the
    result object when it completes. See our guide on :doc:`Promises and
    Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Collection.html#~resultCallback>` for
+   :node-api-4.0:`API documentation </classes/collection.html#~resultcallback>` for
    information on the result object.
 
 You can retrieve a list of distinct values for a field across a
-collection by using the :node-api:`collection.distinct()
-<Collection.html#distinct>` method. Call the ``distinct()`` method
+collection by using the 
+:node-api-4.0:`collection.distinct() </classes/collection.html#distinct>` 
+method. Call the ``distinct()`` method
 on a ``Collection`` object with a document field name parameter as a
 ``String`` to produce a list that contains one of each of the different
 values found in the specified document field as shown below:
@@ -35,8 +36,8 @@ a method call to the ``wins`` field in the ``awards`` subdocument:
 
 You can specify additional query options using the ``options`` object passed
 as the third parameter to the ``distinct()`` method. For details on the
-query parameters, see the :node-api:`distinct() method in the API
-documentation <Collection.html#distinct>`.
+query parameters, see the 
+:node-api-4.0:`distinct() method in the API documentation </classes/collection.html#distinct>`.
 
 If you specify a value for the document field name that is not of type
 ``String`` such as a ``Document``, ``Array``, ``Number``, or ``null``,
diff --git a/source/usage-examples/find.txt b/source/usage-examples/find.txt
@@ -18,10 +18,10 @@ and
 :doc:`projection </fundamentals/crud/read-operations/project>`
 to configure the result set. You can specify these in the options
 parameter in your ``find()`` method call in ``sort`` and ``projection``
-objects. See :node-api:`collection.find() <Collection.html#find>` for more
+objects. See :node-api-4.0:`collection.find() </classes/collection.html#find>` for more
 information on the parameters you can pass to the method.
 
-The ``find()`` method returns a :node-api:`Cursor <Cursor.html>` that
+The ``find()`` method returns a :node-api-4.0:`FindCursor </classes/findcursor.html>` that
 manages the results of your query. You can iterate through the matching
 documents using one of the following :ref:`cursor methods <cursor-methods>`:
 
diff --git a/source/usage-examples/findOne.txt b/source/usage-examples/findOne.txt
@@ -9,7 +9,7 @@ Find a Document
    not specify one, this method returns a ``Promise`` that resolves to the
    result object when it completes. See our guide on :doc:`Promises and
    Callbacks </fundamentals/promises>` for more information, or the
-   :node-api:`API documentation <Collection.html#~resultCallback>` for
+   :node-api-4.0:`API documentation </classes/collection.html#~resultcallback>` for
    information on the result object.
 
 You can query for a single document in a collection with the
@@ -27,7 +27,7 @@ and :doc:`projection </fundamentals/crud/read-operations/project>`
 to configure the returned document. You can specify the additional options
 in the ``options`` object passed as the second parameter of the
 ``findOne`` method. For detailed reference documentation, see
-:node-api:`collection.findOne() <Collection.html#findOne>`.
+:node-api-4.0:`collection.findOne() </classes/collection.html#findone>`.
 
 Example
 -------
diff --git a/source/usage-examples/insertMany.txt b/source/usage-examples/insertMany.txt
diff --git a/source/usage-examples/insertOne.txt b/source/usage-examples/insertOne.txt
diff --git a/source/usage-examples/replaceOne.txt b/source/usage-examples/replaceOne.txt
diff --git a/source/usage-examples/updateMany.txt b/source/usage-examples/updateMany.txt
diff --git a/source/usage-examples/updateOne.txt b/source/usage-examples/updateOne.txt
diff --git a/source/whats-new.txt b/source/whats-new.txt

Original file line number	Diff line number	Diff line change
`@@ -313,5 +313,4 @@ URI to specify the behavior of the client.`
`313`	`313`
`314`	`314`
`315`	`315`
`316`		-For a complete list of options, see the :node-api:`MongoClient
`317`		-<MongoClient.html>` API reference page.
	`316`	+For a complete list of options, see the :node-api-4.0:`MongoClient </classes/mongoclient.html>` API reference page.
Original file line number	Diff line number	Diff line change
`@@ -222,4 +222,4 @@ The output of the example resembles the following:`
`222`	`222`	`}`
`223`	`223`
`224`	`224`	For more information on the methods available on the ``Logger``, see the
`225`		-:node-api:`Logger API documentation <Logger.html>`.
	`225`	+:node-api-4.0:`Logger API documentation </classes/logger.html>`.