Rewording and fixing typo

Author: toddfoust

articles/azure-monitor/app/ip-addresses.md

@@ -33,9 +33,9 @@ You need to open some outgoing ports in your server's firewall to allow the Appl
 > These addresses are listed by using Classless Interdomain Routing notation. As an example, an entry like `51.144.56.112/28` is equivalent to 16 IPs that start at `51.144.56.112` and end at `51.144.56.127`.
 
 > [!NOTE]
-> Application Insights connection-string based telemetry ingestion regional endpoints only support TLS 1.2. Telemetry global endpoints continue to support TLS 1.0 and TLS 1.1.
-> 
-> As described in the [Azure TLS 1.2 migration announcement](https://azure.microsoft.com/updates/azuretls12/), Application Insights regional endpoints only support TLS 1.2. If you're using an older version of TLS, Application Insights will not ingest any telemetry. For applications based on .NET Framework see [Transport Layer Security (TLS) best practices with the .NET Framework](https://learn.microsoft.com/dotnet/framework/network-programming/tls) to support the newer TLS version.
+> As described in the [Azure TLS 1.2 migration announcement](https://azure.microsoft.com/updates/azuretls12/), Application Insights connection-string based regional telemetry endpoints only support TLS 1.2. Global telemetry endpoints continue to support TLS 1.0 and TLS 1.1.
+>
+> If you're using an older version of TLS, Application Insights will not ingest any telemetry. For applications based on .NET Framework see [Transport Layer Security (TLS) best practices with the .NET Framework](https://learn.microsoft.com/dotnet/framework/network-programming/tls) to support the newer TLS version.
 
 ## Status Monitor