Fixing bookmarks

Author: alexeyo26

articles/cognitive-services/Speech-Service/includes/speech-vnet-service-enpoints-private-endpoints.md

@@ -19,7 +19,7 @@ These are a few things that you should consider when making a choice:
 - VNet service points are often used when you want to restrict the access for your Speech resource based on the VNet(s) where the traffic originates from.
 - In case of Cognitive Services, enabling the VNet service endpoint forces the traffic for **all** Cognitive Services resources to go through the private backbone network. That requires explicit network access configuration (see details [here](../speech-service-vnet-service-endpoint.md#configure-vnets-and-the-speech-resource-networking-settings)). Private endpoints do not have this limitation and provide more flexibility for your network configuration - you can access one resource through the private backbone and another through the public internet using the same subnet of the same VNet.
 - Private endpoints incur [extra costs](https://azure.microsoft.com/pricing/details/private-link). VNet service endpoints are free.
-- Private endpoints require [extra DNS configuration](../speech-services-private-link.md#enable-private-endpoints).
+- Private endpoints require [extra DNS configuration](../speech-services-private-link.md#turn-on-private-endpoints).
 - One Speech resource may simultaneously work with both private endpoints and VNet service endpoints.
 
 We recommend that you try both endpoint types before deciding on your production design. 

articles/cognitive-services/Speech-Service/speech-service-vnet-service-endpoint.md

@@ -76,7 +76,7 @@ A Speech resource with a custom domain enabled uses a different way to interact
 
 ### Use a Speech resource with a custom domain name and allowed VNet(s) configured
 
-This is the case when **Selected Networks and Private Endpoints** option is selected in networking settings of the Speech resource **AND** at least one VNet is allowed. The usage is equivalent to [using a Speech resource with a custom domain name and a private endpoint enabled](speech-services-private-link.md#use-a-speech-resource-with-a-custom-domain-name-and-a-private-endpoint-enabled).
+This is the case when **Selected Networks and Private Endpoints** option is selected in networking settings of the Speech resource **AND** at least one VNet is allowed. The usage is equivalent to [using a Speech resource with a custom domain name and a private endpoint enabled](speech-services-private-link.md#adjust-an-application-to-use-a-speech-resource-with-a-private-endpoint).
 
 
 ### Use a Speech resource with a custom domain name and without allowed VNet(s)
@@ -86,7 +86,7 @@ This is the case when private endpoints are **not** enabled, and any of the foll
 - **Selected Networks and Private Endpoints** option is selected in networking settings of the Speech resource, but **no** allowed VNet(s) are configured
 - **All networks** option is selected in networking settings of the Speech resource
 
-The usage is equivalent to [using a Speech resource with a custom domain name and without private endpoints](speech-services-private-link.md#use-a-speech-resource-with-a-custom-domain-name-and-without-private-endpoints).
+The usage is equivalent to [using a Speech resource with a custom domain name and without private endpoints](speech-services-private-link.md#adjust-an-application-to-use-a-speech-resource-without-private-endpoints).
 
 
 [!INCLUDE [](includes/speech-vnet-service-enpoints-private-endpoints-simultaneously.md)]