mongodb · andf-mongodb · Apr 1, 2021 · Mar 31, 2021
diff --git a/source/administration/monitoring.txt b/source/administration/monitoring.txt
@@ -572,7 +572,7 @@ become primary.
 Once a :binary:`~bin.mongod` has terminated, it may not be possible to cleanly
 restart it on the *same* machine.
 
-.. topic:: Symlinks
+.. note:: Symlinks
 
    If any of its monitored directories is a symlink to other volumes, the
    Storage Node Watchdog does not monitor the symlink target.

diff --git a/source/core/backups.txt b/source/core/backups.txt
@@ -91,7 +91,7 @@ and the :opsmgr:`Ops Manager Manual </>`.
 Back Up by Copying Underlying Data Files
 ----------------------------------------
 
-.. topic:: Considerations for Encrypted Storage Engines using AES256-GCM 
+.. note:: Considerations for Encrypted Storage Engines using AES256-GCM 
 
    .. include:: /includes/fact-aes256-backups.rst
 

diff --git a/source/core/causal-consistency-read-write-concerns.txt b/source/core/causal-consistency-read-write-concerns.txt
@@ -136,7 +136,7 @@ the following causal consistency guarantees:
 
 |checkmark| Read own writes  |checkmark| Monotonic reads  |checkmark| Monotonic writes  |checkmark| Writes follow reads
 
-.. topic:: Scenario 1 (Read Concern "majority" and Write Concern "majority")
+.. note:: Scenario 1 (Read Concern "majority" and Write Concern "majority")
 
    During the transient period with two primaries, because only ``P``\
    :sub:`new` can fulfill writes with :writeconcern:`{ w: "majority" }
@@ -193,7 +193,7 @@ the following causal consistency guarantees:
           reflects a state of the data after Read\ :sub:`1` (i.e. an
           earlier state reflects the data read by Read\ :sub:`1`).
 
-.. topic:: Scenario 2 (Read Concern "majority" and Write Concern "majority")
+.. note:: Scenario 2 (Read Concern "majority" and Write Concern "majority")
 
    Consider an alternative sequence where Read\ :sub:`1` with read
    concern :readconcern:`"majority"` routes to ``S``\ :sub:`1`:
@@ -273,7 +273,7 @@ provides the following causal consistency guarantees *if causal consistency impl
 
 |checkmark| Read own writes  |checkmark| Monotonic reads  |checkmark| Monotonic writes  |checkmark| Writes follow reads
 
-.. topic:: Scenario 3 (Read Concern "majority" and Write Concern ``{w: 1}``)
+.. note:: Scenario 3 (Read Concern "majority" and Write Concern ``{w: 1}``)
 
    During the transient period with two primaries, because both ``P``\
    :sub:`old` and ``P``\ :sub:`new` can fulfill writes with
@@ -375,7 +375,7 @@ provides the following causal consistency guarantees *if causal consistency impl
           earlier state reflects the data read by Read\
           :sub:`1`).
 
-.. topic:: Scenario 4 (Read Concern "majority" and Write Concern ``{w: 1}``)
+.. note:: Scenario 4 (Read Concern "majority" and Write Concern ``{w: 1}``)
 
    Consider an alternative sequence where Read\ :sub:`1` with
    read concern :readconcern:`"majority"` routes to ``S``\ :sub:`1`:
@@ -482,7 +482,7 @@ cannot guarantee causal consistency.
 This combination may satisfy all four causal consistency guarantees in
 some situations, but not necessarily in all situations.
 
-.. topic:: Scenario 5 (Read Concern "local" and Write Concern ``{w: 1}``)
+.. note:: Scenario 5 (Read Concern "local" and Write Concern ``{w: 1}``)
 
    During this transient period, because both ``P``\ :sub:`old` and
    ``P``\ :sub:`new` can fulfill writes with :writeconcern:`{ w: 1 } <\<number\>>` write concern, a
@@ -553,7 +553,7 @@ the following causal consistency guarantees:
 This combination may satisfy all four causal consistency guarantees in
 some situations, but not necessarily in all situations.
 
-.. topic:: Scenario 6 (Read Concern "local" and Write Concern "majority")
+.. note:: Scenario 6 (Read Concern "local" and Write Concern "majority")
 
    During this transient period, because only ``P``\ :sub:`new` can
    fulfill writes with  :writeconcern:`{ w: "majority" } <"majority">` write concern, a client

diff --git a/source/core/data-model-operations.txt b/source/core/data-model-operations.txt
@@ -139,9 +139,9 @@ the following behaviors:
 
 - For each :term:`database`, a single namespace file (i.e.
   ``<database>.ns``) stores all meta-data for that database, and each
-  index and collection has its own entry in the namespace file. MongoDB
-  places :limit:`limits on the size of namespace files
-  <Size of Namespace File>`.
+  index and collection has its own entry in the namespace file. See
+  places :ref:`namespace length limits <limit-namespace-length>` for
+  specific limitations.
 
 .. _faq-developers-embed-documents:
 

diff --git a/source/core/index-multikey.txt b/source/core/index-multikey.txt
@@ -128,7 +128,6 @@ For an example, see :ref:`multikey-embedded-documents`.
 .. seealso::
 
    - :ref:`unique-separate-documents`
-
    - :ref:`index-unique-index`
 
 Sorting

diff --git a/source/core/index-single.txt b/source/core/index-single.txt
@@ -63,7 +63,7 @@ You can create indexes on fields within embedded documents, just as you
 can index top-level fields in documents. Indexes on embedded fields
 differ from :ref:`indexes on embedded documents <index-embedded-documents>`,
 which include the full content up to the maximum :limit:`index size
