DOCSP-24523-read-concern-definition (#1755)

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

* DOCSP-24523-read-concern-definition

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/includes/snapshot-definition.rst

@@ -0,0 +1,5 @@
+A snapshot is a complete copy of the data in a :binary:`mongod` instance
+at a specific point in time. You can retrieve snapshot metadata for the
+whole cluster or replica set, or for a single config server in a
+cluster. For more details, see `snapshots
+<https://www.mongodb.com/docs/cloud-manager/reference/api/snapshots>`__.

source/reference/glossary.txt

@@ -1002,6 +1002,9 @@ Glossary
       consistency and is the replication topology employed by MongoDB.
       See :doc:`/core/replica-set-primary`.
 
+   snapshot
+      .. include:: /includes/snapshot-definition.rst
+
    snappy
       A compression/decompression library designed to balance
       efficient computation requirements with reasonable compression rates.

source/reference/read-concern-snapshot.txt

@@ -21,14 +21,16 @@ Read Concern ``"snapshot"``
 .. versionadded:: 4.0
 .. versionchanged:: 5.0
 
+.. include:: /includes/snapshot-definition.rst
+
 Read concern ``"snapshot"`` is available for :doc:`multi-document
 transactions </core/transactions>`, and starting in MongoDB 5.0, certain
 read operations outside of multi-document transactions.
 
 - If the transaction is not part of a :ref:`causally consistent session
   <sessions>`, upon transaction commit with write concern
   :writeconcern:`"majority"`, the transaction operations are guaranteed
-  to have read from a snapshot of majority-committed data.
+  to have read from a :term:`snapshot` of majority-committed data.
 
 - If the transaction is part of a :ref:`causally consistent session
   <sessions>`, upon transaction commit with write concern

source/reference/read-concern.txt

@@ -22,7 +22,6 @@ of consistency and availability guarantees as appropriate, such as
 waiting for stronger consistency guarantees, or loosening consistency
 requirements to provide higher availability.
 
-
 MongoDB drivers updated for MongoDB 3.2 or later support specifying
 read concern.
 
@@ -161,12 +160,14 @@ The following read concern levels are available:
 
    * - :readconcern:`"snapshot"`
 
-     - | If a transaction is not part of a :ref:`causally consistent
+     - .. include:: /includes/snapshot-definition.rst
+       
+       | If a transaction is not part of a :ref:`causally consistent
          session <sessions>`, upon transaction commit with write
          concern :writeconcern:`"majority"`, the transaction operations
          are guaranteed to have read from a snapshot of
          majority-committed data.
-
+     
        | If a transaction is part of a :ref:`causally consistent
          session <sessions>`, upon transaction commit with write
          concern :writeconcern:`"majority"`, the transaction operations
@@ -190,8 +191,6 @@ The following read concern levels are available:
          All other read operations prohibit
          :readconcern:`"snapshot"`.
 
-
-
 .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst
 
 For more information on each read concern level, see:
@@ -203,7 +202,6 @@ For more information on each read concern level, see:
 - :doc:`/reference/read-concern-snapshot`
 - :doc:`/reference/mongodb-defaults`
 
-
 ``readConcern`` Support
 -----------------------
 
@@ -268,7 +266,6 @@ concern.
 For more information, see :ref:`Transaction Read Concern
 <transactions-read-concern>`.
 
-
 Causally Consistent Sessions and Available Read Concerns
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~