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

Co-authored-by: Hannah Hunter <[email protected]>

Author: pradeepmi-MSFT

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

@@ -21,7 +21,7 @@ Autopurge is an opt-in feature. You can enable it by defining retention policies
 
 The orchestration instances eligible for autopurge match those targeted by [the Durable SDK PurgeInstancesAsync API](/dotnet/api/microsoft.durabletask.client.durabletaskclientextensions.purgeinstancesasync?view=durabletask-dotnet-1.x&preserve-view=true).
 
->[!Note]
+> [!NOTE]
 > Orchestrations using `ContinueAsNew` may appear with a status that is marked as obsolete in some C# SDK versions. This behavior is expected. `ContinueAsNew` does not represent a terminal state. Instead, it restarts the orchestration with a new execution history while preserving the instance ID. In this case, such instances:
 > - Aren't considered completed or failed for auto-purge purposes.
 > - Aren't removed until they eventually reach a true terminal state (`Completed`, `Failed`, or `Terminated`).