-<Index Key>` of the embedded document in the index. Instead, indexes on
+<Index Key Limit>` of the embedded document in the index. Instead, indexes on
 embedded fields allow you to use a "dot notation," to introspect into
 embedded documents.
 

diff --git a/source/core/replica-set-architecture-three-members.txt b/source/core/replica-set-architecture-three-members.txt
@@ -86,5 +86,4 @@ set will elect the secondary to be primary.
 
 .. seealso::
 
-   :doc:`/tutorial/deploy-replica-set`.
-
+   :doc:`/tutorial/deploy-replica-set`
diff --git a/source/core/retryable-writes.txt b/source/core/retryable-writes.txt
@@ -157,7 +157,7 @@ cannot be :writeconcern:`{w: 0} <\<number\>>`.
        any multi-document write operations, such as ``update`` which
        specifies ``true`` for the ``multi`` option.
 
-.. topic:: Updates to Shard Key Values
+.. note:: Updates to Shard Key Values
 
    Starting in MongoDB 4.2, you can update a document's shard key value
    (unless the shard key field is the immutable ``_id`` field) by

diff --git a/source/core/security-encryption-at-rest.txt b/source/core/security-encryption-at-rest.txt
@@ -49,7 +49,7 @@ Enterprise for Linux also supports authenticated encryption
 ``AES256-GCM`` (or 256-bit Advanced Encryption Standard in
 Galois/Counter Mode). FIPS mode encryption is also available.
 
-.. topic:: AES256-GCM and Filesystem Backups
+.. note:: AES256-GCM and Filesystem Backups
 
    .. include:: /includes/fact-aes256-backups.rst
 

diff --git a/source/core/sharding-balancer-administration.txt b/source/core/sharding-balancer-administration.txt
@@ -176,7 +176,7 @@ All chunk migrations use the following procedure:
 
    .. seealso::
 
-      :ref:`moveChunk-directory`.
+      :ref:`moveChunk-directory`
 
 The migration process ensures consistency and maximizes the availability of
 chunks during balancing.

diff --git a/source/core/sharding-shard-key.txt b/source/core/sharding-shard-key.txt
@@ -59,7 +59,7 @@ use the :binary:`~bin.mongo` shell method
 
        - ``"hashed"`` indicates :doc:`hashed sharding </core/hashed-sharding>`.
 
-.. topic:: Shard Key Fields and Values
+.. note:: Shard Key Fields and Values
 
    Existence
       Starting in version 4.4, documents in sharded collections can be
