Resolved errors

Fixed Validation errors from GitHub

Author: vac0224

articles/communication-services/concepts/includes/codes/call-automation-sdk.md

@@ -12,7 +12,7 @@ ms.topic: include
 ms.custom: include file
 ms.author: slpavkov
 ---
-# Call Automation SDK error codes
+## Call Automation SDK error codes
 
 The following error codes are exposed by the Call Automation SDK.
 

articles/communication-services/concepts/includes/codes/calling-sdk.md

@@ -12,7 +12,7 @@ ms.topic: include
 ms.custom: include file
 ms.author: slpavkov
 ---
-# Calling SDK error codes
+## Calling SDK error codes
 
 The Azure Communication Services Calling SDK uses the following error codes to help you troubleshoot calling issues. These error codes are exposed through the `call.callEndReason` property after a call ends.
 

articles/communication-services/concepts/includes/codes/chat-sdk.md

@@ -12,7 +12,7 @@ ms.topic: include
 ms.custom: include file
 ms.author: slpavkov
 ---
-# Chat SDK error codes
+## Chat SDK error codes
 
 The Chat SDK uses the following error codes to help you troubleshoot chat issues. The error codes are exposed through the `error.code` property in the error response.
 

articles/communication-services/concepts/includes/codes/pstn.md

@@ -12,11 +12,11 @@ ms.topic: include
 ms.custom: include file
 ms.author: slpavkov
 ---
-# PSTN call response codes with ParticipantEndReason
+## PSTN call response codes with ParticipantEndReason
 
 This section provides troubleshooting information for various combinations of `ParticipantEndReason` and `ParticipantEndSubCode` response codes. For the tables in this section, `ParticipantEndReason` = **Code** and `ParticipantEndSubCode` = **SubCode**.
 
-## ParticipantEndReason 0
+### ParticipantEndReason 0
 
 Response `ParticipantEndReason` with value 0 usually means normal call clearing and marks calls that completed without errors.
 
@@ -27,7 +27,7 @@ Response `ParticipantEndReason` with value 0 usually means normal call clearing
 | 540000 | 0 | Normal PSTN call end:<br/> - User ended the call.<br/>  - Call ended by media agent.  | Success | |
 
 
-## ParticipantEndReason 4xx
+### ParticipantEndReason 4xx
 
 Response `ParticipantEndReason` with value 4xx means that the call didn't connect.
 
@@ -48,7 +48,7 @@ Response `ParticipantEndReason` with value 4xx means that the call didn't connec
 | 560487 | 497 | - The caller terminated the call request.<br/> - Request terminated with normal call clearing. |  | Retry the call. |
 
 
-## ParticipantEndReason 5xx 
+### ParticipantEndReason 5xx 
 
 Response `ParticipantEndReason` with value 5xx means that the call failed due to a problem with a software or hardware component required to complete the connection.
 
@@ -58,7 +58,7 @@ Response `ParticipantEndReason` with value 5xx means that the call failed due to
 | 560503 | 503 | - Call failed because of an internal server error in one of the services involved in the call.<br/> - The network used to establish the call is out of order.<br/> - A temporary failure in one of the services involved in the call. |  | - Check your network and routing configuration for possible issues. Verify that your network firewall rules are correct.<br/> - Retry the call. If the issue persist contact your telco provider or Microsoft support.<br/> - For direct routing calls, check your Session Border Control logs and settings and timeouts configuration, to see if your SBC caused the failure. |
 
 
-## ParticipantEndReason 603
+### ParticipantEndReason 603
 
 Response `ParticipantEndReason` with value 603 means that the call was rejected without connecting.
 

articles/communication-services/concepts/includes/codes/sms-sdk.md

@@ -12,7 +12,7 @@ ms.topic: include
 ms.custom: include file
 ms.author: slpavkov
 ---
-# SMS error codes
+## SMS error codes
 
 The SMS SDK uses the following error codes to help you troubleshoot SMS issues. The error codes are exposed through the `DeliveryStatusDetails` field in the SMS delivery report. 
 

articles/communication-services/concepts/sms/sms-faq.md

@@ -153,7 +153,7 @@ New limits are as follows:
 
 
 > [!IMPORTANT]
-> Unverified SMS traffic that exceeds the daily limit or is filtered for spam will have a [4010 error code](../troubleshooting-info.md#sms-error-codes)  returned for both scenarios.
+> Unverified SMS traffic that exceeds the daily limit or is filtered for spam has a [4010 error code](../troubleshooting-codes.md) returned for both scenarios.
 
 #### SMS to Canadian phone numbers
 Effective **October 1, 2022**, unverified toll-free numbers sending messages to Canadian destinations will have its traffic **blocked**. To unblock the traffic, a verification application needs to be submitted and in [verified status](#what-do-the-different-application-statuses-verified-and-unverified-mean).