Skip to content

Commit bd6fa6c

Browse files
committed
Fix em-dash usage
1 parent cc61f5f commit bd6fa6c

3 files changed

Lines changed: 5 additions & 5 deletions

File tree

learn-pr/wwl-azure/guided-project-cost-guardrails/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 setting up cost guardrails using resource tags, budgets, and Azure Policy.
22

3-
Azure provides several tools to help you control cloud spending. Tags let you categorize resources for cost reporting. Budgets send alerts when spending approaches a threshold. Azure Policy enforces organizational ruleslike restricting which regions resources can be deployed toautomatically.
3+
Azure provides several tools to help you control cloud spending. Tags let you categorize resources for cost reporting. Budgets send alerts when spending approaches a threshold. Azure Policy enforces organizational ruleslike restricting which regions resources can be deployed toautomatically.
44

55
## Scenario
66

learn-pr/wwl-azure/guided-project-cost-guardrails/includes/2-exercise-tag-resources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This guided project consists of the following exercises:
44
- Create budget and alerts
55
- Assign and test Azure Policy
66

7-
In this exercise, you create a resource group and storage account, then apply organizational tags to both. Tags are the foundation of cost governancethey let you categorize resources by team, environment, or project so you can track spending accurately.
7+
In this exercise, you create a resource group and storage account, then apply organizational tags to both. Tags are the foundation of cost governancethey let you categorize resources by team, environment, or project so you can track spending accurately.
88

99
This exercise includes the following tasks:
1010

@@ -63,7 +63,7 @@ Apply organizational tags to your resource group. Tags are key-value pairs that
6363
> **Validation step:** Confirm the resource group displays both tags (**environment: pilot** and **owner: it-team**).
6464
6565
> [!NOTE]
66-
> 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.
66+
> 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.
6767
6868
## Task 4: Tag the storage account
6969

learn-pr/wwl-azure/guided-project-cost-guardrails/includes/4-exercise-assign-test-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Test that the policy prevents resource creation in disallowed regions. This vali
4040
4. For **Storage account name**, enter a temporary name (for example, **stgppolicytest** followed by your initials).
4141
5. For **Region**, select a region that is **not** the allowed location you configured in the policy.
4242
6. Select **Review + create**.
43-
7. Confirm the creation is denied with a policy error message. Note the errorit references the **Allowed locations** policy by name.
43+
7. Confirm the creation is denied with a policy error message. Note the errorit references the **Allowed locations** policy by name.
4444
8. Select **Previous** to return to the **Basics** tab.
4545
9. Change the **Region** to the allowed location.
4646
10. Select **Review + create** again.
@@ -58,7 +58,7 @@ Check the policy compliance dashboard to see how Azure tracks compliance across
5858
2. In the left menu, select **Compliance**.
5959
3. Find the **Allowed locations** policy assignment in the compliance list.
6060
4. Select it to view the compliance details, including the number of compliant and noncompliant resources.
61-
5. Note the compliance stateresources created in the allowed region should show as compliant.
61+
5. Note the compliance stateresources created in the allowed region should show as compliant.
6262

6363
> [!NOTE]
6464
> **Validation step:** Confirm the Compliance dashboard shows the policy enforcement status with compliant resources in the allowed region.

0 commit comments

Comments
 (0)