one change

Author: v-thepet

docs/pipelines/process/conditions.md

@@ -3,7 +3,7 @@ title: Pipeline conditions
 description: Learn about how to specify the conditions under which each Azure Pipelines stage, job, or step runs.
 ms.topic: conceptual
 ms.assetid: C79149CC-6E0D-4A39-B8D1-EB36C8D3AB89
-ms.date: 06/18/2024
+ms.date: 06/20/2024
 monikerRange: '<= azure-devops'
 ---
 
@@ -19,15 +19,15 @@ This article describes the conditions under which an Azure Pipelines stage, job,
 
 You can override or customize this behavior by forcing a stage, job, or step to run even if a previous dependency fails, or by specifying a custom condition.
 
+> [!NOTE]
+> For Classic pipelines, you can specify the conditions under which the task or job runs in the **Control Options** of each task, and in the **Additional options** for a job in a release pipeline.
+
 ## Conditions under which a stage, job, or step runs
 
 In the pipeline definition YAML, you can specify the following conditions under which a stage, job, or step runs:
 [!INCLUDE [include](includes/task-run-built-in-conditions.md)]
 - Custom conditions.
 
-> [!NOTE]
-> For Classic pipelines, you can specify the conditions under which the task or job runs in the **Control Options** of each task, and in the **Additional options** for a job in a release pipeline.
-
 By default, stages, jobs, and steps run if all direct and indirect dependencies succeed. This status is the same as specifying `condition: succeeded()`. For more information, see [succeeded status function](expressions.md#succeeded).
 
 When you specify a `condition` property for a stage, job, or step, you overwrite the default `condition: succeeded()`. Specifying your own conditions can cause your stage, job, or step to run even if the build is canceled. Make sure the conditions you write take into account the state of the parent stage or job.