Skip to content

Commit 423463e

Browse files
committed
Fix em-dash usage
1 parent 811246e commit 423463e

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

learn-pr/wwl-azure/guided-project-monitor-service-health-activity-alerts/includes/1-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
This guided project focuses on monitoring Azure using Service Health alerts, Activity Log alerts, and action groups.
22

3-
Azure Monitor provides several alert types that notify you about issues without requiring paid compute resources. Service Health alerts watch for platform-level incidents and planned maintenance. Activity Log alerts fire when management operationslike resource deletionoccur. Action groups define who gets notified and how.
3+
Azure Monitor provides several alert types that notify you about issues without requiring paid compute resources. Service Health alerts watch for platform-level incidents and planned maintenance. Activity Log alerts fire when management operationslike resource deletionoccur. Action groups define who gets notified and how.
44

55
## Scenario
66

learn-pr/wwl-azure/guided-project-monitor-service-health-activity-alerts/includes/2-exercise-create-action-group.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This guided project consists of the following exercises:
44
- Create a Service Health alert
55
- Create an Activity Log alert
66

7-
In this exercise, you create an action group with email notification and send a test message to verify delivery. Action groups are the notification backbone for Azure alertsyou set them up once and reuse them across multiple alert rules.
7+
In this exercise, you create an action group with email notification and send a test message to verify delivery. Action groups are the notification backbone for Azure alertsyou set them up once and reuse them across multiple alert rules.
88

99
This exercise includes the following tasks:
1010

@@ -50,7 +50,7 @@ Create an action group that defines who gets notified and how. Action groups are
5050
> **Validation step:** Confirm the **ag-gp-ops-email** action group is created with email notification configured.
5151
5252
> [!NOTE]
53-
> Each exercise includes validation steps like this one. Track your results as you goyou'll review them all in the validation unit at the end of this module.
53+
> Each exercise includes validation steps like this one. Track your results as you goyou'll review them all in the validation unit at the end of this module.
5454
5555
## Task 3: Test the action group
5656

@@ -62,7 +62,7 @@ Send a test notification to verify the action group delivers email successfully.
6262
4. Make sure the **ops-team-email** notification is checked.
6363
5. Select **Test**.
6464
6. Wait for the test results to appear. Confirm the **Status** column shows **Success**.
65-
7. Check your email inbox for the test notification from Azure. Open the email and review its contentthis is the same format you would receive during a real incident.
65+
7. Check your email inbox for the test notification from Azure. Open the email and review its contentthis is the same format you would receive during a real incident.
6666

6767
> [!NOTE]
6868
> **Validation step:** Confirm the test notification status shows **Success** and you received the email notification.

0 commit comments

Comments
 (0)