[Node] Capitalize Server throughout repo (#833)

rachel-mack · web-flow · commit 3544d777c390 · 2023-11-29T08:07:16.000-05:00
* capitalize Server in reference to the 'Server manual' and 'MongoDB Server'
diff --git a/.gitignore b/.gitignore
@@ -8,3 +8,5 @@ giza.log
 .vscode*
 *.swp
 *.code-workspace
+package.json
+package-lock.json
diff --git a/source/connection-troubleshooting.txt b/source/connection-troubleshooting.txt
@@ -318,7 +318,7 @@ takes too long attempting to reach unreachable replica set nodes. You can limit
 time the driver spends attempting to establish the connection by using the
 ``connectTimeMS`` setting. To learn more about this setting, see the
 :manual:`Timeout Options </reference/connection-string/#timeout-options>` in
-the server manual.
+the Server manual.
 
 You should ensure the ``connectTimeoutMS`` setting is not lower than
 the highest network latency you have to a member of the set. If one of the
diff --git a/source/faq.txt b/source/faq.txt
@@ -119,13 +119,13 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
      - ``connectTimeoutMS`` is a :ref:`connection option
        <node-connection-options>` that sets the time, in milliseconds,
        for an individual connection from your connection pool to
-       establish a TCP connection to the MongoDB server before
+       establish a TCP connection to the {+mdb-server+} before
        timing out.
 
        .. tip::
 
           To modify the allowed time for `MongoClient.connect <{+api+}/classes/MongoClient.html#connect>`__ to establish a
-          connection to a MongoDB server, use the ``serverSelectionTimeoutMS`` option instead.
+          connection to a {+mdb-server+}, use the ``serverSelectionTimeoutMS`` option instead.
 
        **Default:** 30000
    * - **socketTimeoutMS**
diff --git a/source/fundamentals/connection/connect.txt b/source/fundamentals/connection/connect.txt
@@ -103,11 +103,11 @@ API feature, see the :ref:`{+stable-api+} page <nodejs-stable-api>`.
 Other Ways to Connect to MongoDB
 --------------------------------
 
-If you are connecting to a single MongoDB server instance or replica set
+If you are connecting to a single {+mdb-server+} instance or replica set
 that is not hosted on Atlas, see the following sections to find out how to
 connect.
 
-Connect to a MongoDB Server on Your Local Machine
+Connect to a {+mdb-server+} on Your Local Machine
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 .. include:: /includes/localhost-connection.rst
diff --git a/source/fundamentals/crud/read-operations/cursor.txt b/source/fundamentals/crud/read-operations/cursor.txt
@@ -159,7 +159,7 @@ Cursors consume memory and network resources both in the client
 application and in the connected instance of MongoDB. Use
 `close() <{+api+}/classes/FindCursor.html#close>`__
 to free up a cursor's resources in both the client application
-and the MongoDB server:
+and the {+mdb-server+}:
 
 .. literalinclude:: /code-snippets/crud/cursor.js
    :language: javascript
diff --git a/source/fundamentals/crud/read-operations/geo.txt b/source/fundamentals/crud/read-operations/geo.txt
@@ -93,7 +93,7 @@ the field on the collection. The following snippet creates an index on the
    db.shipwrecks({coordinates: "2d"});
 
 See the
-:manual:`MongoDB server manual page on legacy coordinate pairs </geospatial-queries/#legacy-coordinate-pairs>`
+:manual:`{+mdb-server+} manual page on legacy coordinate pairs </geospatial-queries/#legacy-coordinate-pairs>`
 for more information.
 
 .. note::
@@ -142,5 +142,5 @@ England area:
    :start-after: start range geo example
    :end-before: end range geo example
 
-See the :manual:`MongoDB server manual page on geospatial query operators </geospatial-queries/index.html>`
+See the :manual:`{+mdb-server+} manual page on geospatial query operators </geospatial-queries/index.html>`
 for more information on the operators you can use in your query.
diff --git a/source/fundamentals/crud/read-operations/retrieve.txt b/source/fundamentals/crud/read-operations/retrieve.txt
@@ -173,7 +173,7 @@ group, and arrange the result data from a collection.
         { _id: 'created', count: 9 }
       ]
 
-See the MongoDB server manual pages on :manual:`aggregation </aggregation>`
+See the {+mdb-server+} manual pages on :manual:`aggregation </aggregation>`
 for more information on how to construct an aggregation pipeline.
 
 .. _node-fundamentals-watch:
diff --git a/source/fundamentals/crud/write-operations/insert.txt b/source/fundamentals/crud/write-operations/insert.txt
@@ -69,7 +69,7 @@ you let the driver automatically generate ``_id`` values.
    Duplicate ``_id`` values violate unique index constraints, resulting
    in a ``WriteError``.
 
-For additional information about ``_id``, see the Server Manual Entry on
+For more information about ``_id``, see the Server manual entry on
 :manual:`Unique Indexes </core/index-unique/>`.
 
 Insert a Single Document
