Skip to content

Commit 35aea3e

Browse files
authored
Merge pull request #312662 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 6871b98 + f1e7724 commit 35aea3e

2 files changed

Lines changed: 5 additions & 5 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

articles/traffic-manager/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ landingContent:
4949
url: traffic-manager-configure-geographic-routing-method.md
5050
- text: Configure the weighted traffic routing method
5151
url: traffic-manager-configure-weighted-routing-method.md
52-
- text: Configure priority traffic routing method
52+
- text: Configure the priority traffic routing method
5353
url: traffic-manager-configure-priority-routing-method.md
5454
- text: Control traffic routing with weighted endpoints
5555
url: tutorial-traffic-manager-weighted-endpoint-routing.md
@@ -73,7 +73,7 @@ landingContent:
7373
url: traffic-manager-manage-endpoints.md
7474
- text: Manage a Traffic Manager profile
7575
url: traffic-manager-manage-profiles.md
76-
- text: Using load-balancing services in Azure
76+
- text: Use load-balancing services in Azure
7777
url: traffic-manager-load-balancing-azure.md
7878
- text: Point a company Internet domain to an Azure Traffic Manager domain
7979
url: traffic-manager-point-internet-domain.md

0 commit comments

Comments
 (0)