Skip to content

Commit 020f466

Browse files
authored
Update alerts-classic.overview.md
1 parent e6f9b75 commit 020f466

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-monitor/alerts/alerts-classic.overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,8 @@ The following diagram summarizes sources of data in Azure Monitor and, conceptua
5252
## Taxonomy of alerts (classic)
5353
Azure uses the following terms to describe classic alerts and their functions:
5454
* **Alert**: A definition of criteria (one or more rules or conditions) that becomes activated when met.
55-
* **Active**: The state when the criteria defined by a classic alert is met.
56-
* **Resolved**: The state when the criteria defined by a classic alert is no longer met after it was previously met.
55+
* **Active**: The state when the criteria defined by a classic alert are met.
56+
* **Resolved**: The state when the criteria defined by a classic alert are no longer met after they were previously met.
5757
* **Notification**: The action taken based off of a classic alert becoming active.
5858
* **Action**: A specific call sent to a receiver of a notification (for example, emailing an address or posting to a webhook URL). Notifications can usually trigger multiple actions.
5959

0 commit comments

Comments
 (0)