@@ -343,7 +343,7 @@ monotonically, consider using :doc:`/core/hashed-sharding`.
 Change a Document's Shard Key Value
 -----------------------------------
 
-.. topic:: When updating the shard key value
+.. note:: When updating the shard key value
 
    - You :red:`must` run on a :binary:`~bin.mongos`. Do :red:`not`
      issue the operation directly on the shard.

diff --git a/source/core/transactions-operations.txt b/source/core/transactions-operations.txt
@@ -36,7 +36,7 @@ The following read/write operations are allowed in transactions:
 
 .. include:: /includes/table-transactions-operations.rst
 
-.. topic:: Updates to Shard Key Values
+.. note:: Updates to Shard Key Values
 
    Starting in MongoDB 4.2, you can update a document's shard key value
    (unless the shard key field is the immutable ``_id`` field) by

diff --git a/source/core/transactions-production-consideration.txt b/source/core/transactions-production-consideration.txt
@@ -33,7 +33,7 @@ Availability
   sharded clusters), clients :red:`must` use MongoDB drivers updated for
   MongoDB 4.2.
 
-.. topic:: Distributed Transactions and Multi-Document Transactions
+.. note:: Distributed Transactions and Multi-Document Transactions
 
    Starting in MongoDB 4.2, the two terms are synonymous. Distributed
    transactions refer to multi-document transactions on sharded

diff --git a/source/core/transactions.txt b/source/core/transactions.txt
@@ -322,7 +322,7 @@ This example highlights the key components of the transactions API.
 Transactions and Atomicity
 --------------------------
 
-.. topic:: Distributed Transactions and Multi-Document Transactions
+.. note:: Distributed Transactions and Multi-Document Transactions
 
    Starting in MongoDB 4.2, the two terms are synonymous. Distributed
    transactions refer to multi-document transactions on sharded

diff --git a/source/includes/extracts-4.4-changes.yaml b/source/includes/extracts-4.4-changes.yaml
@@ -145,7 +145,7 @@ ref: 4.4-changes-projection-sort-meta-list
 content: |
 
    - Starting in MongoDB 4.4, you can specify the
-     :projection:`{ $meta: "textScore" } <$meta>` expression in the
+     :expression:`{ $meta: "textScore" } <$meta>` expression in the
      :method:`~cursor.sort()` without also specifying the expression in
      the projection. For example,
 
@@ -158,18 +158,20 @@ content: |
      As a result, you can sort the resulting documents by their search
      relevance without projecting the ``textScore``.
 
-     | In earlier versions, to include :projection:`{ $meta: "textScore" }
-       <$meta>` expression in the :method:`~cursor.sort()`, you must also
-       include the same expression in the projection.
+     | In earlier versions, to include
+       :expression:`{ $meta: "textScore" } <$meta>` expression in the
+       :method:`~cursor.sort()`, you must also include the same
+       expression in the projection.
 
-   - Starting in MongoDB 4.4, if you include the :projection:`{ $meta:
-     "textScore" } <$meta>` expression in both the :ref:`projection
-     <find-projection>` and :method:`~cursor.sort()`, the projection and
-     sort documents can have different field names for the expression.
+   - Starting in MongoDB 4.4, if you include the
+     :expression:`{ $meta: "textScore" } <$meta>` expression in both the
+     :ref:`projection <find-projection>` and :method:`~cursor.sort()`,
+     the projection and sort documents can have different field names
+     for the expression.
 
      | For example, in the following operation, the projection uses a
-      field named  ``score`` for the expression and the :method:`~cursor.sort()`
-      uses the field named ``ignoredName``.
+      field named  ``score`` for the expression and the
+      :method:`~cursor.sort()` uses the field named ``ignoredName``.
 
      .. code-block:: javascript 
 
@@ -188,7 +190,7 @@ content: |
 
    Starting in MongoDB 4.4, you must specify the :query:`$text` operator
    in the query predicate of the :method:`db.collection.find()` operations
-   to use :projection:`{ $meta: "textScore" } <$meta>` expression in the
+   to use :expression:`{ $meta: "textScore" } <$meta>` expression in the
    projection or sort. For example:
 
    .. code-block:: javascript

