Update batch-tls-101-migration-guide.md

Author: alfpark

articles/batch/batch-tls-101-migration-guide.md

@@ -16,7 +16,7 @@ To support security best practices and remain in compliance with industry standa
 
 TLS versions 1.0 and TLS 1.1 are known to be susceptible to BEAST and POODLE attacks and to have other Common Vulnerabilities and Exposures (CVE) weaknesses. TLS 1.0 and TLS 1.1 don't support the modern encryption methods and cipher suites that the Payment Card Industry (PCI) compliance standards recommends. Microsoft is participating in an industry-wide push toward the exclusive use of TLS version 1.2 or later.
 
-If you've already migrated to use TLS 1.2 in your Batch client application, then this retirement doesn't apply to you. Only APIs requests that go directly to the Batch service via the data plane API (that is, not management plane) are impacted. API requests at the management plane layer are routed through ARM and are subject to ARM TLS minimum version requirements. We recommend that you migrate to TLS 1.2 across Batch data plane or management plane API calls for security best practices, if applicable.
+If you've already migrated to use TLS 1.2 in your Batch client applications, then this retirement doesn't apply to you. Only API requests that go directly to the Batch service via the data plane API (not management plane) are impacted. API requests at the management plane layer are routed through ARM and are subject to ARM TLS minimum version requirements. We recommend that you migrate to TLS 1.2 across Batch data plane or management plane API calls for security best practices, if possible.
 
 ## Alternative: Use TLS 1.2
 
@@ -38,7 +38,7 @@ For more information, see [TLS best practices for the .NET Framework](/dotnet/fr
 
    TLS 1.0 and TLS 1.1 are considered insecure and have security issues that are addressed in TLS 1.2. TLS 1.2 has been available since 2008. TLS 1.2 is widely adopted as the minimum version for securing communication channels using TLS.
 
-- What happens if I don’t upgrade?
+- What happens if I don't upgrade?
 
    After the feature retirement from Azure Batch, your client application won't be able to communicate with Batch data plane API services unless you upgrade to TLS 1.2.
 
@@ -48,7 +48,7 @@ For more information, see [TLS best practices for the .NET Framework](/dotnet/fr
 
 - How do I know if I’m using TLS 1.0 or TLS 1.1?
 
-   To determine the TLS version you're using, check the audit log for your Batch deployment.
+   To determine the TLS version you're using, check your client application logs and the audit log for your Batch deployment.
 
 ## Next steps