tweaks for clarity

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable-task-scheduler/durable-task-scheduler-auto-purge.md

@@ -9,44 +9,42 @@ ms.date: 04/17/2025
 
 Large volumes of completed orchestration instance data can lead to storage bloat, incur higher storage cost, and increase performance issues. The autopurge feature for Durable Task Scheduler offers a lightweight, configurable, and adoptable way to manage orchestration instance clean-up without manual intervention.
 
-## How it works
+Autopurge runs asynchronously in the background to avoid using too many system resources and to prevent blocking or delaying other Durable Task operations. While autopurge doesn't run on a precise schedule, the clean-up rate roughly matches your orchestration scheduling rate.
 
-You enable autopurge by defining retention policies that control how long to keep completed, failed, or canceled orchestrations. Once enabled, autopurge deletes orchestration instances older than the retention period you set. 
+## Enable autopurge
 
-Autopurge runs asynchronously in the background to avoid using too many system resources and blocking or delaying other Durable Task operations. While autopurge doesn't run on a precise schedule, the clean-up rate roughly matches your orchestration scheduling rate.
-
-### Enable autopurge
+Enable autopurge by defining retention policies that control how long to keep completed, failed, or canceled orchestrations. Once enabled, autopurge deletes orchestration instances older than the retention period you set. 
 
 You can configure autopurge using:
 
-- Azure Resource Manager: Retention Policy Spec
-- Azure CLI (coming soon)
-- Azure portal (coming soon)
+- Azure Resource Manager
+- Azure CLI
+- Azure portal
 
 # [Azure Resource Manager](#tab/arm)  
 
-When configuring in Azure Resource Manager, you can set a *specific* retention policy. Specific policies are applied only to the `orchestrationState` specified. 
+When configuring in Azure Resource Manager, you can set either a *specific* or a *default* retention policy. Retention value can range from 0 (purge immediately after completion) to any large number.
 
-```json
-{
-  "retentionPeriodInDays": 1,
-  "orchestrationState": "Completed"
-}
-```
+- **Specific policies** are applied only to the `orchestrationState` specified. 
 
-In this example, the retention policy tells Durable Task Scheduler to keep completed orchestrations for 1 day, and purge the rest. 
+     ```json
+     {
+       "retentionPeriodInDays": 1,
+       "orchestrationState": "Completed"
+     }
+     ```
 
-You can also set a default policy to apply to all purgeable statuses by omitting `orchestrationState`:
+     In this example, the retention policy tells Durable Task Scheduler to keep completed orchestrations for 1 day, and purge the rest. 
 
-```json
-{
-  "retentionPeriodInDays": 2
-}
-```
+- **Default policies** are applied to all purgeable statuses by omitting `orchestrationState`:
 
-You can set retention from 0 (purge immediately after completion) to any large number.
+     ```json
+     {
+       "retentionPeriodInDays": 2
+     }
+     ```
 
-[For more information, see the API reference spec for Durable Task Scheduler retention policies](/rest/api/durabletask/retention-policies/create-or-replace?view=rest-durabletask-2025-04-01-preview&preserve-view=true)
+[For more information, see the API reference spec for Durable Task Scheduler retention policies.](/rest/api/durabletask/retention-policies/create-or-replace?view=rest-durabletask-2025-04-01-preview&preserve-view=true)
 
 # [Azure CLI](#tab/cli)  
 todo
@@ -59,7 +57,7 @@ todo
 > [!NOTE]
 > If both a specific and a default policy are set, the specific policy takes priority.
 
-### Disable autopurge
+## Disable autopurge
 
 # [Azure Resource Manager](#tab/arm)