diff --git a/source/includes/fact-platform-s390x-enterprise.rst b/source/includes/fact-platform-s390x-enterprise.rst
@@ -1,4 +1,4 @@
-.. topic:: Platform Support EOL Notice
+.. note:: Platform Support EOL Notice
 
    .. list-table::
       :widths: 20 80

diff --git a/source/includes/fact-platform-support-amazon.rst b/source/includes/fact-platform-support-amazon.rst
@@ -1,4 +1,4 @@
-.. topic:: EOL Notice
+.. note:: EOL Notice
 
    - MongoDB 4.4 Community Edition removes support for Amazon Linux
      2013.03 on :ref:`x86_64 <prod-notes-supported-platforms-x86_64>`

diff --git a/source/includes/fact-platform-support-enterprise-amazon.rst b/source/includes/fact-platform-support-enterprise-amazon.rst
@@ -1,4 +1,4 @@
-.. topic:: EOL Notice
+.. note:: EOL Notice
 
    - MongoDB 4.4 Enterprise Edition removes support for Amazon Linux
      2013.03 on :ref:`x86_64 <prod-notes-supported-platforms-x86_64>`

diff --git a/source/includes/fact-platform-support-enterprise-red-hat.rst b/source/includes/fact-platform-support-enterprise-red-hat.rst
@@ -1,4 +1,4 @@
-.. topic:: EOL Notice
+.. note:: EOL Notice
 
    - MongoDB 4.4 Enterprise Edition removes support for
      :abbr:`RHEL (Red Hat Enterprise Linux)` / CentOS / Oracle 6

diff --git a/source/includes/fact-platform-support-enterprise-windows.rst b/source/includes/fact-platform-support-enterprise-windows.rst
@@ -1,4 +1,4 @@
-.. topic:: EOL Notice
+.. note:: EOL Notice
 
    - MongoDB 4.4 Enterprise Edition removes support for Windows 8.1 /
      Server 2012 R2

diff --git a/source/includes/fact-platform-support-windows.rst b/source/includes/fact-platform-support-windows.rst
@@ -1,4 +1,4 @@
-.. topic:: EOL Notice
+.. note:: EOL Notice
 
    - MongoDB 4.4 Community Edition removes support for Windows 8.1 /
      Server 2012 R2

diff --git a/source/includes/fact-platform-x86_64.rst b/source/includes/fact-platform-x86_64.rst
@@ -1,4 +1,4 @@
-.. topic:: Platform Support EOL Notice
+.. note:: Platform Support EOL Notice
 
    .. list-table::
       :widths: 40 60

diff --git a/source/includes/steps-4.4-upgrade-sharded-cluster.yaml b/source/includes/steps-4.4-upgrade-sharded-cluster.yaml
@@ -313,7 +313,7 @@ content: |
      during orphaned document cleanup, see
      :ref:`range-deletion-performance-tuning`.
 
-   .. topic:: Additional Consideration
+   .. note:: Additional Consideration
 
       .. include:: /includes/fact-mongos-fcv.rst
 

