Import wiredtiger: 2aa2673d45c3ef1666107a5e381202f92502201e from branch mongodb-master

ref: 03dfd53f7a..2aa2673d45
for: 6.0.0-rc0

WT-8990       Validate commit and durability timestamps at transaction commit

1 files changed, 7 insertions, 5 deletions

diff --git a/src/third_party/wiredtiger/src/docs/transactions_api.dox b/src/third_party/wiredtiger/src/docs/transactions_api.dox
index e3083aaac59..de4054018da 100644
--- a/src/third_party/wiredtiger/src/docs/transactions_api.dox
+++ b/src/third_party/wiredtiger/src/docs/transactions_api.dox
@@ -136,14 +136,16 @@ well as any key and value that may have been set.
 
 @section snapshot_reset Resetting the session snapshot
 
-Snapshot-isolation transactions can pin a large amount of data into the database
+Snapshot-isolation transactions can pin large amounts of data into the database
 cache in order to be able to satisfy potential reads at the snapshot.
 WT_SESSION::reset_snapshot releases the current snapshot and gets a new (more
 recent) snapshot to avoid pinning content in the cache that is no longer needed.
-Applications may see different search results compared to earlier after updating
-the snapshot. It is an error to call WT_SESSION::reset_snapshot at any isolation
-level other than snapshot, or if the current transaction has performed any write
-operations.
+It is an error to call WT_SESSION::reset_snapshot at any isolation level other
+than snapshot, or if the current transaction has performed any write operations.
+
+\warning
+Applications not using read timestamps for search may see different results
+after the snapshot is updated.
 
 @snippet ex_all.c reset snapshot