fix validation errors

vac0224 · vac0224 · commit 3aa94fc8f61e · 2025-05-27T16:24:43.000-05:00
diff --git a/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-client-capabilities.md b/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-client-capabilities.md
@@ -13,7 +13,7 @@ ms.service: azure-communication-services
 ---
 
 # Microsoft Teams Phone client capabilities in Calling client and Call Automation SDK
-
+    
 This article describes which Microsoft Teams Phone client capabilities Azure Communication Services Calling client and Call Automation SDKs support for Teams Phone extensibility.
 
 [!INCLUDE [public-preview-notice.md](../../../includes/public-preview-include-document.md)]
@@ -44,7 +44,7 @@ The following list of capabilities is supported for scenarios where at least one
 | | Terminate the entire call (ending the call for all participants)  | PP | ✔️  | ✔️  |
 | | Add an agent to an ongoing call | PP | ✔️  | ✔️  |
 | | Add external phone number from an ongoing call  | PP | ✔️  | ✔️  |
-| | Cancel an already initiated add participant request, as long as the the target agent / phone number hasn't accepted the call invite | PP | ❌  | ✔️  |
+| | Cancel an already initiated add participant request, as long as the the target agent / phone number has yet to accept the call invite | PP | ❌  | ✔️  |
 | | Remove a call participant from ongoing call | PP | ✔️  | ✔️  |
 | | Dial out to same phone number multiple times in a call | N/A | ❌  | ❌  |
 | | Transfer the end user from ongoing 1:1 call to another agent or external phone number  | PP | ✔️  | ✔️  |
@@ -68,7 +68,7 @@ The following list of capabilities is supported for scenarios where at least one
 | | Place call on hold and take call off hold (1:1 call only)   | PP | ✔️  | ❌ |
 | | Play music to the participant put on hold  | N/A | ❌  | ✔️ |
 | | Developer/agent can stream real-time audio out of the call to a WebSocket | PP | N/A | ✔️  |
-| Mid call media controls and device management | Existing Client Calling capabilities conform to [Calling SDK Features](../../../concepts/voice-video-calling/calling-sdk-features) | N/A | ✔️ | ❌ |
+| Mid call media controls and device management | Existing Client Calling capabilities conform to [Calling SDK Features](../../../concepts/voice-video-calling/calling-sdk-features.md) | N/A | ✔️ | ❌ |
 | Accessibility  | Agent can turn on Teams closed captions  | N/A | ❌  | N/A |
 | Emergency calling  | Agent can make an emergency call | PP | ✔️  | N/A |
 | | Honor Security desk policy for emergency calls  | PP | ✔️  | N/A |
@@ -90,10 +90,10 @@ The following list of capabilities is supported for scenarios where at least one
 | | Park a call  | N/A | ❌  | ❌  |
 | | Be parked  | N/A | ❌  | ❌  |
 | DevOps | Developers can access API operational metrics under Azure Metrics  | PuP | ✔️  | ✔️  |
-| | Developer can access call diagnostics under [Call Diagnostics Center](../../../concepts/voice-video-calling/call-diagnostics) | PuP | ✔️  | ✔️  |
+| | Developer can access call diagnostics under [Call Diagnostics Center](../../../concepts/voice-video-calling/call-diagnostics.md) | PuP | ✔️  | ✔️  |
 | | Developers can subscribe to get API and call logs under [Azure Monitor](../../analytics/logs/voice-and-video-logs.md) | PuP | ✔️  | ✔️  |
 | | Developers can get insights about their resource usage under [Azure Communication Services Insights](../../analytics/logs/voice-and-video-logs.md)  | PuP | ✔️  | ✔️  |
-| | Developers can subscribe to receive call state and roster changes events via Event Grid: [Azure Communication Services Voice and video calling events](../../../quickstarts/voice-video-calling/handle-calling-events) | N/A | ❌  | ❌  |
+| | Developers can subscribe to receive call state and roster changes events via Event Grid: [Azure Communication Services Voice and video calling events](../../../quickstarts/voice-video-calling/handle-calling-events.md) | N/A | ❌  | ❌  |
 | Teams caller ID policies  | Replace the caller ID with Replace the caller ID with this service number (Outbound PSTN call from the Teams Resource account honors its assigned Caller ID policy in the Teams Admin Center) | GA  | ✔️  | N/A |
 | | Block incoming caller ID  | GA  | ✔️  | ✔️  |
 | | Override the caller ID policy  | GA  | ✔️  | ✔️  |
diff --git a/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-connectivity-cost.md b/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-connectivity-cost.md
@@ -64,7 +64,7 @@ Choosing the best PSTN connectivity solution for Teams Phone extensibility depen
 
 The Teams Phone Extensibility business model for independent software vendors (ISVs) includes charging contact center as a service (CCaaS) vendors for using Azure Communication Services SDKs. This model includes Calling SDK and VoIP consumption, which require charges for each leg between the call automation bot and the CCaaS agent.
 
