DOCSP-10080: Replace NodeJS with Node.js (#89)

* DOCSP-10080: Replace NodeJS with Node.js

Author: Chris Cho

snooty.toml

@@ -1,5 +1,5 @@
 name = "node"
-title = "NodeJS"
+title = "Node.js"
 
 toc_landing_pages = ["/fundamentals/authentication", "/fundamentals/crud", "/usage-examples"]
 

source/faq.txt

@@ -42,7 +42,8 @@ How Can I Prevent the Driver From Hanging During Connection or From Spending Too
 To prevent the driver from hanging during connection or to prevent the
 driver from spending too long trying to reach unreachable replica sets,
 you can set the ``connectTimeoutMS`` option of your
-``connection-settings``. Generally, you should ensure that the
+:doc:`connection options </fundamentals/connection#connection-options>`. 
+Generally, you should ensure that the
 ``connectTimeoutMS`` setting is not lower than the longest network
 latency you have to a member of the set. If one of the secondary members
 is on the other side of the planet and has a latency of 10000
@@ -171,7 +172,7 @@ How Can I Prevent a Slow Operation From Delaying Other Operations?
 
 A slow operation may delay your other operations that occur after it, if
 the ``poolSize`` has not been set in the
-:doc:`Connection Options </fundamentals/connection#connection-options>`
+:doc:`connection options </fundamentals/connection#connection-options>`.
 MongoDB is synchronous and uses a single execution thread per socket,
 meaning that MongoDB will execute one single operation per socket at any
 point in time. Any other operation sent to that socket will have to wait

source/fundamentals/authentication.txt

@@ -36,4 +36,4 @@ Enterprise Edition which includes:
 .. note::
    For instructions on MongoDB driver installation and deployment setup, see
    our :guides:`Connect to MongoDB guide </server/drivers/>`. Select your
-   MongoDB deployment type and the NodeJS client.
+   MongoDB deployment type and the Node.js client.

source/fundamentals/connection.txt

@@ -10,15 +10,15 @@ Connection URI
 --------------
 
 The **connection URI** is the set of instructions that the driver uses to
-connect to a MongoDB deployment. It instructs the driver on how it should 
-connect to MongoDB and how it should behave while connected. The following 
+connect to a MongoDB deployment. It instructs the driver on how it should
+connect to MongoDB and how it should behave while connected. The following
 example shows each part of the connection URI:
 
 .. figure:: /includes/figures/connection_string_parts.png
 
 
 In this example, for the protocol, we use ``mongodb+srv`` which specifies the
-:manual:`DNS Seedlist Connection Format 
+:manual:`DNS Seedlist Connection Format
 </reference/connection-string/#dns-seedlist-connection-format>`. This indicates
 that the hostname following it corresponds to the DNS SRV record of your
 MongoDB instance or deployment. If your instance or deployment does not have a
@@ -44,8 +44,8 @@ your MongoDB instance.
 
 The last part of the connection string contains connection and authentication
 options as parameters. In the example above, we set two connection options:
-``poolSize=20`` and ``w=majority``. 
-For more information on connection options, skip to the :ref:`Connection Options` section.
+``poolSize=20`` and ``w=majority``. For more information on connection
+options, skip to the :ref:`connection-options` section.
 
 The code below shows how you can use the sample connection URI in a client to
 connect to MongoDB.
@@ -64,7 +64,7 @@ redundancy and high data availability.
 
 To connect to a replica set deployment, specify the hostname and port numbers
 of each instance, separated by a comma, and the replica set name as the value
-of the ``replicaSet`` parameter in the connection string. 
+of the ``replicaSet`` parameter in the connection string.
 
 .. code-block:: none
 
@@ -76,6 +76,8 @@ of the ``replicaSet`` parameter in the connection string.
    providing only a single host, you should provide the driver with the
    full list to ensure that it is able to connect even if one host fails.
 
+.. _connection-options:
+
 ------------------
 Connection Options
 ------------------

source/fundamentals/indexes.txt

@@ -137,7 +137,7 @@ MongoDB supports queries of geospatial coordinate data using :manual:`2dsphere <
 .. seealso::
 
    The :doc:`/fundamentals/crud/read-operations/geo` guide for an
-   overview of working with geospatial data with MongoDB and |node|.
+   overview of working with geospatial data with MongoDB and Node.js.
 
 To create a ``2dsphere`` index, the field you are indexing must be a :manual:`GeoJSON object </reference/geojson>`. The ``location.geo`` field in following sample document from the ``theaters`` collection in the ``sample_mflix`` database is a GeoJSON point object that describes the coordinates of the specified theater:
 

source/fundamentals/promises.txt

@@ -155,7 +155,7 @@ snippet:
 For more information on the callback method signature for the specific
 driver method, see the :node-api:`API documentation <>`.
 
- .. note::
+.. note::
 
     If you specify a callback, the method *does not* return a Promise.
 

source/usage-examples/command.txt

@@ -20,7 +20,7 @@ set.
 
 .. note::
     Use the :manual:`mongo shell </reference/mongo-shell>` for
-    administrative tasks instead of the NodeJS driver whenever possible.
+    administrative tasks instead of the Node.js driver whenever possible.
 
 You can specify additional options in the ``options`` object passed in
 the second parameter of the ``deleteMany()`` method. For more information