diff --git a/source/reference/command/collMod.txt b/source/reference/command/collMod.txt
@@ -157,9 +157,8 @@ Document Validation
    The ``validator`` option takes a document that specifies the
    validation rules or expressions. You can specify the expressions
    using the same operators as the :ref:`query operators
-   <query-selectors>` with the exception of : :query:`$geoNear`,
-   :query:`$near`, :query:`$nearSphere`, :query:`$text`, and
-   :query:`$where`.
+   <query-selectors>` with the exception of :query:`$near`,
+   :query:`$nearSphere`, :query:`$text`, and :query:`$where`.
 
    .. note::
 

diff --git a/source/reference/command/create.txt b/source/reference/command/create.txt
@@ -159,8 +159,8 @@ Definition
           The ``validator`` option takes a document that specifies the
           validation rules or expressions. You can specify the expressions using
           the same operators as the :ref:`query operators <query-selectors>`
-          with the exception of :query:`$geoNear`, :query:`$near`,
-          :query:`$nearSphere`, :query:`$text`, and :query:`$where`.
+          with the exception of :query:`$near`, :query:`$nearSphere`,
+          :query:`$text`, and :query:`$where`.
 
           .. note::
 

diff --git a/source/reference/command/refineCollectionShardKey.txt b/source/reference/command/refineCollectionShardKey.txt
@@ -25,7 +25,7 @@ Definition
    where the existing key has led to :ref:`jumbo (i.e. indivisible)
    chunks <jumbo-chunks>` due to insufficient cardinality.
 
-.. topic:: Data Distribution
+.. note:: Data Distribution
 
    As part of refining the shard key, the
    :dbcommand:`refineCollectionShardKey` command updates the

diff --git a/source/reference/command/serverStatus.txt b/source/reference/command/serverStatus.txt
@@ -1633,20 +1633,20 @@ opWriteConcernCounters
 
       * - ``"wmajority"``
 
-        - Number of insert operations that specified :writeconcern:`w:
-          "majority" <"majority">`.
+        - Number of insert operations that specified
+          :writeconcern:`w: "majority" <"majority">`.
 
       * - ``"wnum"``
 
-        - Number of insert operations that specified :writeconcern:`w:
-          \<num\> <\<number\>>`. The counts are grouped by the specific
-          ``<num>``.
+        - Number of insert operations that specified
+          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
+          grouped by the specific``<num>``.
 
       * - ``"wtag"``
 
-        - Number of insert operations that specified :writeconcern:`w:
-          \<tag\> <\<tag set\>>`. The counts are grouped by the
-          specific ``<tag>``.
+        - Number of insert operations that specified
+          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
+          The counts are grouped by the specific ``<tag>``.
 
       * - ``"none"``
 
@@ -1691,20 +1691,20 @@ opWriteConcernCounters
 
       * - ``"wmajority"``
 
-        - Number of update operations that specified :writeconcern:`w:
-          "majority" <"majority">`.
+        - Number of update operations that specified
+          :writeconcern:`w: "majority" <"majority">`.
 
       * - ``"wnum"``
 
-        - Number of update operations that specified :writeconcern:`w:
-          \<num\> <\<number\>>`. The counts are grouped by the
-          specific ``<num>``.
+        - Number of update operations that specified
+          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
+          grouped by the specific ``<num>``.
 
       * - ``"wtag"``
 
-        - Number of update operations that specified :writeconcern:`w:
-          \<tag\> <\<tag set\>>`. The counts are grouped by the specific
-          ``<tag>``.
+        - Number of update operations that specified
+          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
+          The counts are grouped by the specific ``<tag>``.
 
       * - ``"none"``
 
@@ -1750,20 +1750,20 @@ opWriteConcernCounters
 
       * - ``"wmajority"``
 
-        - Number of delete operations that specified :writeconcern:`w:
-          "majority" <"majority">`.
+        - Number of delete operations that specified
+          :writeconcern:`w: "majority" <"majority">`.
 
       * - ``"wnum"``
 
-        - Number of delete operations that specified :writeconcern:`w:
-          \<num\> <\<number\>>`. The counts are grouped by the specific
-          ``<num>``.
+        - Number of delete operations that specified
+          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
+          grouped by the specific ``<num>``.
 
       * - ``"wtag"``
 
-        - Number of delete operations that specified :writeconcern:`w:
-          \<tag\> <\<tag set\>>`. The counts are grouped by the
-          specific ``<tag>``.
+        - Number of delete operations that specified
+          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
+          The counts are grouped by the specific ``<tag>``.
 
       * - ``"none"``
-Original file line number
+Diff line change
@@ Expand Up / @@ -128,7 +128,6 @@ For an example, see :ref:`multikey-embedded-documents`. @@
     .. seealso::
        - :ref:`unique-separate-documents`
        - :ref:`index-unique-index`
     Sorting
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -86,5 +86,4 @@ set will elect the secondary to be primary.

		.. seealso::

		:doc:`/tutorial/deploy-replica-set`.

		:doc:`/tutorial/deploy-replica-set`