Skip to content

Commit 871d5db

Browse files
Merge pull request #126877 from changeworld/patch-16
Fix typo: Traffic Manger -> Traffic Manager
2 parents 693142b + 93fd806 commit 871d5db

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/traffic-manager/traffic-manager-FAQs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ For example, if your Traffic Manager profile name is **label1**, then **label1.t
9292

9393
### What version of TLS is required by Traffic Manager?
9494

95-
The Microsoft implementation of older TLS versions is not known to be vulnerable, however, TLS 1.2 and later offer improved security with features such as perfect forward secrecy and stronger cipher suites. To enhance security and provide best-in-class encryption for your data, Traffic Manger requires interactions with services to be secured using Transport Layer Security (TLS) 1.2 or later before February 28,2025. Traffic Manger support for TLS 1.0 and 1.1 will end on this date. This date might be different than the [Azure-wide TLS 1.0 and TLS 1.1 retirement date](https://azure.microsoft.com/updates?id=update-retirement-tls1-0-tls1-1-versions-azure-services).
95+
The Microsoft implementation of older TLS versions is not known to be vulnerable, however, TLS 1.2 and later offer improved security with features such as perfect forward secrecy and stronger cipher suites. To enhance security and provide best-in-class encryption for your data, Traffic Manager requires interactions with services to be secured using Transport Layer Security (TLS) 1.2 or later before February 28,2025. Traffic Manager support for TLS 1.0 and 1.1 will end on this date. This date might be different than the [Azure-wide TLS 1.0 and TLS 1.1 retirement date](https://azure.microsoft.com/updates?id=update-retirement-tls1-0-tls1-1-versions-azure-services).
9696

9797
**Recommended action**
9898

@@ -521,7 +521,7 @@ One of the metrics provided by Traffic Manager is the health status of endpoints
521521

522522
Nested Traffic Manager profiles can be configured using both the Azure Resource Manager and the classic Azure REST APIs, Azure PowerShell cmdlets and cross-platform Azure CLI commands. They're also supported via the new Azure portal.
523523

524-
### How many layers of nesting does Traffic Manger support?
524+
### How many layers of nesting does Traffic Manager support?
525525

526526
You can nest profiles up to 10 levels deep. 'Loops' aren't permitted.
527527

articles/traffic-manager/traffic-manager-nested-profiles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ In this example, the **East US** endpoint is unhealthy, because it doesn't satis
116116

117117
* [How do I configure nested profiles?](./traffic-manager-faqs.md#traffic-manager-nested-profiles)
118118

119-
* [How many layers of nesting does Traffic Manger support?](./traffic-manager-faqs.md#how-many-layers-of-nesting-does-traffic-manger-support)
119+
* [How many layers of nesting does Traffic Manager support?](./traffic-manager-faqs.md#how-many-layers-of-nesting-does-traffic-manager-support)
120120

121121
* [Can I mix other endpoint types with nested child profiles, in the same Traffic Manager profile?](./traffic-manager-faqs.md#can-i-mix-other-endpoint-types-with-nested-child-profiles-in-the-same-traffic-manager-profile)
122122

0 commit comments

Comments
 (0)