Skip to content

Commit f84829a

Browse files
authored
Update troubleshoot-response-timeout-and-errors.md
Fix cross-link
1 parent 7135716 commit f84829a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/api-management/troubleshoot-response-timeout-and-errors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ General strategies for mitigating SNAT port exhaustion are discussed in [Trouble
3939

4040
### Scale your APIM instance
4141

42-
Each API Management instance is allocated a number of SNAT ports, based on APIM units. You can allocate additional SNAT ports by scaling your API Management instance with additional units. For more info, see [Scale your API Management service](upgrade-and-scale.md#scale-your-api-management-service)
42+
Each API Management instance is allocated a number of SNAT ports, based on APIM units. You can allocate additional SNAT ports by scaling your API Management instance with additional units. For more info, see [Scale your API Management service](upgrade-and-scale.md#scale-your-api-management-instance).
4343

4444
> [!NOTE]
4545
> SNAT port usage is currently not available as a metric for autoscaling API Management units.
@@ -79,4 +79,4 @@ See [API Management access restriction policies](api-management-access-restricti
7979
## See also
8080

8181
* [Azure Load Balancer: Troubleshooting outbound connections failures](../load-balancer/troubleshoot-outbound-connection.md)
82-
* [Azure App Service: Troubleshooting intermittent outbound connection errors](../app-service/troubleshoot-intermittent-outbound-connection-errors.md)
82+
* [Azure App Service: Troubleshooting intermittent outbound connection errors](../app-service/troubleshoot-intermittent-outbound-connection-errors.md)

0 commit comments

Comments
 (0)