Merge pull request #277329 from seesharprun/patch-5

Cosmos DB | Update hyperlinks in TTL

Author: prmerger-automator[bot]

articles/cosmos-db/mongodb/time-to-live.md

@@ -8,7 +8,7 @@ ms.subservice: mongodb
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript
 ms.topic: how-to
-ms.date: 02/16/2022
+ms.date: 06/05/2024
 ms.custom: devx-track-csharp
 ---
 # Expire data with Azure Cosmos DB's API for MongoDB
@@ -38,7 +38,7 @@ The output of the command includes various metadata:
 }
 ```
 
- Once the index is created, the database will automatically delete any documents in that collection that have not been modified in the last 10 seconds. 
+ Once the index is created, the database will automatically delete any documents in that collection that haven't been modified in the last 10 seconds. 
 
 > [!NOTE]
 > `_ts` is an Azure Cosmos DB-specific field and is not accessible from MongoDB clients. It is a reserved (system) property that contains the timestamp of the document's last modification.
@@ -61,11 +61,11 @@ await collection.Indexes.CreateOneAsync(indexDefinition, options);
 ``` 
 
 ## Set time to live value for a document 
-Per-document TTL values are also supported. The document(s) must contain a root-level property "ttl" (lower-case), and a TTL index as described above must have been created for that collection. TTL values set on a document will override the collection's TTL value.
+Per-document TTL values are also supported. The document(s) must contain a root-level property "ttl" (lower-case), and a TTL index as described above must have been created for that collection. TTL values set on a document overrides the collection's TTL value.
 
-The TTL value must be an int32. Alternatively, an int64 that fits in an int32, or a double with no decimal part that fits in an int32. Values for the TTL property that do not conform to these specifications are allowed but not treated as a meaningful document TTL value.
+The TTL value must be an int32. Alternatively, an int64 that fits in an int32, or a double with no decimal part that fits in an int32. Values for the TTL property that don't conform to these specifications are allowed but not treated as a meaningful document TTL value.
 
-The TTL value for the document is optional; documents without a TTL value can be inserted into the collection.  In this case, the collection's TTL value will be honored. 
+The TTL value for the document is optional; documents without a TTL value can be inserted into the collection.  In this case, the collection's TTL value is honored. 
 
 The following documents have valid TTL values. Once the documents are inserted, the document TTL values override the collection's TTL values. So, the documents will be removed after 20 seconds. 	
 
@@ -75,13 +75,14 @@ globaldb:PRIMARY> db.coll.insert({id:1, location: "Paris", ttl: NumberInt(20)})
 globaldb:PRIMARY> db.coll.insert({id:1, location: "Paris", ttl: NumberLong(20)}) 
 ```
 
-The following documents have invalid TTL values. The documents will be inserted, but the document TTL value will not be honored. So, the documents will be removed after 10 seconds because of the collection's TTL value. 
+The following documents have invalid TTL values. The documents are inserted, but the document TTL value won't be honored. So, the documents will be removed after 10 seconds because of the collection's TTL value. 
 
 ```JavaScript 
 globaldb:PRIMARY> db.coll.insert({id:1, location: "Paris", ttl: 20.5}) //TTL value contains non-zero decimal part. 
 globaldb:PRIMARY> db.coll.insert({id:1, location: "Paris", ttl: NumberLong(2147483649)}) //TTL value is greater than Int32.MaxValue (2,147,483,648). 
 ``` 
 
-## Next steps
-* [Expire data in Azure Cosmos DB automatically with time to live](../mongodb/time-to-live.md)
-* [Indexing your Azure Cosmos DB database configured with Azure Cosmos DB's API for MongoDB](../mongodb/indexing.md)
+## Next step
+
+> [!div class="nextstepaction"]
+> [Indexing your Azure Cosmos DB database configured with Azure Cosmos DB's API for MongoDB](../mongodb/indexing.md)