AWS documentdb documentation change
Summary
Removed the word 'please' from two sentences for editorial consistency
Security assessment
Change is purely editorial/cosmetic (removing 'please') without modifying technical content about transactions or profiling. No security implications as atomicity/consistency guarantees and profiling functionality remain unchanged.
Diff
diff --git a/documentdb/latest/devguide/functional-differences.md b/documentdb/latest/devguide/functional-differences.md index e71e4b509..994f5aa0c 100644 --- a//documentdb/latest/devguide/functional-differences.md +++ b//documentdb/latest/devguide/functional-differences.md @@ -28 +28 @@ The following are the functional differences between Amazon DocumentDB (with Mon -In Amazon DocumentDB, all CRUD statements (`findAndModify`, `update`, `insert`, `delete`) guarantee atomicity and consistency, even for operations that modify multiple documents. With the launch of Amazon DocumentDB 4.0, explicit transactions that provide ACID properties for multi-statement and multi-collection operations are now supported. For more on using transactions in Amazon DocumentDB, please see [Transactions in Amazon DocumentDB](./transactions.html). +In Amazon DocumentDB, all CRUD statements (`findAndModify`, `update`, `insert`, `delete`) guarantee atomicity and consistency, even for operations that modify multiple documents. With the launch of Amazon DocumentDB 4.0, explicit transactions that provide ACID properties for multi-statement and multi-collection operations are now supported. For more on using transactions in Amazon DocumentDB, see [Transactions in Amazon DocumentDB](./transactions.html). @@ -431 +431 @@ You can identify the indexing algorithm that is being used for the `$lookup` ope -As an alternative to using the `explain()` method, you can use the profiler to review the algorithm that is being utilized with your use of the `$lookup` operator. For more information on the profiler, please see [Profiling Amazon DocumentDB operations](./profiling.html). +As an alternative to using the `explain()` method, you can use the profiler to review the algorithm that is being utilized with your use of the `$lookup` operator. For more information on the profiler, see [Profiling Amazon DocumentDB operations](./profiling.html).