Update expressroute-troubleshooting-network-performance.md

annadeAz · web-flow · commit e6c52e0744a3 · 2024-08-28T08:58:04.000-05:00
typo .. Rotue .. Route
diff --git a/articles/expressroute/expressroute-troubleshooting-network-performance.md b/articles/expressroute/expressroute-troubleshooting-network-performance.md
@@ -109,7 +109,7 @@ There are three basic steps to use this toolkit for Performance testing.
 If the performance test isn't giving you expected results, figuring out why should be a progressive step-by-step process. Given the number of components in the path, a systematic approach provides a faster path to resolution than jumping around. By troubleshooting systematically, you can prevent doing unnecessary testing multiple times.
 
 >[!NOTE]
->The scenario here is a performance issue, not a connectivity issue. To isolate the connectivity problem to Azure network, follow [Verifying ExpressRotue connectivity](expressroute-troubleshooting-expressroute-overview.md) article.
+>The scenario here is a performance issue, not a connectivity issue. To isolate the connectivity problem to Azure network, follow [Verifying ExpressRoute connectivity](expressroute-troubleshooting-expressroute-overview.md) article.
 >
 
 First, challenge your assumptions. Is your expectation reasonable? For instance, if you have a 1-Gbps ExpressRoute circuit and 100 ms of latency. It's not reasonable to expect the full 1 Gbps of traffic given the performance characteristics of TCP over high latency links. See the [References section](#references) for more on performance assumptions.

Original file line number	Diff line number	Diff line change
`@@ -109,7 +109,7 @@ There are three basic steps to use this toolkit for Performance testing.`
`109`	`109`	`If the performance test isn't giving you expected results, figuring out why should be a progressive step-by-step process. Given the number of components in the path, a systematic approach provides a faster path to resolution than jumping around. By troubleshooting systematically, you can prevent doing unnecessary testing multiple times.`
`110`	`110`
`111`	`111`	`>[!NOTE]`
`112`		`->The scenario here is a performance issue, not a connectivity issue. To isolate the connectivity problem to Azure network, follow [Verifying ExpressRotue connectivity](expressroute-troubleshooting-expressroute-overview.md) article.`
	`112`	`+>The scenario here is a performance issue, not a connectivity issue. To isolate the connectivity problem to Azure network, follow [Verifying ExpressRoute connectivity](expressroute-troubleshooting-expressroute-overview.md) article.`
`113`	`113`	`>`
`114`	`114`
`115`	`115`	`First, challenge your assumptions. Is your expectation reasonable? For instance, if you have a 1-Gbps ExpressRoute circuit and 100 ms of latency. It's not reasonable to expect the full 1 Gbps of traffic given the performance characteristics of TCP over high latency links. See the [References section](#references) for more on performance assumptions.`