@@ -111,7 +111,7 @@ section, see the following resources:
 
 - API Documentation on `insertOne() <{+api+}/classes/Collection.html#insertOne>`__
 - API Documentation on `InsertOneResult <{+api+}/interfaces/InsertOneResult.html>`__
-- Server Manual Entry on :manual:`insertOne() </reference/method/db.collection.insertOne/>`
+- Server manual entry on :manual:`insertOne() </reference/method/db.collection.insertOne/>`
 - Runnable :doc:`Insert a Document Example </usage-examples/insertOne>`
 
 Insert Multiple Documents
@@ -236,7 +236,7 @@ section, see the following resources:
 - API Documentation on `insertMany() <{+api+}/classes/Collection.html#insertMany>`__
 - API Documentation on `InsertManyResult <{+api+}/interfaces/InsertManyResult.html>`__
 - API Documentation on `PkFactory <{+api+}/interfaces/PkFactory.html>`__
-- Server Manual Entry on :manual:`insertMany() </reference/method/db.collection.insertMany/>`
+- Server manual entry on :manual:`insertMany() </reference/method/db.collection.insertMany/>`
 - Runnable :doc:`Insert Multiple Documents Example </usage-examples/insertMany>`
 
 .. _node-insert-instruqt-lab:
diff --git a/source/fundamentals/crud/write-operations/modify.txt b/source/fundamentals/crud/write-operations/modify.txt
@@ -67,7 +67,7 @@ update operators:
 - ``$unset``: removes fields
 - ``$mul``: multiplies a field value by a specified number
 
-See the MongoDB Server manual for a :manual:`complete list of update operators
+See the {+mdb-server+} manual for a :manual:`complete list of update operators
 and their usage </reference/operator/update-field/>`.
 
 The update operators apply only to the fields associated with them in your
@@ -134,7 +134,7 @@ attempts to perform an update, but if no documents are matched, inserts
 a new document with the specified fields and values.
 
 You cannot modify the ``_id`` field of a document nor change a field to
-a value that violates a unique index constraint. See the MongoDB Server manual
+a value that violates a unique index constraint. See the {+mdb-server+} manual
 for more information on :manual:`unique indexes </core/index-unique/>`.
 
 .. _node-fundamentals-replaceone:
@@ -215,7 +215,7 @@ attempts to perform the replacement, but if no documents are matched, it
 inserts a new document with the specified fields and values.
 
 You cannot modify the ``_id`` field of a document nor change a field to
-a value that violates a unique index constraint. See the MongoDB Server manual
+a value that violates a unique index constraint. See the {+mdb-server+} manual
 for more information on :manual:`unique indexes </core/index-unique/>`.
 
 .. _node-update-instruqt-lab:
diff --git a/source/fundamentals/gridfs.txt b/source/fundamentals/gridfs.txt
@@ -29,7 +29,7 @@ the file storage.
 
 You should use GridFS if the size of your file exceeds the BSON-document
 size limit of 16 megabytes. For more detailed information on whether GridFS is
-suitable for your use case, see the :manual:`GridFS server manual page </core/gridfs>`.
+suitable for your use case, see the :manual:`GridFS Server manual page </core/gridfs>`.
 
 Navigate the following sections to learn more about GridFS operations
 and implementation:
@@ -60,7 +60,7 @@ collection to ensure efficient retrieval of files and related
 metadata. The driver only creates the GridFS bucket on the first write
 operation if it does not already exist. The driver only creates indexes if
 they do not exist and when the bucket is empty. For more information on
-GridFS indexes, see the server manual page on :manual:`GridFS Indexes </core/gridfs/#gridfs-indexes>`.
+GridFS indexes, see the Server manual page on :manual:`GridFS Indexes </core/gridfs/#gridfs-indexes>`.
 
 When storing files with GridFS, the driver splits the files into smaller
 pieces, each represented by a separate document in the ``chunks`` collection.
diff --git a/source/fundamentals/indexes.txt b/source/fundamentals/indexes.txt
@@ -62,7 +62,7 @@ when a write operation updates an indexed field, MongoDB also has to update
 the related index.
 
 For more information on designing your data model and choosing indexes
-appropriate for your application, see the MongoDB server documentation on
+appropriate for your application, see the {+mdb-server+} documentation on
 :manual:`Indexing Strategies </applications/indexes>` and
 :manual:`Data Modeling and Indexes </core/data-model-operations/#data-model-indexes>`.
 
