Skip to content

Commit 30b528e

Browse files
authored
Docs: Fix spacing typo and capitalization consistency
This PR makes two minor corrections to improve readability and adhere to the Microsoft Style Guide: 1. Added a missing space after a comma in the NOTE block under the "Deploy the template" section. 2. Changed "ARM Template" to "ARM template" in the H1 heading and introductory paragraph to ensure capitalization consistency with the article's metadata title.
1 parent d4ca2cb commit 30b528e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/traffic-manager/configure-multivalue-routing-method-template.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ ms.custom:
1414
# Customer intent: As a cloud engineer, I want to configure a Multivalue routing method with nested endpoints using an ARM template, so that I can efficiently manage traffic distribution in my Azure environment.
1515
---
1616

17-
# Configure the Multivalue routing method using an ARM Template
17+
# Configure the Multivalue routing method using an ARM template
1818

19-
This article describes how to use an Azure Resource Manager template (ARM Template) to create a nested, Multivalue profile with the min-child feature.
19+
This article describes how to use an Azure Resource Manager template (ARM template) to create a nested, Multivalue profile with the min-child feature.
2020

2121
[!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
2222

@@ -69,7 +69,7 @@ To find more templates that are related to Azure Traffic Manager, see [Azure Qui
6969
The resource group name is the existing resource group that contains the existing profiles.
7070
7171
> [!NOTE]
72-
> **existingTMProfileName1**, **existingTMProfileName2**,**TMProfileDNS1**, and **TMProfileDNS2** must match your existing Traffic Manager profiles in order for the template to deploy successfully. If deployment fails, start over with Step 1.
72+
> **existingTMProfileName1**, **existingTMProfileName2**, **TMProfileDNS1**, and **TMProfileDNS2** must match your existing Traffic Manager profiles in order for the template to deploy successfully. If deployment fails, start over with Step 1.
7373
7474
It takes a few minutes to deploy the template. When completed, the output is similar to:
7575

0 commit comments

Comments
 (0)