fix blocking issues

Author: boris-bazilevskiy

articles/communication-services/concepts/telephony/emergency-calling-concept.md

@@ -65,7 +65,7 @@ The Emergency service is temporarily free to use for Azure Communication Service
 ## Emergency calling with Azure Communication Services direct routing
 
 Emergency call is a regular call from a direct routing perspective. If you want to implement emergency calling with Azure Communication Services direct routing, you need to make sure that there is a routing rule for your emergency number (911, 112, etc.). You also need to make sure that your carrier processes emergency calls properly.
-there is also an option to use purchased number as a caller id for direct routing calls, in such case if there is no voice routing rule for emergency number, the call will fall back to Microsoft network, and we will treat it as a regular emergency call. Learn more about [voice routing fall back](./direct-routing-provisioning.md#voice-routing-considerations).
+There is also an option to use purchased number as a caller ID for direct routing calls, in such case if there is no voice routing rule for emergency number, the call will fall back to Microsoft network, and we will treat it as a regular emergency call. Learn more about [voice routing fall back](./direct-routing-provisioning.md#voice-routing-considerations).
 
 ## Next steps
 

articles/communication-services/concepts/telephony/known-limitations-acs-telephony.md

@@ -14,26 +14,26 @@ ms.subservice: pstn
 
 # Known limitations in Azure telephony
 
-## Azure Communication Services direct routing known limitations
+This article provides information about limitations and known issues related to telephony in Azure Communication Services.
 
-This article provides information about limitations and known issues related to the Azure Communication Services direct routing
+## Azure Communication Services direct routing known limitations
 
-1. Anonymous calling isn't supported
+- Anonymous calling isn't supported
     - will be fixed in GA release
-1. Different set of Media Processors (MP) is used with different IP addresses. Currently [any Azure IP address](./direct-routing-infrastructure.md#media-traffic-ip-and-port-ranges) can be used for media connection between Azure MP and Session Border Controller (SBC).
+- Different set of Media Processors (MP) is used with different IP addresses. Currently [any Azure IP address](./direct-routing-infrastructure.md#media-traffic-ip-and-port-ranges) can be used for media connection between Azure MP and Session Border Controller (SBC).
     - will be fixed in GA release
-1. Azure Communication Services SBC Fully Qualified Domain Name (FQDN) must be different from Teams Direct Routing SBC FQDN
-1. Wildcard SBC certificates require extra workaround. Contact Azure support for details.
+- Azure Communication Services SBC Fully Qualified Domain Name (FQDN) must be different from Teams Direct Routing SBC FQDN
+- Wildcard SBC certificates require extra workaround. Contact Azure support for details.
     - will be fixed in GA release
-1. Media bypass/optimization isn't supported
-1. No indication of SBC connection status/details in Azure portal
+- Media bypass/optimization isn't supported
+- No indication of SBC connection status/details in Azure portal
     - will be fixed in GA release
-1. Azure Communication Services direct routing isn't available in Government Clouds
-1. Multi-tenant trunks aren't supported
-1. Location-based routing isn't supported
-1. No quality dashboard is available for customers
-1. Enhanced 911 isn't supported 
-1. PSTN numbers missing from Call Summary logs 
+- Azure Communication Services direct routing isn't available in Government Clouds
+- Multi-tenant trunks aren't supported
+- Location-based routing isn't supported
+- No quality dashboard is available for customers
+- Enhanced 911 isn't supported 
+- PSTN numbers missing from Call Summary logs 
 
 ## Next steps
 

articles/communication-services/toc.yml

@@ -185,6 +185,8 @@ items:
         href: concepts/telephony/certified-session-border-controllers.md
       - name: Inbound telephony calling capabilities
         href: concepts/telephony/inbound-calling-capabilities.md
+      - name: Known limitations
+        href: concepts/telephony/known-limitations-acs-telephony.md
   - name: SMS
     items:
       - name: SMS SDK overview