AWS documentdb documentation change
Summary
Editorial updates: replaced 'please see' with 'see', improved sentence flow, and removed 'Please' from session consistency note
Security assessment
Changes are limited to grammatical improvements and tone adjustments. Transaction limits and session consistency concepts remain unchanged with no security implications.
Diff
diff --git a/documentdb/latest/devguide/transactions.md b/documentdb/latest/devguide/transactions.md index 6de607d91..3baa8c4fd 100644 --- a//documentdb/latest/devguide/transactions.md +++ b//documentdb/latest/devguide/transactions.md @@ -72 +72 @@ Here are some best practices so that you can get the most using transactions wit - * Each Amazon DocumentDB instance has an upper bound limit on the number of concurrent transaction open on the instance at one time. For the limits, please see [Instance limits](./limits.html#limits.instance). + * Each Amazon DocumentDB instance has an upper bound limit on the number of concurrent transaction open on the instance at one time. For the limits, see [Instance limits](./limits.html#limits.instance). @@ -123 +123 @@ Additionally, new fields were added to both `currentOp` `lsid`, `transactionThre -When starting a transaction, you have the ability to specify both the `readConcern` and `writeConcern` as shown in the example below: +When starting a transaction, you have the ability to specify both the `readConcern` and `writeConcern` as shown in the following example: @@ -1696 +1696 @@ Causal consistency guarantees that within a single client session the client wil -You can disable causal consistency within a session. Please note, doing so will enable you to utilize the session framework, but will not provide causal consistency guarantees for reads. When using Amazon DocumentDB, reads from the primary will be read-after-write consistent and reads from the replica instances will be eventually consistent. Transactions are the primary use case for utilizing sessions. +You can disable causal consistency within a session. Note that doing so will enable you to utilize the session framework, but will not provide causal consistency guarantees for reads. When using Amazon DocumentDB, reads from the primary will be read-after-write consistent and reads from the replica instances will be eventually consistent. Transactions are the primary use case for utilizing sessions.