-This solution also includes Audio Insights with access to mixed/unmixed audio streams or direct transcriptions. Using transcription incurs an [Azure AI Speech pricing](https://azure.microsoft.com/en-us/pricing/details/cognitive-services/speech-services/) for the selected Azure resource and Call Recording with pay-as-you-go for mixed/unmixed AV recordings. You can review current pricing for VoIP, transcription, and recording at [Azure Communication Services pricing](https://azure.microsoft.com/en-us/pricing/details/communication-services/).
+This solution also includes Audio Insights with access to mixed/unmixed audio streams or direct transcriptions. Using transcription incurs an [Azure AI Speech pricing](https://azure.microsoft.com/en-us/pricing/details/cognitive-services/speech-services/) for the selected Azure resource and Call Recording with pay-as-you-go for mixed/unmixed AV recordings. You can review current pricing for VoIP, transcription, and recording at [Azure Communication Services pricing](https://azure.microsoft.com/pricing/details/communication-services/).
 
 End users can take advantage of their Teams Calling plans or any of the connectivity options for PSTN usage with inbound / outbound and any associated extra usage. Users must enable the required Teams licenses including Teams Phone License for any agent involved in the call including SMEs, and Resource Account license for the provisioned Teams resource account. For more information, see [Microsoft Teams Phone - Cloud Phone System](/microsoftteams/microsoft-teams-phone).
 
diff --git a/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md b/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md
@@ -44,7 +44,7 @@ This feature is available in all supported countries by Microsoft Teams for user
 - Teams Phone License: Required essential for any agent using either a CCaaS client based on Azure Communication Services Calling SDK or a Teams client. The Teams Phone license enables the use of Teams Phone capabilities.
 - Resource Account License: Included in the Teams Phone license and is necessary for managing resource accounts used in call automation and other functionalities.
 - Enterprise Voice: Users must be Enterprise Voice enabled to ensure they can make and receive calls using the Teams Phone system.
-- Calling Plan (or similar connectivity option): For customers making outbound calls.
+- Calling Plan (or similar connectivity option): Applies to customers making outbound calls.
 
 ## What is Dual Persona or Multi Persona?
 
diff --git a/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md b/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md
@@ -2,9 +2,12 @@
 title: Teams Phone extensibility Troubleshooting
 titleSuffix: An Azure Communication Services document
 description: This article describes most common issues and ways to troubleshoot them with Teams Phone extensibility.
+author: henikaraa
+manager: chpalm
 ms.service: azure-communication-services
 ms.subservice: teams-interop
 ms.date: 05/19/2025
+ms.topic: conceptual
 ms.author: henikaraa
 ms.custom: public_preview
 services: azure-communication-services
@@ -23,8 +26,8 @@ By understanding the potential sources of errors, you can ensure a smoother and
 ## Call Automation troubleshooting
 
 For troubleshooting issues related to call automation, see the following resources:
-- [Troubleshooting call end response codes](../../../resources/troubleshooting/voice-video-calling/troubleshooting-codes?pivots=automation): provides detailed information on troubleshooting call end response codes for Call Automation, including common error codes and their meanings.
-- [Known issues](../../voice-video-calling/known-issues-call-automation): outlines known issues with call automation, offering insights into current limitations and workarounds.
+- [Troubleshooting call end response codes](../../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md?pivots=automation): provides detailed information on troubleshooting call end response codes for Call Automation, including common error codes and their meanings.
+- [Known issues](../../voice-video-calling/known-issues-call-automation.md): outlines known issues with call automation, offering insights into current limitations and workarounds.
   
 ## Calling SDK troubleshooting
 
@@ -52,7 +55,7 @@ For troubleshooting issues related to the Calling SDK, see:
 
 If you receive the following error:
 
-    The app is trying to access a service '1fd5118e-2576-4263-8130-9503064c837a'(Azure Communication Services) that your organization '{GUID}' lacks a service principal for. Contact your IT Admin to review the configuration of your service subscriptions or consent to the application to create the required service principal.
+   The app is trying to access a service '1fd5118e-2576-4263-8130-9503064c837a'(Azure Communication Services) that your organization '{GUID}' lacks a service principal for. Contact your IT Admin to review the configuration of your service subscriptions or consent to the application to create the required service principal.
 
 Your Microsoft Entra ID tenant lacks a service principal for the Azure Communication Services application. To fix this issue, use PowerShell as a Microsoft Entra ID administrator to connect to your tenant. Replace Tenant_ID with an ID of your Microsoft Entra ID tenancy.
 
diff --git a/articles/communication-services/concepts/interop/tpe/teams-phone-overview.md b/articles/communication-services/concepts/interop/tpe/teams-phone-overview.md
@@ -248,6 +248,6 @@ The following diagram shows an example call recording flow. In this example, the
 
 ## Related articles
 
-- [Teams Phone client capabilities](./teams-phone-client-capabilities.md)
+- [Teams Phone client capabilities](./teams-phone-extensibility-client-capabilities.md)
 - [Teams Phone extensibility FAQ](./teams-phone-extensibility-faq.md)
 - [Teams Phone extensibility troubleshooting](./teams-phone-extensibility-troubleshooting.md)
diff --git a/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md b/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md
