Merge pull request #284064 from seesharprun/cosmos-ttl

Cosmos DB | Improve Acrolinx score in TTL article

Author: v-shils

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

@@ -7,14 +7,16 @@ ms.reviewer: mjbrown
 ms.service: azure-cosmos-db
 ms.subservice: nosql
 ms.topic: conceptual
-ms.date: 11/03/2023
+ms.date: 08/08/2024
 ---
+
 # Time to Live (TTL) in Azure Cosmos DB
+
 [!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
 
-With **Time to Live** or TTL, Azure Cosmos DB deletes items automatically from a container after a certain time period. By default, you can set time to live at the container level and override the value on a per-item basis. After you set the TTL at a container or at an item level, Azure Cosmos DB will automatically remove these items after the time period, since the time they were last modified. Time to live value is configured in seconds. When you configure TTL, the system automatically deletes the expired items based on the TTL value, without needing a delete operation explicitly issued by the client application. The maximum value for TTL is 2147483647 seconds, the approximate equivalent of 24,855 days or 68 years.
+With **Time to Live** or TTL, Azure Cosmos DB deletes items automatically from a container after a certain time period. By default, you can set time to live at the container level and override the value on a per-item basis. After you set the TTL at a container or at an item level, Azure Cosmos DB will automatically remove these items after the time period, since the time they were last modified. Time to live value is configured in seconds. When you configure TTL, the system automatically deletes the expired items based on the TTL value, without needing a delete operation explicitly issued by the client application. The maximum value for TTL is 2,147,483,647 seconds, the approximate equivalent of 24,855 days or 68 years.
 
-Deletion of expired items is a background task that consumes left-over [Request Units](../request-units.md) that haven't been consumed by user requests. Even after the TTL expires, if the container is overloaded with requests and if there aren't enough RUs available, the data deletion is delayed. Data is deleted once there are enough RUs available to perform the delete operation. Though the data deletion is delayed, data isn't returned by any queries (by any API) after the TTL expires.
+Deletion of expired items is a background task that consumes left-over [Request Units](../request-units.md) that haven't been consumed by user requests. Even after the TTL expires, if the container is overloaded with requests and if there aren't enough request units (RUs) available, the data deletion is delayed. Data is deleted once there are enough RUs available to perform the delete operation. Though the data deletion is delayed, data isn't returned by any queries (by any API) after the TTL expires.
 
 > [!NOTE]
 > This content is related to Azure Cosmos DB transactional store TTL. If you are looking for analytical store TTL, that enables NoETL HTAP scenarios through [Azure Synapse Link](../synapse-link.md), please click [here](../analytical-store-introduction.md#analytical-ttl).
@@ -27,9 +29,9 @@ The time to live value is set in seconds, and is interpreted as a delta from the
 
    - If missing (or set to null), items aren't expired automatically.
 
-   - If present and the value is set to "-1", it's equal to infinity, and items don’t expire by default.
+   - If present and the value is set to *"-1,"* it's equal to infinity, and items don’t expire by default.
 
-   - If present and the value is set to some *nonzero* number *"n"* – items will expire *"n"* seconds after their last modified time.
+   - If present and the value is set to some *nonzero* number *"n,"* items will expire *"n"* seconds after their last modified time.
 
 2. **Time to Live on an item** (set using `ttl`):
 
@@ -58,29 +60,29 @@ TTL on container is set to null (DefaultTimeToLive = null)
 
 |TTL on item| Result|
 |---|---|
-|ttl property missing |TTL is disabled. The item will never expire (default).|
-|ttl = -1|TTL is disabled. The item will never expire.|
-|ttl = 2000|TTL is disabled. The item will never expire.|
+|ttl property missing |TTL is disabled. The item never expires (default).|
+|ttl = -1|TTL is disabled. The item never expires.|
+|ttl = 2000|TTL is disabled. The item never expires.|
 
 ### Example 2
 
 TTL on container is set to -1 (DefaultTimeToLive = -1)
 
 |TTL on item| Result|
 |---|---|
-|ttl property missing |TTL is enabled. The item will never expire (default).|
-|ttl = -1|TTL is enabled. The item will never expire.|
-|ttl = 2000|TTL is enabled. The item will expire after 2000 seconds.|
+|ttl property missing |TTL is enabled. The item never expires (default).|
+|ttl = -1|TTL is enabled. The item never expires.|
+|ttl = 2000|TTL is enabled. The item expires after 2,000 seconds.|
 
 ### Example 3
 
 TTL on container is set to 1000 (DefaultTimeToLive = 1000)
 
 |TTL on item| Result|
 |---|---|
-|ttl property missing |TTL is enabled. The item will expire after 1000 seconds (default).|
+|ttl property missing |TTL is enabled. The item will expire after 1,000 seconds (default).|
 |ttl = -1|TTL is enabled. The item will never expire.|
-|ttl = 2000|TTL is enabled. The item will expire after 2000 seconds.|
+|ttl = 2000|TTL is enabled. The item will expire after 2,000 seconds.|
 
 ## Next steps