fix spelling

Author: boris-bazilevskiy

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

@@ -18,21 +18,21 @@ ms.subservice: pstn
 
 This article provides information about limitations and known issues related to the Azure Communication Services direct routing
 
-1. Anonymous calling is not supported
+1. 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).
     - 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 additional workaround. Please contact Azure support for details.
+1. Wildcard SBC certificates require extra workaround. Contact Azure support for details.
     - will be fixed in GA release
-1. Media bypass/optimization is not supported
+1. Media bypass/optimization isn't supported
 1. No indication of SBC connection status/details in Azure portal
     - will be fixed in GA release
-1. Azure Communication Services direct routing is not available in Government Clouds
-1. Multi-tenant trunks are not supported
-1. Location-based routing is not supported
+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 is not supported 
+1. Enhanced 911 isn't supported 
 1. PSTN numbers missing from Call Summary logs 
 
 ## Next steps