diff --git a/source/administration/monitoring.txt b/source/administration/monitoring.txt index 7740676ff55..6d9189d3ea0 100644 --- 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 index 143430147dd..22040ce7384 100644 --- 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 index 41db209c6e1..b67d3686691 100644 --- 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 } <\>` 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 index ff0bd9a8cb2..cb492846160 100644 --- 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. ``.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 - `. + index and collection has its own entry in the namespace file. See + places :ref:`namespace length limits ` for + specific limitations. .. _faq-developers-embed-documents: diff --git a/source/core/index-multikey.txt b/source/core/index-multikey.txt index 4f2c9a2afd2..3051b1c11ca 100644 --- 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 index 929865d9082..5b9f3673ef6 100644 --- 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 `, which include the full content up to the maximum :limit:`index size -` of the embedded document in the index. Instead, indexes on +` 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 index 17741b118cd..121ab446547 100644 --- 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 index 5e9704d68ca..597deb5b20d 100644 --- a/source/core/retryable-writes.txt +++ b/source/core/retryable-writes.txt @@ -157,7 +157,7 @@ cannot be :writeconcern:`{w: 0} <\>`. 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 index a6f9fc1b286..5352251e360 100644 --- 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 index 3bafe94ea4d..9fa3fe6dde5 100644 --- 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 index e8716f54198..9a3da6d71f0 100644 --- 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 `. -.. 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 index c3a480a693b..cad48c6bf28 100644 --- 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 index 1ca661d14ee..1c2a13d924c 100644 --- 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 index 9af69526355..b83cd719267 100644 --- 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 index acfbd80600a..042bacccb30 100644 --- 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 - ` 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 ` 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 index dd3f5168425..55e23dbbfe1 100644 --- 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 index a8d5156d62e..41c6ede3cf1 100644 --- 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 ` diff --git a/source/includes/fact-platform-support-enterprise-amazon.rst b/source/includes/fact-platform-support-enterprise-amazon.rst index 0b64407466e..645d2e55ea0 100644 --- 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 ` diff --git a/source/includes/fact-platform-support-enterprise-red-hat.rst b/source/includes/fact-platform-support-enterprise-red-hat.rst index 8b1dcfd04d0..5d6a0adf768 100644 --- 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 index 54ce7b71675..8eec79e3ba1 100644 --- 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 index ac6965369c2..30ba3dfea04 100644 --- 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 index 9640b8821bd..96a7f637956 100644 --- 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 index ce24ac654fb..320e81bdd2e 100644 --- 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 index 773d5f3e8c4..aaab40f9547 100644 --- 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 - ` 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/create.txt b/source/reference/command/create.txt index 9c766a4fdc3..994d503b605 100644 --- 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 ` - 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 index 0c363a2e872..e5c8c1a042b 100644 --- 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 ` 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 index 6be1ae88389..a9f3926e42c 100644 --- 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: - \ <\>`. The counts are grouped by the specific - ````. + - Number of insert operations that specified + :writeconcern:`w: \ <\>`. The counts are + grouped by the specific````. * - ``"wtag"`` - - Number of insert operations that specified :writeconcern:`w: - \ <\>`. The counts are grouped by the - specific ````. + - Number of insert operations that specified + :writeconcern:`w: \ <\>`. + The counts are grouped by the specific ````. * - ``"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: - \ <\>`. The counts are grouped by the - specific ````. + - Number of update operations that specified + :writeconcern:`w: \ <\>`. The counts are + grouped by the specific ````. * - ``"wtag"`` - - Number of update operations that specified :writeconcern:`w: - \ <\>`. The counts are grouped by the specific - ````. + - Number of update operations that specified + :writeconcern:`w: \ <\>`. + The counts are grouped by the specific ````. * - ``"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: - \ <\>`. The counts are grouped by the specific - ````. + - Number of delete operations that specified + :writeconcern:`w: \ <\>`. The counts are + grouped by the specific ````. * - ``"wtag"`` - - Number of delete operations that specified :writeconcern:`w: - \ <\>`. The counts are grouped by the - specific ````. + - Number of delete operations that specified + :writeconcern:`w: \ <\>`. + The counts are grouped by the specific ````. * - ``"none"`` diff --git a/source/reference/configuration-options.txt b/source/reference/configuration-options.txt index 97faedd4506..051df16947d 100644 --- a/source/reference/configuration-options.txt +++ b/source/reference/configuration-options.txt @@ -3649,9 +3649,6 @@ LDAP Parameters all available disk space. If you set :setting:`storage.syncPeriodSecs` to ``0`` for testing purposes, you should also set :option:`--nojournal ` to ``true``. - - The :dbcommand:`serverStatus` command reports the background flush - thread's status via the :serverstatus:`backgroundFlushing` field. The :setting:`storage.syncPeriodSecs` setting is available only for :binary:`~bin.mongod`. diff --git a/source/reference/connection-string.txt b/source/reference/connection-string.txt index 6e2c357560a..702f19bea28 100644 --- a/source/reference/connection-string.txt +++ b/source/reference/connection-string.txt @@ -759,7 +759,7 @@ timeout using the :urioption:`wtimeoutMS` write concern parameter: You can specify a :writeconcern:`number <\>`, the string :writeconcern:`majority <"majority">`, or a - :writeconcern:`tag set <\>`. + :writeconcern:`tag set <\>`. For details, see :ref:`wc-w`. diff --git a/source/reference/method.txt b/source/reference/method.txt index ccd721680d7..9881315e0e3 100644 --- a/source/reference/method.txt +++ b/source/reference/method.txt @@ -1112,10 +1112,8 @@ Sharding Free Monitoring --------------- -.. only:: website - - .. list-table:: - :header-rows: 1 +.. list-table:: + :header-rows: 1 * - Name diff --git a/source/reference/method/Mongo.watch.txt b/source/reference/method/Mongo.watch.txt index 8e547912320..9513ee6b8dc 100644 --- a/source/reference/method/Mongo.watch.txt +++ b/source/reference/method/Mongo.watch.txt @@ -235,7 +235,7 @@ Resumability .. |watchmethod| replace:: :method:`Mongo.watch()` -.. topic:: Resume Token +.. note:: Resume Token .. include:: /includes/extracts/changestream-resume-token-versions-4.2-greater.rst diff --git a/source/reference/method/cursor.max.txt b/source/reference/method/cursor.max.txt index 37d9d1188ef..b7590910b13 100644 --- a/source/reference/method/cursor.max.txt +++ b/source/reference/method/cursor.max.txt @@ -59,7 +59,7 @@ The ``indexBounds`` parameter has the following prototype form: The fields correspond to *all* the keys of a particular index *in order*. -.. topic:: Index Use +.. note:: Index Use Starting in MongoDB 4.2, you must explicitly specify the particular index with the :method:`~cursor.hint()` method to run diff --git a/source/reference/method/cursor.min.txt b/source/reference/method/cursor.min.txt index 6426a6759ee..7e7fd89fc15 100644 --- a/source/reference/method/cursor.min.txt +++ b/source/reference/method/cursor.min.txt @@ -53,7 +53,7 @@ Definition { field1: , field2: , fieldN: } -.. topic:: Index Use +.. note:: Index Use Starting in MongoDB 4.2, you must explicitly specify the particular index with the :method:`~cursor.hint()` method to run diff --git a/source/reference/method/db.collection.watch.txt b/source/reference/method/db.collection.watch.txt index 23946f66b35..ae9a0c29c67 100644 --- a/source/reference/method/db.collection.watch.txt +++ b/source/reference/method/db.collection.watch.txt @@ -238,7 +238,7 @@ Resumability .. include:: /includes/extracts/changestream-resume.rst -.. topic:: Resume Token +.. note:: Resume Token .. include:: /includes/extracts/changestream-resume-token-versions-4.2-greater.rst diff --git a/source/reference/method/db.createCollection.txt b/source/reference/method/db.createCollection.txt index cb118b7ee54..2887f02ab01 100644 --- a/source/reference/method/db.createCollection.txt +++ b/source/reference/method/db.createCollection.txt @@ -187,8 +187,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 ` - 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/method/db.watch.txt b/source/reference/method/db.watch.txt index bb1bc368d01..1be5c7deeeb 100644 --- a/source/reference/method/db.watch.txt +++ b/source/reference/method/db.watch.txt @@ -239,7 +239,7 @@ Resumability .. include:: /includes/extracts/changestream-resume.rst -.. topic:: Resume Token +.. note:: Resume Token .. include:: /includes/extracts/changestream-resume-token-versions-4.2-greater.rst diff --git a/source/reference/method/js-collection.txt b/source/reference/method/js-collection.txt index 8d61797d901..879f9c47a85 100644 --- a/source/reference/method/js-collection.txt +++ b/source/reference/method/js-collection.txt @@ -10,7 +10,7 @@ Collection Methods :depth: 1 :class: singlecol -.. topic:: ``mongo`` Shell Methods +.. note:: ``mongo`` Shell Methods .. include:: /includes/fact-mongo-shell-method-toc.rst diff --git a/source/reference/method/js-cursor.txt b/source/reference/method/js-cursor.txt index 31027fc28a4..b432e3e1997 100644 --- a/source/reference/method/js-cursor.txt +++ b/source/reference/method/js-cursor.txt @@ -10,7 +10,7 @@ Cursor Methods :depth: 1 :class: singlecol -.. topic:: ``mongo`` Shell Methods +.. note:: ``mongo`` Shell Methods .. include:: /includes/fact-mongo-shell-method-toc.rst diff --git a/source/reference/method/sh.status.txt b/source/reference/method/sh.status.txt index d3327904055..4df54dc2450 100644 --- a/source/reference/method/sh.status.txt +++ b/source/reference/method/sh.status.txt @@ -64,7 +64,7 @@ Definition .. seealso:: - :method:`db.printShardingStatus()` + :method:`db.printShardingStatus()` .. end-include-here diff --git a/source/reference/mongo-shell.txt b/source/reference/mongo-shell.txt index 028509073d4..152a96dce85 100644 --- a/source/reference/mongo-shell.txt +++ b/source/reference/mongo-shell.txt @@ -104,7 +104,6 @@ displays some common help methods and commands: :ref:`4.0-compat-show-collections` - * - ``show users`` - Print a list of users for current database. diff --git a/source/reference/operator/aggregation/collStats.txt b/source/reference/operator/aggregation/collStats.txt index 6aa9107de92..ac73c184e47 100644 --- a/source/reference/operator/aggregation/collStats.txt +++ b/source/reference/operator/aggregation/collStats.txt @@ -302,7 +302,7 @@ This query returns a result similar to the following: See :ref:`collStats-output` for a reference on this document. -.. topic:: In-progress Indexes +.. note:: In-progress Indexes Starting in MongoDB 4.2, the returned ``storageStats`` includes information on indexes being built. For details, see: diff --git a/source/reference/operator/aggregation/out.txt b/source/reference/operator/aggregation/out.txt index 3161c19f639..109fdca022e 100644 --- a/source/reference/operator/aggregation/out.txt +++ b/source/reference/operator/aggregation/out.txt @@ -85,7 +85,7 @@ The :pipeline:`$out` stage has the following syntax: Comparison with ``$merge`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. topic:: ``$merge`` and ``$out`` Comparison +.. note:: ``$merge`` and ``$out`` Comparison With the introduction of :pipeline:`$merge` in version 4.2, MongoDB provides two stages, :pipeline:`$merge` and :pipeline:`$out`, for diff --git a/source/reference/operator/meta/max.txt b/source/reference/operator/meta/max.txt index 0442db6cc9d..d169a00a943 100644 --- a/source/reference/operator/meta/max.txt +++ b/source/reference/operator/meta/max.txt @@ -36,7 +36,7 @@ Definition db.collection.find( { } )._addSpecial( "$max", { field1: , ... fieldN: } ) db.collection.find( { $query: { }, $max: { field1: , ... fieldN: } } ) -.. topic:: Index Use +.. note:: Index Use Starting in MongoDB 4.2, you must explicitly specify the particular index with the :method:`~cursor.hint()` method to run diff --git a/source/reference/operator/meta/min.txt b/source/reference/operator/meta/min.txt index 382ef4d4aaf..d89eb30be95 100644 --- a/source/reference/operator/meta/min.txt +++ b/source/reference/operator/meta/min.txt @@ -36,7 +36,7 @@ Definition db.collection.find( { } )._addSpecial( "$min", { field1: , ... fieldN: } ) db.collection.find( { $query: { }, $min: { field1: , ... fieldN: } } ) -.. topic:: Index Use +.. note:: Index Use Starting in MongoDB 4.2, you must explicitly specify the particular index with the :method:`~cursor.hint()` method to run diff --git a/source/reference/program/mongod.txt b/source/reference/program/mongod.txt index 380c706bf83..11fdc3e773c 100644 --- a/source/reference/program/mongod.txt +++ b/source/reference/program/mongod.txt @@ -1509,9 +1509,6 @@ Storage Options all available disk space. If you set :option:`--syncdelay` to ``0`` for testing purposes, you should also set :option:`--nojournal ` to ``true``. - - The :dbcommand:`serverStatus` command reports the background flush - thread's status via the :serverstatus:`backgroundFlushing` field. .. include:: /includes/not-available-for-inmemory-storage-engine.rst @@ -3379,7 +3376,7 @@ Encryption Key Management Options String containing the path to the client certificate used for authenticating MongoDB to the KMIP server. Requires that a - :setting:`kmipServerName` be provided. + :option:`--kmipServerName` be provided. .. note:: @@ -3396,9 +3393,9 @@ Encryption Key Management Options .. versionadded:: 3.2 The password (if one exists) for the client certificate passed into - :setting:`kmipClientCertificateFile`. Is used for + :option:`--kmipClientCertificateFile`. Is used for authenticating MongoDB to the KMIP server. Requires that a - :setting:`kmipClientCertificateFile` be provided. + :option:`--kmipClientCertificateFile` be provided. .. include:: /includes/fact-enterprise-only-admonition.rst diff --git a/source/reference/read-concern-majority.txt b/source/reference/read-concern-majority.txt index ddf1e13726b..dfda562fad7 100644 --- a/source/reference/read-concern-majority.txt +++ b/source/reference/read-concern-majority.txt @@ -176,15 +176,15 @@ If ``false``, read concern "majority" is disabled. cluster with a three-member PSA shard, disable to prevent the storage cache pressure from immobilizing the deployment. -.. topic:: Change Streams +.. note:: Change Streams .. include:: /includes/extracts/changestream-disable-rc-majority.rst -.. topic:: Transactions +.. note:: Transactions .. include:: /includes/extracts/transactions-read-concern-majority.rst -.. topic:: Rollback Considerations +.. note:: Rollback Considerations .. include:: /includes/fact-disable-majority-rc-rollbacks.rst diff --git a/source/release-notes/2.4-javascript.txt b/source/release-notes/2.4-javascript.txt index 335bae621e0..54d413d4937 100644 --- a/source/release-notes/2.4-javascript.txt +++ b/source/release-notes/2.4-javascript.txt @@ -15,7 +15,7 @@ MongoDB 2.4: .. tip:: - Use the new :js:func:`interpreterVersion()` method in the + Use the new ``interpreterVersion()`` method in the :binary:`~bin.mongo` shell and the :data:`~buildInfo.javascriptEngine` field in the output of :method:`db.serverBuildInfo()` to determine which JavaScript engine a MongoDB binary uses. diff --git a/source/release-notes/3.2-javascript.txt b/source/release-notes/3.2-javascript.txt index bc471987221..329911fb154 100644 --- a/source/release-notes/3.2-javascript.txt +++ b/source/release-notes/3.2-javascript.txt @@ -15,7 +15,7 @@ and for server-side javascript in :binary:`~bin.mongod` changed from V8 to `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 +``interpreterVersion()`` method in the :binary:`~bin.mongo` shell and the :data:`~buildInfo.javascriptEngine` field in the output of :method:`db.serverBuildInfo()` diff --git a/source/release-notes/4.2.txt b/source/release-notes/4.2.txt index a3b42b81cfc..fd52caaf506 100644 --- a/source/release-notes/4.2.txt +++ b/source/release-notes/4.2.txt @@ -332,7 +332,7 @@ Issues fixed: Distributed Transactions ------------------------ -.. 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/tutorial/backup-and-restore-tools.txt b/source/tutorial/backup-and-restore-tools.txt index aa29050c707..a474d5c5614 100644 --- a/source/tutorial/backup-and-restore-tools.txt +++ b/source/tutorial/backup-and-restore-tools.txt @@ -15,7 +15,7 @@ Back Up and Restore with MongoDB Tools This tutorial describes the process for creating backups and restoring data using the utilities provided with MongoDB. -.. topic:: MongoDB Atlas +.. note:: MongoDB Atlas MongoDB Atlas, the official MongoDB cloud service, provides 2 fully-managed methods for backups: diff --git a/source/tutorial/deploy-shard-cluster.txt b/source/tutorial/deploy-shard-cluster.txt index 9a517176665..58dae575940 100644 --- a/source/tutorial/deploy-shard-cluster.txt +++ b/source/tutorial/deploy-shard-cluster.txt @@ -247,7 +247,7 @@ To shard a collection, connect to the :binary:`~bin.mongos` from the :binary:`~bin.mongo` shell and use the :method:`sh.shardCollection()` method. -.. topic:: Sharding and Indexes +.. note:: Sharding and Indexes If the collection already contains data, you must :ref:`create an index ` that supports the