@@ -179,7 +179,7 @@ Multikey indexes behave differently from non-multikey indexes in terms of
 query coverage, index bound computation, and sort behavior. For a full
 explanation of multikey indexes, including a discussion of their behavior
 and limitations, refer to the :manual:`Multikey Indexes page
-</core/index-multikey>` in the MongoDB Server manual.
+</core/index-multikey>` in the {+mdb-server+} manual.
 
 Clustered Indexes
 ~~~~~~~~~~~~~~~~~
@@ -263,7 +263,7 @@ geospatial data with the MongoDB Node.js driver, read our
 
 To create a 2dsphere index, you must specify a field that contains
 only **GeoJSON objects**. For more details on this type, see the MongoDB
-server manual page on :manual:`GeoJSON objects </reference/geojson>`.
+Server manual page on :manual:`GeoJSON objects </reference/geojson>`.
 
 The ``location.geo`` field in following sample document from the
 ``theaters`` collection in the ``sample_mflix`` database is a GeoJSON Point
diff --git a/source/fundamentals/stable-api.txt b/source/fundamentals/stable-api.txt
@@ -19,7 +19,7 @@
 
 .. note::
 
-   The {+stable-api+} feature requires MongoDB Server 5.0 or later.
+   The {+stable-api+} feature requires {+mdb-server+} 5.0 or later.
 
    Use the {+stable-api+} feature only if all the MongoDB
    servers you are connecting to support this feature.
@@ -82,9 +82,9 @@ following operations:
 
 .. warning::
 
-   If you specify an API version and connect to a MongoDB server that does
+   If you specify an API version and connect to a {+mdb-server+} that does
    not support the {+stable-api+}, your application may throw an error when
-   connecting to your MongoDB server with the following text:
+   connecting to your {+mdb-server+} with the following text:
 
    .. code-block:: none
       :copyable: false
diff --git a/source/fundamentals/transactions.txt b/source/fundamentals/transactions.txt
@@ -40,7 +40,7 @@ ACID transactions </basics/acid-transactions>`.
 .. note::
 
    To execute a multi-document transaction, you must be connected to a
-   deployment running MongoDB Server version 4.0 or later.
+   deployment running {+mdb-server+} version 4.0 or later.
 
    For a detailed list of limitations, see the :manual:`Transactions and
    Operations </core/transactions/#transactions-and-operations>` section in
@@ -90,9 +90,9 @@ raises certain error types. To learn more about this behavior, see the
 
 .. important::
    
-   When you connect to MongoDB Server version 4.2 or
+   When you connect to {+mdb-server+} version 4.2 or
    earlier, you can perform write operations in a transaction only on
-   collections that already exist. When you connect to MongoDB Server
+   collections that already exist. When you connect to {+mdb-server+}
    version 4.4 and later, the server automatically creates collections
    as necessary when you perform write operations in a transaction. To
    learn more about this behavior, see :manual:`Create Collections and
diff --git a/source/includes/localhost-connection.rst b/source/includes/localhost-connection.rst
@@ -3,22 +3,22 @@ steps:
 
 1. Download the `Community <https://www.mongodb.com/try/download/community>`__
    or `Enterprise <https://www.mongodb.com/try/download/enterprise>`__ version
-   of MongoDB Server.
+   of {+mdb-server+}.
 
-#. :manual:`Install and configure </installation/>` MongoDB Server.
+#. :manual:`Install and configure </installation/>` {+mdb-server+}.
 
 #. Start the server.
 
 .. important::
 
-   Always secure your MongoDB server from malicious attacks. See our
+   Always secure your {+mdb-server+} from malicious attacks. See our
    :manual:`Security Checklist </administration/security-checklist/>` for a
    list of security recommendations.
 
-After you successfully start your MongoDB server, specify your connection
+After you successfully start your {+mdb-server+}, specify your connection
 string in your driver connection code.
 
-If your MongoDB Server is running locally, you can use the following
+If your {+mdb-server+} is running locally, you can use the following
 connection string:
 
 .. code-block:: none
diff --git a/source/index.txt b/source/index.txt
@@ -103,7 +103,7 @@ Compatibility
 -------------
 
 For the compatibility tables that show the recommended {+driver-short+}
-version for each MongoDB Server version, see the
+version for each {+mdb-server+} version, see the
 :doc:`Compatibility </compatibility>` section.
 
 Upgrade Driver Versions
diff --git a/source/whats-new.txt b/source/whats-new.txt
@@ -589,7 +589,7 @@ What's New in 4.11
 Prioritization Order in Monitoring
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-When connecting to MongoDB Server version 6.0 or later, the driver prioritizes
+When connecting to {+mdb-server+} version 6.0 or later, the driver prioritizes
 ``electionId`` settings before ``setVersion`` settings during Server Discovery and
 Monitoring events. In previous versions, the prioritization order was reversed.
 

Original file line number	Diff line number	Diff line change
`@@ -173,7 +173,7 @@ group, and arrange the result data from a collection.`
`173`	`173`	`{ _id: 'created', count: 9 }`
`174`	`174`	`]`
`175`	`175`
`176`		-See the MongoDB server manual pages on :manual:`aggregation </aggregation>`
	`176`	+See the {+mdb-server+} manual pages on :manual:`aggregation </aggregation>`
`177`	`177`	`for more information on how to construct an aggregation pipeline.`
`178`	`178`
`179`	`179`	`.. _node-fundamentals-watch:`