Skip to content

Commit a30079b

Browse files
committed
acrolinx tweaks
1 parent deda3b6 commit a30079b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/frontdoor/standard-premium/how-to-enable-private-link-web-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ This article guides you through configuring Azure Front Door Premium to connect
4646
::: zone-end
4747

4848
> [!NOTE]
49-
> Private endpoints require your App Service plan to meet specific requirements. For more information, see [Using Private Endpoints for Azure Web App](../../app-service/networking/private-endpoint.md). This feature is not supported with App Service Slots.
49+
> Private endpoints require your App Service plan to meet specific requirements. For more information, see [Using Private Endpoints for Azure Web App](../../app-service/networking/private-endpoint.md). This feature isn't supported with App Service Slots.
5050
5151
## Enable Private Link to an App Service (Web App or Function App) in Azure Front Door Premium
5252

@@ -141,7 +141,7 @@ It can take a few minutes for the connection to fully establish after approval.
141141
142142
## Common mistakes to avoid
143143
144-
The following is a common mistake when configuring an origin with Azure Private Link enabled:
144+
The following mistake is common when configuring an origin with Azure Private Link enabled:
145145
146146
- Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
147147

0 commit comments

Comments
 (0)